| Summary: | [abrt] firefox-3.6.15-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dpw818 | ||||
| Component: | firefox | Assignee: | Gecko Maintainer <gecko-bugs-nobody> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | ericsword, gecko-bugs-nobody | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:96b3713c0c91898c7db5c6bb20f3d0410d032708 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-07 13:17:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
dpw818
2011-03-17 23:26:07 UTC
Created attachment 486121 [details]
File: backtrace
Package: firefox-3.6.15-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Firefox open with many tabs for ~1 day. Had played at least one flash-based screen cast during that time. Put computer to sleep for night and woke it the next morning with FF still running. 2. Opened new tab with an audio podcast (mp3). Listened to ~20 minutes of it. Url is: http://hansamann.podspot.de/files/grails_podcast_episode_120.mp3 3. Clicked to close the tab while podcast was still going. 4. Tab containing podcast did not close. FF appeared to lock up. 5. Clicked to close tab again. FF crashed. We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky). Thanks! |