Thread: [Vimprobable-users] js crash
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
Menu
▾
▴
vimprobable-users
|
From: Serge E. H. <se...@ha...> - 2016-03-11 08:45:43
|
Hi, for several months now I've had regular crashes in vimprobable - most easily reproduced by turning js on and going to imgur, then paging down a bit. Presumably ad reloading or something. gdb unhelpfully gives me: (gdb) where #0 0x00007f6dcfe6e6f0 in JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #1 0x00007f6dcfd44bdc in ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #2 0x00007f6d703ac3f0 in ?? () #3 0x00007f6d5deae5b0 in ?? () #4 0x00007f6dbd868000 in ?? () #5 0x00007f6d4c0756c8 in ?? () #6 0x00007fff79eb11d0 in ?? () #7 0x00007f6d5e32eff8 in ?? () #8 0x00007fff79eb11e0 in ?? () #9 0x00007fff79eb1160 in ?? () #10 0x00007f6dcfd29813 in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Just curious, does this say anything to anyone here? thanks, -serge |
|
From: Hannes S. <ha...@yl...> - 2016-03-11 15:58:31
|
Hi Serge! On Fri, 11 Mar 2016 02:26:24 -0600, "Serge E. Hallyn" <se...@ha...> wrote: > for several months now I've had regular crashes in vimprobable - most > easily reproduced by turning js on and going to imgur, then paging > down a bit. Presumably ad reloading or something. gdb unhelpfully > gives me: Could you provide an URL where this happens? Also, could you build the browser with debugging symbols enabled (see Makefile) and then provide a backtrace? Hannes |
|
From: Serge E. H. <se...@ha...> - 2016-03-12 00:39:21
|
On Fri, Mar 11, 2016 at 04:19:07PM +0100, Hannes Schüller wrote: > Hi Serge! > > On Fri, 11 Mar 2016 02:26:24 -0600, "Serge E. Hallyn" > <se...@ha...> wrote: > > for several months now I've had regular crashes in vimprobable - most > > easily reproduced by turning js on and going to imgur, then paging > > down a bit. Presumably ad reloading or something. gdb unhelpfully > > gives me: > > Could you provide an URL where this happens? Also, could you build the > browser with debugging symbols enabled (see Makefile) and then provide a > backtrace? I went ahead and rebuilt, and got: Thread 1 "vimprobable2" received signal SIGSEGV, Segmentation fault. 0x00007ffff4cb6678 in JSC::JSCell::toPrimitive(JSC::ExecState*, JSC::PreferredPrimitiveType) const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb) where #0 0x00007ffff4cb6678 in JSC::JSCell::toPrimitive(JSC::ExecState*, JSC::PreferredPrimitiveType) const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #1 0x00007ffff4d1bf0b in JSC::JSValue::toStringSlowCase(JSC::ExecState*) const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #2 0x00007ffff4b87991 in ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #3 0x00007ffff4b88273 in ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #4 0x00007fff90065409 in ?? () #5 0x0000000000000000 in ?? () as I said, http://imgur.com is my easiest reproducer; just browse with javascript on and page down. |
|
From: Hannes S. <ha...@yl...> - 2016-03-12 08:22:47
|
On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" <se...@ha...> wrote: > On Fri, Mar 11, 2016 at 04:19:07PM +0100, Hannes Schüller wrote: > > On Fri, 11 Mar 2016 02:26:24 -0600, "Serge E. Hallyn" > > <se...@ha...> wrote: > > > for several months now I've had regular crashes in vimprobable - > > > most easily reproduced by turning js on and going to imgur, then > > > paging down a bit. Presumably ad reloading or something. gdb > > > unhelpfully gives me: > > > > Could you provide an URL where this happens? Also, could you build > > the browser with debugging symbols enabled (see Makefile) and then > > provide a backtrace? > > I went ahead and rebuilt, and got: > > Thread 1 "vimprobable2" received signal SIGSEGV, Segmentation fault. > 0x00007ffff4cb6678 in JSC::JSCell::toPrimitive(JSC::ExecState*, > JSC::PreferredPrimitiveType) const () > from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 (gdb) > where #0 0x00007ffff4cb6678 in > JSC::JSCell::toPrimitive(JSC::ExecState*, > JSC::PreferredPrimitiveType) const () > from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #1 > 0x00007ffff4d1bf0b in JSC::JSValue::toStringSlowCase(JSC::ExecState*) > const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 > #2 0x00007ffff4b87991 in ?? () > from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #3 > 0x00007ffff4b88273 in ?? () > from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0 #4 > 0x00007fff90065409 in ?? () #5 0x0000000000000000 in ?? () Hm, still not particularly telling. Probably an indication that the error is really inside a library rather than the browser itself. > as I said, http://imgur.com is my easiest reproducer; just browse > with javascript on and page down. Sorry, I can't reproduce it. I scrolled down until it had reloaded new images about ten times, but no instability – it's working fine here. Anyone else experience the problem? Hannes |
|
From: Marcos C. <vim...@pr...> - 2016-03-12 13:35:48
|
En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / skribis / wrote : > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" wrote: > > as I said, http://imgur.com is my easiest reproducer; just browse > > with javascript on and page down. > > Sorry, I can't reproduce it. I scrolled down until it had reloaded new > images about ten times, but no instability – it's working fine here. > > Anyone else experience the problem? It's working fine here. No problem scrolling down many times. -- Marcos Cruz http://programandala.net |
|
From: Serge E. H. <se...@ha...> - 2016-03-13 03:25:48
|
Quoting Marcos Cruz (vim...@pr...): > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / skribis / wrote : > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" wrote: > > > as I said, http://imgur.com is my easiest reproducer; just browse > > > with javascript on and page down. > > > > Sorry, I can't reproduce it. I scrolled down until it had reloaded new > > images about ten times, but no instability – it's working fine here. > > > > Anyone else experience the problem? > > It's working fine here. No problem scrolling down many times. Fascinating - what on earth do I have going on then :) I'll figure it out. thanks, -serge |
|
From: Serge E. H. <se...@ha...> - 2016-03-14 01:26:57
|
Quoting Serge E. Hallyn (se...@ha...): > Quoting Marcos Cruz (vim...@pr...): > > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / skribis / wrote : > > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" wrote: > > > > as I said, http://imgur.com is my easiest reproducer; just browse > > > > with javascript on and page down. > > > > > > Sorry, I can't reproduce it. I scrolled down until it had reloaded new > > > images about ten times, but no instability – it's working fine here. > > > > > > Anyone else experience the problem? > > > > It's working fine here. No problem scrolling down many times. > > Fascinating - what on earth do I have going on then :) I'll figure > it out. Ok it's purely a webkitgtk bug. I just reproduced it with surf. |
|
From: Hannes S. <ha...@yl...> - 2016-03-14 17:10:46
|
On Sun, 13 Mar 2016 20:26:48 -0500, "Serge E. Hallyn" <se...@ha...> wrote: > Quoting Serge E. Hallyn (se...@ha...): > > Quoting Marcos Cruz (vim...@pr...): > > > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / skribis / > > > wrote : > > > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" wrote: > > > > > as I said, http://imgur.com is my easiest reproducer; just > > > > > browse with javascript on and page down. > > > > > > > > Sorry, I can't reproduce it. I scrolled down until it had > > > > reloaded new images about ten times, but no instability – it's > > > > working fine here. > > > > > > > > Anyone else experience the problem? > > > > > > It's working fine here. No problem scrolling down many times. > > > > Fascinating - what on earth do I have going on then :) I'll figure > > it out. > > Ok it's purely a webkitgtk bug. I just reproduced it with surf. Thanks for the followup :) Hannes |
|
From: Serge E. H. <se...@ha...> - 2016-03-14 17:25:24
|
Quoting Hannes Schüller (ha...@yl...): > On Sun, 13 Mar 2016 20:26:48 -0500, "Serge E. Hallyn" > <se...@ha...> wrote: > > Quoting Serge E. Hallyn (se...@ha...): > > > Quoting Marcos Cruz (vim...@pr...): > > > > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / skribis / > > > > wrote : > > > > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" wrote: > > > > > > as I said, http://imgur.com is my easiest reproducer; just > > > > > > browse with javascript on and page down. > > > > > > > > > > Sorry, I can't reproduce it. I scrolled down until it had > > > > > reloaded new images about ten times, but no instability – it's > > > > > working fine here. > > > > > > > > > > Anyone else experience the problem? > > > > > > > > It's working fine here. No problem scrolling down many times. > > > > > > Fascinating - what on earth do I have going on then :) I'll figure > > > it out. > > > > Ok it's purely a webkitgtk bug. I just reproduced it with surf. > > Thanks for the followup :) Hannes and Marcos, could you tell me the distro and webkit version you're running? |
|
From: Hannes S. <ha...@yl...> - 2016-03-14 18:05:00
|
On Mon, 14 Mar 2016 12:25:16 -0500, "Serge E. Hallyn" <se...@ha...> wrote: > Quoting Hannes Schüller (ha...@yl...): > > On Sun, 13 Mar 2016 20:26:48 -0500, "Serge E. Hallyn" > > <se...@ha...> wrote: > > > Quoting Serge E. Hallyn (se...@ha...): > > > > Quoting Marcos Cruz (vim...@pr...): > > > > > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / > > > > > skribis / wrote : > > > > > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" > > > > > > wrote: > > > > > > > as I said, http://imgur.com is my easiest reproducer; > > > > > > > just browse with javascript on and page down. > > > > > > > > > > > > Sorry, I can't reproduce it. I scrolled down until it had > > > > > > reloaded new images about ten times, but no instability – > > > > > > it's working fine here. > > > > > > > > > > > > Anyone else experience the problem? > > > > > > > > > > It's working fine here. No problem scrolling down many > > > > > times. > > > > > > > > Fascinating - what on earth do I have going on then :) I'll > > > > figure it out. > > > > > > Ok it's purely a webkitgtk bug. I just reproduced it with surf. > > > > Thanks for the followup :) > > Hannes and Marcos, could you tell me the distro and webkit version > you're running? I have Debian with libwebkitgtk-1.0-0 2.4.8-1 Hannes |
|
From: Serge E. H. <se...@ha...> - 2016-03-14 22:21:56
|
Quoting Hannes Schüller (ha...@yl...): > On Mon, 14 Mar 2016 12:25:16 -0500, "Serge E. Hallyn" > <se...@ha...> wrote: > > Quoting Hannes Schüller (ha...@yl...): > > > On Sun, 13 Mar 2016 20:26:48 -0500, "Serge E. Hallyn" > > > <se...@ha...> wrote: > > > > Quoting Serge E. Hallyn (se...@ha...): > > > > > Quoting Marcos Cruz (vim...@pr...): > > > > > > En/Je/On 2016-03-12 09:22, Hannes Schüller escribió / > > > > > > skribis / wrote : > > > > > > > On Fri, 11 Mar 2016 18:39:13 -0600, "Serge E. Hallyn" > > > > > > > wrote: > > > > > > > > as I said, http://imgur.com is my easiest reproducer; > > > > > > > > just browse with javascript on and page down. > > > > > > > > > > > > > > Sorry, I can't reproduce it. I scrolled down until it had > > > > > > > reloaded new images about ten times, but no instability – > > > > > > > it's working fine here. > > > > > > > > > > > > > > Anyone else experience the problem? > > > > > > > > > > > > It's working fine here. No problem scrolling down many > > > > > > times. > > > > > > > > > > Fascinating - what on earth do I have going on then :) I'll > > > > > figure it out. > > > > > > > > Ok it's purely a webkitgtk bug. I just reproduced it with surf. > > > > > > Thanks for the followup :) > > > > Hannes and Marcos, could you tell me the distro and webkit version > > you're running? > > I have Debian with libwebkitgtk-1.0-0 2.4.8-1 Hi, did you pin that? I'm seeing: rmadison -u debian libwebkitgtk-1.0-0 libwebkitgtk-1.0-0 | 1.8.1-3.4 | oldstable | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc libwebkitgtk-1.0-0 | 2.4.8-2 | stable-kfreebsd | kfreebsd-amd64, kfreebsd-i386 libwebkitgtk-1.0-0 | 2.4.9-1~deb8u1 | stable | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libwebkitgtk-1.0-0 | 2.4.9-3 | testing | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x libwebkitgtk-1.0-0 | 2.4.9-3 | unstable | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x I should probably look at the debdiff from 2.4.8-1..2.4.9-3 (or -2), the bug must lie there. |
|
From: Marcos C. <vim...@pr...> - 2016-03-15 12:57:15
|
En/Je/On 2016-03-14 12:25, Serge E. Hallyn escribió / skribis / wrote : > Hannes and Marcos, could you tell me the distro and webkit version you're > running? Raspbian (equivalent to Debian 7.9, for Raspberry Pi) libwebkitgtk-1.0-0 Version: 1.8.1-3.4+rpi1 -- Marcos Cruz http://programandala.net |
|
From: Serge E. H. <se...@ha...> - 2016-03-15 16:58:28
|
On Tue, Mar 15, 2016 at 01:57:00PM +0100, Marcos Cruz wrote: > En/Je/On 2016-03-14 12:25, Serge E. Hallyn escribió / skribis / wrote : > > > Hannes and Marcos, could you tell me the distro and webkit version you're > > running? > > Raspbian (equivalent to Debian 7.9, for Raspberry Pi) > > libwebkitgtk-1.0-0 Version: 1.8.1-3.4+rpi1 Thanks. So maybe until I have more time I should statically link with 2.4.8 which apparently works fine. I'm on 2.4.9 (2.4.9-2ubuntu2). |
Thanks for helping keep SourceForge clean.
X