abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/gtk-gnash -u http://us.js2.yimg.com/us.js.yimg.com/lib/fi/201008171841/us/swf/yfcv3/flashchart.swf -U http://finance.yahoo.com/echarts?s=DHT+Interactive#symbol=DHT;range=5d -x 140509248 -j 780 -k 380 -F 15:16 -P allowscriptaccess=always -P bgcolor=#ffffff -P flashvars=lcId=1295451364097&localeUri=http%3A//us.js2.yimg.com/us.js.yimg.com/lib/fi/201008171841/us/locale/yfcv3/dictionary.xml&chartHost=chartapi.finance.yahoo.com&keyeventsHost=finance.yahoo.com&sigdevsHost=ads.finance.yahoo.com&buildType=prod&state=symbol%3Ddht%3Brange%3D5d%3Bindicator%3Dvolume%3Bcharttype%3Dline%3Bcrosshair%3Don%3Bohlcvalues%3D0%3Blogscale%3Don&source=undefined -P height=380px -P loop=false -P menu=false -P name=test -P pluginspage=http://www.macromedia.com/go/getflashplayer -P src=http://us.js2.yimg.com/us.js.yimg.com/lib/fi/201008171841/us/swf/yfcv3/flashchart.swf -P type=application/x-shockwave-flash -P width=100% -P wmode=opaque - comment: See above .... component: gnash crash_function: extent_tree_ad_s_RB_REMOVE executable: /usr/bin/gtk-gnash kernel: 2.6.35.10-74.fc14.x86_64 package: gnash-1:0.8.8-4.fc14 rating: 4 reason: Process /usr/bin/gtk-gnash was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1295451388 uid: 1110 How to reproduce ----- 1.visited finance.yahoo.com 2.tried to generate a plot on that site, not sure about more details :-/ .... 3.
Created attachment 474298 [details] File: backtrace
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.