Crashing after a while of use

Bug #1488760 reported by Abdusamed Ahmed
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Midori Web Browser
Fix Released
Undecided
Unassigned

Bug Description

It's crashes on Ubuntu 15.04 64bit and Linuxmint 17.2 Mate 32bit. Don't know exactly why it crashes on Ubuntu machine but here is the log for Linuxmint 17.2 Mate 32bit when Midori running with "midori --debug" mode

Note, it happened twice. It crashed, it ran the command again and it crashed again.

~ $ midori --debug
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt' --return-child-result --args midori
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/i386-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
Vector smash protection is enabled.
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
OpenJDK Server VM (build 24.79-b02, mixed mode)

(midori4:3530): GLib-CRITICAL **: Source ID 17690 was not found when attempting to remove it

(midori4:3530): GLib-CRITICAL **: Source ID 17318 was not found when attempting to remove it

Program received signal SIGSEGV, Segmentation fault.
0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#0 0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#1 0xb51591e1 in JSC::JSValue::toNumberSlowCase(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2 0xb51704fa in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3 0x9b88146f in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
 ~ $ midori --debug
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt' --return-child-result --args midori
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/i386-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
Vector smash protection is enabled.
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
OpenJDK Server VM (build 24.79-b02, mixed mode)

Program received signal SIGSEGV, Segmentation fault.
0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#0 0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#1 0xb51591e1 in JSC::JSValue::toNumberSlowCase(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2 0xb51704fa in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3 0x9b87846f in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Tags: javascript
Revision history for this message
Abdusamed Ahmed (sir508) wrote :

Can someone please tell me how I can fix? It keeps on crashing. I tried debugging and tried to fix "ImportError: No module named 'libstdcxx'"

Won't budge.

Revision history for this message
Abdusamed Ahmed (sir508) wrote :

Alright, I tried fixing and I though I fixed it. I *think* I fixed the "ImportError: No module named 'libstdcxx" by doing the following

Created the text file at ~/.gdbinit

And pasted this code.

python
import sys
sys.path.append("/usr/share/gcc-4.8/python")
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end

I got entire code from somewhere else for which I no longer have link to. The only edit I did was to replace some previous command to this "sys.path.append("/usr/share/gcc-4.8/python")" which I got from here:

http://stackoverflow.com/questions/26205564/gdb-pretty-printing-importerror-no-module-named-printers

But the crashing still persist.

 $ midori --debug
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt' --return-child-result --args midori
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Vector smash protection is enabled.
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
OpenJDK Server VM (build 24.79-b02, mixed mode)

Program received signal SIGSEGV, Segmentation fault.
0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#0 0xb50eed38 in JSC::JSCell::toNumber(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#1 0xb51591e1 in JSC::JSValue::toNumberSlowCase(JSC::ExecState*) const () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2 0xb51704fa in ?? () from /usr/lib/i386-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3 0x9b88146f in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Now I have honestly no idea what is going on. Some javascript error? Can this be blamed for Soundcloud.com not working on it?

tags: added: libstdcxx
tags: added: javascript
removed: libstdcxx
Revision history for this message
Abdusamed Ahmed (sir508) wrote :

I think the pretty printer error is fixed. Will mark it done but some sites not opening still like Wunderlist. going to report a bug another for it.

Revision history for this message
Abdusamed Ahmed (sir508) wrote :

Close Bug.

Changed in midori:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.