Bug 600698

Summary: [abrt] crash in midori-0.2.6-1.fc12: malloc_consolidate: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Simon.D <sd2310>
Component: midoriAssignee: Peter Gordon <peter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: den.mail, frederic.hancart, jade-mail, kevin, maxamillion, melanphos, oliverlake, peter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:767de9f695f39233bde49fa7f120158e17a7c7ae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:01:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Simon.D 2010-06-05 16:58:14 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: midori
component: midori
crash_function: malloc_consolidate
executable: /usr/bin/midori
global_uuid: 767de9f695f39233bde49fa7f120158e17a7c7ae
kernel: 2.6.32.12-115.fc12.x86_64
package: midori-0.2.6-1.fc12
rating: 4
reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Simon.D 2010-06-05 16:58:17 UTC
Created attachment 421454 [details]
File: backtrace

Comment 2 Jason Elwell 2010-07-04 17:46:55 UTC
Package: midori-0.2.6-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. start app from X/Gnome icon
2. watch app disappear
3.


Comment
-----
app will work fine from gnome terminal

Comment 3 Jason Elwell 2010-07-04 17:49:30 UTC
Package: midori-0.2.6-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. started app and it crashed before use
2.
3.

Comment 4 Dag 2010-07-13 15:38:00 UTC
Package: midori-0.2.6-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. I start Midori (click on the icon in the "internet" applications' sub-menu)
2. it displays a message saying that Midori seems to have terminated unexpectedly during the last use and let the user with 3 buttons (only "Modify  preferences" is enabled) and a 4th to Valid
3. I tried to Modify preferences, then Valid
4. When I click on Valid, it displays a white window for a short time then disappears: crash. It does that no matter what I change in the preferences.


Comment
-----
Well, it crashes everytime I try to launch it.
I deleted everything in ~/.config/midori but it still crashed.
The only difference launching Midori right after having deleted Midori conf dir, is that it doesn't show the window saying it seems midori terminated unexpectedly.

Comment 5 Dag 2010-07-13 15:41:10 UTC
Package: midori-0.2.6-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. I start Midori (click on the icon in the "internet" applications' sub-menu)
2. it displays a message saying that Midori seems to have terminated
unexpectedly during the last use and let the user with 3 buttons (only "Modify 
preferences" is enabled) and a 4th to Valid
3. I tried to Modify preferences, then Valid
4. When I click on Valid, it displays a white window for a short time then
disappears: crash. It does that no matter what I change in the preferences.

Comment
-----
Well, it crashes everytime I try to launch it.
I deleted everything in ~/.config/midori but it still crashed.
The only difference launching Midori right after having deleted Midori conf
dir, is that it doesn't show the window saying it seems midori terminated
unexpectedly.

Comment 6 Kevin Fenzi 2010-08-28 22:55:27 UTC
This looks related to the openjdk java plugin. 

Can everyone here try: 

1. Upgrade to the latest available midori and java-1.6.0-openjdk-plugin packages and see if the crashes persist. (ie, 'yum update')

2. If they do not, try removing the java-1.6.0-openjdk-plugin package and see if the crashes stop. 

Feedback welcome.

Comment 7 Kevin Fenzi 2010-08-28 23:08:25 UTC
*** Bug 592642 has been marked as a duplicate of this bug. ***

Comment 8 Kevin Fenzi 2010-08-28 23:12:07 UTC
*** Bug 600956 has been marked as a duplicate of this bug. ***

Comment 9 Kevin Fenzi 2010-08-28 23:12:25 UTC
*** Bug 605184 has been marked as a duplicate of this bug. ***

Comment 10 Kevin Fenzi 2010-08-28 23:12:41 UTC
*** Bug 611259 has been marked as a duplicate of this bug. ***

Comment 11 Kevin Fenzi 2010-08-28 23:13:24 UTC
*** Bug 611709 has been marked as a duplicate of this bug. ***

Comment 12 Kevin Fenzi 2010-08-29 00:15:01 UTC
*** Bug 611248 has been marked as a duplicate of this bug. ***

Comment 13 Kevin Fenzi 2010-08-29 00:16:56 UTC
*** Bug 620654 has been marked as a duplicate of this bug. ***

Comment 14 Dag 2010-09-04 16:30:53 UTC
Hi Kevin,

I tested Midori again :
midori-0.2.6-1.fc13.x86_64

without the Java-1.6.0-OpenJDK-plugin everything goes well.



Then I installed:
java-1.6.0-openjdk-1.6.0.0-42.b18.fc13.x86_64
java-1.6.0-openjdk-plugin-1.6.0.0-42.b18.fc13.x86_64

Then I searched for java applet websites:
http://www.dgp.toronto.edu/~mjmcguff/learn/java/
http://www.java.com/fr/download/installed.jsp

Those 2 web sites triggered the kill by SIGNAL 11 (SIGSEGV) issue when trying to execute a java applet.

If there is no java applet on the page, everything is OK until a java applet is executed.



I hope this will be useful.

Bye for now.

Comment 15 Bug Zapper 2010-11-03 13:32:45 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Jason Elwell 2010-11-26 15:36:57 UTC
No longer an issue. Thanks for the fix.

Comment 17 Bug Zapper 2010-12-03 14:01:40 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.