Bug 621442

Summary: [abrt] crash in midori-0.2.6-1.fc13: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: dedanna <skeeter1029>
Component: midoriAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: maxamillion, peter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:1db71506026bb96f810e9ea3c6769019b0cc5d37
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-29 19:40:45 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 dedanna 2010-08-05 04:10:26 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: midori
comment: All said in "How to reproduce"
component: midori
crash_function: parentCrossingShadowBoundaries
executable: /usr/bin/midori
global_uuid: 1db71506026bb96f810e9ea3c6769019b0cc5d37
kernel: 2.6.33.3-85.fc13.i686
package: midori-0.2.6-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Load Midori
2. Surf the web, pull up more than 2 tabs
3. Midori crashes, no explanation, for no reason.
Comment 1 dedanna 2010-08-05 04:10:30 UTC 
Created attachment 436733 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-08-29 19:40:45 UTC 
This looks very similar to the issue in bug 598947. 

Moving it over there for further debug and input.

*** This bug has been marked as a duplicate of bug 598947 ***