Bug 184971 - [GTK] Segfault in libjavascriptcoregtk
Summary: [GTK] Segfault in libjavascriptcoregtk
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-25 08:17 PDT by Cédric Bellegarde
Modified: 2018-04-25 13:04 PDT (History)
2 users (show)

See Also:

Attachments
Full backtrace (40.03 KB, text/plain)
2018-04-25 08:17 PDT, Cédric Bellegarde 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cédric Bellegarde 2018-04-25 08:17:49 PDT 
Created attachment 338737 [details]
Full backtrace

1   0x7f27ad5de2b8 /usr/lib/libjavascriptcoregtk-4.0.so.18(WTFCrash+0x18) [0x7f27ad5de2b8]
2   0x7f27ad043506 /usr/lib/libjavascriptcoregtk-4.0.so.18(+0x8a3506) [0x7f27ad043506]
3   0x7f27ad03b5d4 /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3JSC4Heap31finalizeUnconditionalFinalizersEv+0x44) [0x7f27ad03b5d4]
4   0x7f27ad03d3fb /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3JSC4Heap11runEndPhaseENS_11GCConductorE+0x28b) [0x7f27ad03d3fb]
5   0x7f27ad040bab /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3JSC4Heap15runCurrentPhaseENS_11GCConductorEPNS_18CurrentThreadStateE+0x11b) [0x7f27ad040bab]
6   0x7f27ad040be4 /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3JSC4Heap24collectInCollectorThreadEv+0x14) [0x7f27ad040be4]
7   0x7f27ad045ebe /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3JSC4Heap6Thread4workEv+0xe) [0x7f27ad045ebe]
8   0x7f27ad5e002a /usr/lib/libjavascriptcoregtk-4.0.so.18(+0xe4002a) [0x7f27ad5e002a]
9   0x7f27ad5fd340 /usr/lib/libjavascriptcoregtk-4.0.so.18(_ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE+0x70) [0x7f27ad5fd340]
10  0x7f27ad63206a /usr/lib/libjavascriptcoregtk-4.0.so.18(+0xe9206a) [0x7f27ad63206a]
11  0x7f27bec3f0bc /usr/lib/libpthread.so.0(+0x70bc) [0x7f27bec3f0bc]
12  0x7f27be9742ff /usr/lib/libc.so.6(clone+0x3f) [0x7f27be9742ff]
Comment 1 Michael Catanzaro 2018-04-25 08:46:05 PDT 
The full backtrace is truncated at thread 142. Also, something has gone super wrong for you to have that many threads running. There's probably a thread leak.
Comment 2 Cédric Bellegarde 2018-04-25 13:04:53 PDT 
>The full backtrace is truncated at thread 142

I know, another gdb segfault :-/