| Summary: | [abrt] gnash-1:0.8.8-4.fc14: extent_tree_ad_s_RB_REMOVE: Process /usr/bin/gtk-gnash was killed by signal 11 (SI) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | William A. Mahaffey III <wam> | ||||
| Component: | gnash | Assignee: | Hicham HAOUARI <hicham.haouari> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | denis.arnaud_fedora, jreznik, kevin, pertusus | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:94973b8c4c08f4df3e5f7da02218bf5f59321f3a | ||||||
| Fixed In Version: | gnash-0.8.9-1.fc13 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-03-18 03:59:51 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
William A. Mahaffey III
2011-01-19 15:35:08 UTC
Created attachment 474298 [details]
File: backtrace
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Is this crash reproducible ? I am not entirely sure :-/ .... Can you duplicate from the crash-report info ? Try this URL: http://finance.yahoo.com/q?s=ISH,TNP,DHT,^GSPC&d=s, then click on 1 of the links below 1 of the plots, to look at a plot for a period other than 1 day, that's where this came from. I had a flurry of these (gnash crashes), all submitted by the abrt daemon, over a period of weeks. I mostly don't recall exactly what triggered them, I sorta hoped the automatically generated report would be detailed enough .... In all cases (IIRC) I was surfing & wound up looking at video, often YouTube or FoodTV, but not always .... I realize that ain't much help, but it's all I got .... I have had a few other sporadic crashes which got auto-reported, almost always classified as a new bug, when in fact I suspect they should have *all* been duplicates of an existing bug somewhere, maybe this one. I have yum-upgraded a couple of times since, maybe it got fixed ???? P.S. try clicking on the '5-day' link under the DHT daily plot, that is where the failure occured in this report & that's how I got there, click on the link in the last message to get 4 plots/quotes on the screen, then try to get the 5-day plot for stock symbol 'DHT' .... HTH .... We are gonna disable jemalloc for next release since it seems to cause lot of memory allocation issues. gnash-0.8.9-0.1.20110312git.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gnash-0.8.9-0.1.20110312git.fc14 gnash-0.8.9-0.1.20110312git.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gnash-0.8.9-0.1.20110312git.fc13 gnash-0.8.9-0.1.20110312git.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gnash-0.8.9-0.1.20110312git.fc15 gnash-0.8.9-0.1.20110312git.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. gnash-0.8.9-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gnash-0.8.9-1.fc14 gnash-0.8.9-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gnash-0.8.9-1.fc13 gnash-0.8.9-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. gnash-0.8.9-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |