Bug 13791

Summary: Midori crash
Product: Mageia Reporter: eric lamaze <lameri>
Component: RPM PackagesAssignee: Cesar Vargas <cvargas>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: cvargas, jani.valimaa, marja11, rverschelde
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
URL: https://bugs.launchpad.net/midori/+bug/1347545
See Also: https://bugs.mageia.org/show_bug.cgi?id=14934
Whiteboard:
Source RPM: midori-0.5.8-1.mga5.i586 CVE:
Status comment:
Attachments: terminal's trace of my midoris's crash
running on gdb
debug-install

Description eric lamaze 2014-07-23 12:27:33 CEST
Hi,
I am trying to use midori in mageia 5 586 but it crash:

[...]
#15 0xb478f777 in callToJavaScript () from /lib/libjavascriptcoregtk-1.0.so.0
#16 0xaad99900 in ?? ()
#17 0xb472d23a in JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () from /lib/libjavascriptcoregtk-1.0.so.0
Cannot access memory at address 0xadc4501c

$ midori --version
Gtk-Message: Failed to load module "canberra-gtk-module"
Midori 0.5.8 ((null)) Midori
GTK+ 2.24.22 (2.24.24)	Glib 2.40.0 (2.41.2)
WebKitGTK+ 2.4.0 (2.4.4)	libSoup 2.46.0
cairo 1.12.16 (1.12.16)	libnotify 0.7.6
gcr No	granite No

https://bugs.launchpad.net/midori/+bug/1347545

Full trace above in attachement.

Reproducible: 

Steps to Reproduce:
Comment 1 eric lamaze 2014-07-23 12:28:26 CEST
Created attachment 5308 [details]
terminal's trace of my midoris's crash
Comment 2 Jani Välimaa 2014-07-23 16:24:56 CEST
Does it crash randomly or can you easily reproduce the crash by surfing to some particular site/address?

CC: (none) => jani.valimaa

Comment 3 eric lamaze 2014-07-23 17:49:30 CEST
Crash on google, youtube, hardware.Fr(javascript?) but not duckduckandgo,nofrag.com...
Comment 4 Jani Välimaa 2014-07-23 18:00:44 CEST
Can't reproduce. Please test if crash also happens with latest release -2.mga5.
Comment 5 eric lamaze 2014-07-23 19:38:43 CEST
same problem.
Comment 6 Jani Välimaa 2014-07-23 19:49:06 CEST
Please enable Debug media and do 'debuginfo-install midori-0.5.8-2.mga5.i586' as root and try to get backtrace again with debug symbols installed. Run midori also directly via gdb to see missing debug pkgs.

