| Summary: | dev-libs/gjs-1.36.1 - add support for mozjs-17 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Tsoy <alexander> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | gjs-1.36.1.ebuild.patch | ||
|
Description
Alexander Tsoy
2013-08-12 16:47:43 UTC
(In reply to Alexander Tsoy from comment #0) > (IUSE=mozjs-17 or IUSE=js17 ?). Or may be revision bump? Link to the sources tarball is available on this LFS page: http://www.linuxfromscratch.org/blfs/view/svn/gnome/gjs.html Created attachment 355860 [details, diff]
gjs-1.36.1.ebuild.patch
Patched ebuild works for me. After switching to js17 gnome-shell should be rebuilt.
Before rebuild
$ ldd /usr/bin/gnome-shell | grep mozjs
libmozjs185.so.1.0 => /usr/lib64/libmozjs185.so.1.0 (0x0000030bd2d8b000)
libmozjs-17.0.so => /usr/lib64/libmozjs-17.0.so (0x0000030bccbc3000)
After rebuild
$ ldd /usr/bin/gnome-shell | grep mozjs
libmozjs-17.0.so => /usr/lib64/libmozjs-17.0.so (0x000003cb6b8ff000)
After a week of testing I can say, that with spidermonkey-17 Gnome Shell works much better. With spidermonkey-1.8.5 I was forced to restarted Gnome Shell several times a day, because its memory consumption rose up to ~2 Gb RSS, or because it was completely deadlocked. With spidermonkey-17 memory consumption did not rise above ~500 Mb, deadlocks still happen, but less often. thanks, indeed. $ ldd /usr/bin/gnome-shell | grep mozjs libmozjs-17.0.so => /usr/lib64/libmozjs-17.0.so (0x00007f231fbee000) (In reply to Alexander Tsoy from comment #4) > After a week of testing I can say, that with spidermonkey-17 Gnome Shell > works much better. With spidermonkey-1.8.5 I was forced to restarted Gnome > Shell several times a day, because its memory consumption rose up to ~2 Gb > RSS, or because it was completely deadlocked. With spidermonkey-17 memory > consumption did not rise above ~500 Mb, deadlocks still happen, but less > often. I would wait for upstream to release a version supporting this (they will probably wait for next major version -> 1.38) Second sentence at homepage of spidermonkey states: https://developer.mozilla.org/en-US/docs/SpiderMonkey > SpiderMonkey 17 is the most recent standalone source code release. It > implements JavaScript 1.8.5, and it is largely the same engine that > shipped with Firefox 17. spidermonkey-1.8.5 essentially seems to be spidermonkey-17 without jit Why wait ? Uuups, gnome-3.8 with spidermonkey-17 jit freezes my system sometimes Now I am trying without USE jit and it seems to work so far ... By far better without USE jit. Should this USE flag spidermonkey-17 jit be masked or be warned of: gnome||jit gjs-1.38 is using mozjs-17, closing. |