NEW 137208
[GTK] JSGarbageCollect No such file or directory causing Midori/Epiphany browsers to segfault 
https://bugs.webkit.org/show_bug.cgi?id=137208
Summary [GTK] JSGarbageCollect No such file or directory causing Midori/Epiphany brow...
contax@phrenetic.org
Reported 2014-09-29 03:00:52 PDT
Hi, I hope that this is the right place for this bug report and in the right format. Please forgive me if it's not. I'm new to this kind of thing... On the Raspberry Pie (armv6l) running Raspian, I seem to get a seg fault when any page that has javascript on it is run. It seems that things work okay when using the packages in the 2014-06-20-wheezy-raspberian.img, but after doing an apt-get upgrade, the bug is introduced. I get the following error when running gdb Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xaa33a2a0 (LWP 81330)] JSGarbageCollect (ctx=0x65746144) at ../Source/JavaScriptCore/API/JSBase.cpp:101 101 ../Source/JavaScriptCore/API/JSBase.cpp: No such file or directory. The Backtrack is: #0 JSGarbageCollect (ctx=0x65746144) at ../Spource/JavaScriptCore/API/JSBase.cpp:101 #1 0xb139fe68 in ?? () from /usr/lib/arm-linux-gnueabihf/libproxy/0.3.1/modules/pacrunner_webkit.so #2 0xb139fe68 in ?? () from /usr/lib/arm-linux-gnueabihf/libproxy/0.3.1/modules/pacrunner_webkit.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) The package being used is: Package: libjavascriptcodegtk-1.0-0 Version: 1.8.1-3.4+rpil Architecture: armhf
Attachments
Add attachment proposed patch, testcase, etc.
Note You need to log in before you can comment on or make changes to this bug.