[Webkit-unassigned] [Bug 137208] New: [GTK] JSGarbageCollect No such file or directory causing Midori/Epiphany browsers to segfault

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 29 03:00:53 PDT 2014


https://bugs.webkit.org/show_bug.cgi?id=137208

           Summary: [GTK] JSGarbageCollect No such file or directory
                    causing Midori/Epiphany browsers to segfault
           Product: WebKit
           Version: 412
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: contax at phrenetic.org


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

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list