We appear to still not have a spidermonkey:60 in main tree. This is required by GNOME 3.30. Please provide the SLOT, thanks :)
_AxS_ added one, but unfortunately it crashes when gjs is doing a very simple check, that basically amounts to running the compiled result of this test: #include <js/Initialization.h> int main(void) { if (!JS_Init()) exit(1); JS_ShutDown(); } compiled with e.g. gcc `pkg-config mozjs-60 --cflags --libs` -o gjs-test gjs-test.cpp --std=gnu++14 -ggdb3 (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007ffff770961b in js::Mutex::Mutex (id=..., this=0x7ffff7f820e8 <execMemory+8>) at /usr/src/debug/dev-lang/spidermonkey-60.5.2_p0/mozjs-60.5.2/js/src/threading/Mutex.h:35 #2 ProcessExecutableMemory::ProcessExecutableMemory (this=0x7ffff7f820e0 <execMemory>) at /usr/src/debug/dev-lang/spidermonkey-60.5.2_p0/mozjs-60.5.2/js/src/jit/ProcessExecutableMemory.cpp:427 #3 __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/src/debug/dev-lang/spidermonkey-60.5.2_p0/mozjs-60.5.2/js/src/jit/ProcessExecutableMemory.cpp:565 #4 _GLOBAL__sub_I_Unified_cpp_js_src19.cpp(void) () at /usr/src/debug/dev-lang/spidermonkey-60.5.2_p0/mozjs-60.5.2/js/src/jit/RangeAnalysis.cpp:3122 #5 0x00007ffff7fe36cb in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffffffda08, env=env@entry=0x7fffffffda18) at dl-init.c:72 #6 0x00007ffff7fe37d9 in call_init (env=0x7fffffffda18, argv=0x7fffffffda08, argc=1, l=<optimized out>) at dl-init.c:30 #7 _dl_init (main_map=0x7ffff7ffe130, argc=1, argv=0x7fffffffda08, env=0x7fffffffda18) at dl-init.c:119 #8 0x00007ffff7fd50da in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #9 0x0000000000000001 in ?? () #10 0x00007fffffffde10 in ?? () #11 0x0000000000000000 in ?? ()
hmm, spidermonkey from overlay fails the same; weird, assumed that was used by overlays and works fine. I wonder if this is some kind of local problem even.
Problem goes away if changing --enable-jemalloc to --disable-jemalloc in the ebuild; main tree one too. And looking at one of the overlays that had newer gjs, they have --disable-jemalloc spidermonkey too, without explanations or explaining git history though.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=78d8409a783696604e38266d3c118e35fa349a34 commit 78d8409a783696604e38266d3c118e35fa349a34 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-03-17 18:25:48 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-03-17 22:12:26 +0000 dev-lang/spidermonkey: explicitly disable jemalloc Jemalloc support is broken in standalone mozjs release and causes a trivial embedder to segfault. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1465038 Closes: https://bugs.gentoo.org/680006 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> .../{spidermonkey-60.5.2_p0.ebuild => spidermonkey-60.5.2_p0-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
