Processing control commands:
severity -1 important
Bug #651636 [src:webkit] GtkLauncher segfaults on mipsel, JavaScript-related
Bug #673469 [src:webkit] libwebkitgtk-1.0-0: segfaults all the time on armel,
javascript related
Bug #688640 [src:webkit] JavaScriptCore segmentation fault on PowerPC
found 651636 1.8.1-3.4
thanks
Hi,
I've tested the new builds on mipsel, but when JavaScript is enabled
things are still unstable. The attached crashes from GtkLauncher are
easily reproducible by starting the SunSpider benchmark and refreshing
after a few seconds:
Processing commands for cont...@bugs.debian.org:
found 651636 1.8.1-3.4
Bug #651636 {Done: Michael Gilbert mgilb...@debian.org} [src:webkit]
GtkLauncher segfaults on mipsel, JavaScript-related
Bug #673469 {Done: Michael Gilbert mgilb...@debian.org} [src:webkit]
libwebkitgtk-1.0-0: segfaults
Package: libwebkitgtk-1.0-0
Version: 1.8.1-3.3
Followup-For: Bug #651636
Still frequently crashing on mipsel with 1.8.1-3.3 :
Program terminated with signal 11, Segmentation fault.
#0 0x7562b9d4 in WTF::fastFree(void*) ()
from /usr/lib/libjavascriptcoregtk-1.0.so.0
No symbol table info
Hi,
If this bug relates to JIT, it could be the same as #673469 seen on
armel, still unfixed upstream but disabling JIT for now is a suggested
workaround.
My mipsel hardware is probably not powerful enough to rebuild webkit to
try this myself, though...
p.s.: disabling JavaScript in Midori
Processing commands for cont...@bugs.debian.org:
# justification: renders package unusable
severity 651636 grave
Bug #651636 [libwebkitgtk-1.0-0] GtkLauncher segfaults on mipsel,
JavaScript-related
Severity set to 'grave' from 'important'
thanks
Stopping processing here.
Please contact me if
6 matches
Mail list logo