Is there any page where Midori always crashes? If yes, which?
Comment 7 eric lamaze 2014-07-23 21:24:49 CEST
Created attachment 5311 [details]
running on gdb
Comment 8 eric lamaze 2014-07-23 21:26:05 CEST
Created attachment 5312 [details]
debug-install
Comment 9 eric lamaze 2014-07-23 21:27:38 CEST
Always crash on google.
Comment 10 Jani Välimaa 2014-07-23 21:43:18 CEST
(In reply to eric lamaze from comment #9)
> Always crash on google.

So, you just surf to http://www.google.com and midori crashes? Or do you need to type something or do something else?
Comment 11 Jani Välimaa 2014-07-23 21:48:13 CEST
(In reply to eric lamaze from comment #8)
> Created attachment 5312 [details]
> debug-install

Unfortunately this doesn't help much. Please install also other debug pkgs mentioned in comment 7 (copy paste the command to cmd).
Jani Välimaa 2014-07-23 21:49:01 CEST

Attachment 5312 mime type: application/octet-stream => text/plain

Comment 12 eric lamaze 2014-07-24 15:24:17 CEST
# gdb midori
GNU gdb (GDB) 7.7.1-1.mga5 (Mageia release 5)
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-mageia-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...

warning: /etc/gdbinit.d/gdb-heap.py: Aucun fichier ou dossier de ce type
Reading symbols from midori...Reading symbols from /usr/lib/debug/usr/bin/midori.debug...done.
done.
(gdb) r
Starting program: /usr/bin/midori 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i686/libthread_db.so.1".
warning: the debug information found in "/usr/lib/debug/usr/lib/libjpeg.so.8.0.2.debug" does not match "/lib/libjpeg.so.8" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug//usr/lib/libjpeg.so.8.0.2.debug" does not match "/lib/libjpeg.so.8" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib//libjpeg.so.8.0.2.debug" does not match "/lib/libjpeg.so.8" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib/libuuid.so.1.3.0.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug//usr/lib/libuuid.so.1.3.0.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib//libuuid.so.1.3.0.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).

[New Thread 0xb3272b40 (LWP 6720)]
Gtk-Message: Failed to load module "canberra-gtk-module"
[New Thread 0xb26f1b40 (LWP 6723)]
[New Thread 0xb1dc2b40 (LWP 6724)]
[Thread 0xb1dc2b40 (LWP 6724) exited]
[New Thread 0xb1dc2b40 (LWP 6726)]
[New Thread 0xb13ffb40 (LWP 6727)]
[Thread 0xb13ffb40 (LWP 6727) exited]
warning: the debug information found in "/usr/lib/debug//usr/lib/gio/modules/libdconfsettings.so.debug" does not match "/usr/lib/gio/modules/libdconfsettings.so" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib/gio/modules/libdconfsettings.so.debug" does not match "/usr/lib/gio/modules/libdconfsettings.so" (CRC mismatch).

[New Thread 0xb13ffb40 (LWP 6730)]
[New Thread 0xb021fb40 (LWP 6735)]
[New Thread 0xafa1eb40 (LWP 6736)]
[Thread 0xafa1eb40 (LWP 6736) exited]
[New Thread 0xaf20bb40 (LWP 6738)]
[New Thread 0xafa1eb40 (LWP 6739)]
[Thread 0xb021fb40 (LWP 6735) exited]
[New Thread 0xb021fb40 (LWP 6742)]
[New Thread 0xae9dbb40 (LWP 6743)]
[Thread 0xb021fb40 (LWP 6742) exited]
[Thread 0xafa1eb40 (LWP 6739) exited]
Detaching after fork from child process 6746.
Detaching after fork from child process 6747.
[New Thread 0xafa1eb40 (LWP 6750)]

/* I enter url here (google.fr) an crash*/

(midori4:6706): LibZeitgeist-CRITICAL **: Failed to create proxy for Zeitgeist daemon: La connexion est fermée

Program received signal SIGILL, Illegal instruction.
0xadd0be35 in ?? ()
Missing separate debuginfos, use: debuginfo-install dconf-0.20.0-1.mga5.i586 libjpeg8-1.3.0-3.mga4.i586 libuuid1-2.24.2-1.mga5.i586
Comment 13 eric lamaze 2014-07-24 15:35:24 CEST
Midori's Preferences 
> activate scripts
> Unactived
= no crash

so maybe probleme is in /lib/libjavascriptcoregtk-1.0.so.0 ?
Comment 14 Jani Välimaa 2014-07-24 17:13:48 CEST
Maybe. Could you test which plugin causes the crash?
Comment 15 eric lamaze 2014-07-24 19:51:10 CEST
I tested whithout javascript and no have crash (desactived scripts in preference of midori) but I don't use extensions in midori
Comment 16 Rémi Verschelde 2014-09-17 14:44:45 CEST
Do you still have the same issue on current cauldron Eric?

CC: (none) => remi

Comment 17 eric lamaze 2014-09-18 18:03:33 CEST
Sry, i can't test this now, system is down cause hardware idont know how many time :(
Comment 18 eric lamaze 2014-09-18 18:07:09 CEST
Sry, i can't test this now, system is down cause hardware idont know how many time :(
Comment 19 Rémi Verschelde 2015-01-02 22:12:25 CET
CC'ing vaci0.

CC: (none) => cvargas

Samuel Verschelde 2015-05-21 11:53:06 CEST

Keywords: (none) => NEEDINFO

Samuel Verschelde 2015-05-21 11:55:12 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=14934

Samuel Verschelde 2015-05-21 11:55:27 CEST

Assignee: bugsquad => cvargas

Comment 20 Cesar Vargas 2016-10-25 16:24:31 CEST
Eric, Do you still have the same issue on current cauldron?
Comment 21 Marja Van Waes 2021-05-27 11:17:16 CEST
(In reply to Cesar Vargas from comment #20)
> Eric, Do you still have the same issue on current cauldron?

He reported the issue almost 7 years ago and reported a few months later that he couldn't test because his hardware was down. We haven't heard of him since. Closing

CC: (none) => marja11
Resolution: (none) => OLD
Status: NEW => RESOLVED