Closed
Bug 625130
Opened 14 years ago
Closed 13 years ago
Firefox 4.0b10pre crash in [@ FlashPlayer-10.6@0x46e11a ][@ @0x0 | FlashPlayer-10.6@0x46e11a ][@ ATIRadeonX2000GLDriver@0xe0f06 ]
Categories
(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marcia, Unassigned)
References
Details
(Keywords: crash, reproducible)
Crash Data
Seen while running Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b10pre) Gecko/20110112 Firefox/4.0b10pre
STR:
1. Go to youtube.com
2. Load a HD video such as http://www.youtube.com/watch?v=-zvCUmeoHpw
3. Pop the video out.
4. Press the play button in the popped out video. Then ESC.
5. Return to the original video and click on it.
Reports:
http://crash-stats.mozilla.com/report/index/bp-8dc619bd-7c1b-4281-8569-afe3c2110112
http://crash-stats.mozilla.com/report/index/fead41af-2684-4e55-97d8-c07cc2110112
Flash version:
File: Flash Player.plugin
Version: 10.2.152.14
Shockwave Flash 10.2 r152
Signature FlashPlayer-10.6@0x46e11a
UUID 8dc619bd-7c1b-4281-8569-afe3c2110112
Process Type plugin Version: Filename: Flash Player.plugin
Time 2011-01-12 11:26:17.856202
Uptime 22
Install Age 5881 seconds (1.6 hours) since version was first installed.
Product Firefox
Version 4.0b10pre
Build ID 20110112033217
Branch 2.0
OS Mac OS X
OS Version 10.6.6 10J567
CPU x86
CPU Info family 6 model 23 stepping 6
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Crash Address 0xffffffffe5fe19e5
User Comments
App Notes Renderers: 0x21a00,0x20400
Processor Notes
EMCheckCompatibility False
Bugzilla - Report this Crash
Related Bugs
Crashing Thread
Frame Module Signature [Expand] Source
0 @0xe5fe19e5
1 FlashPlayer-10.6 FlashPlayer-10.6@0x46e11a
2 FlashPlayer-10.6 FlashPlayer-10.6@0x28eec8
3 FlashPlayer-10.6 FlashPlayer-10.6@0x46fa5e
4 FlashPlayer-10.6 FlashPlayer-10.6@0x457bdf
5 FlashPlayer-10.6 FlashPlayer-10.6@0x45d2f4
6 FlashPlayer-10.6 FlashPlayer-10.6@0x653376
7 FlashPlayer-10.6 FlashPlayer-10.6@0x64c1c1
8 FlashPlayer-10.6 FlashPlayer-10.6@0x64fea0
9 FlashPlayer-10.6 FlashPlayer-10.6@0x651786
10 FlashPlayer-10.6 FlashPlayer-10.6@0x37a2e6
11 FlashPlayer-10.6 FlashPlayer-10.6@0x4da230
12 FlashPlayer-10.6 FlashPlayer-10.6@0x4e4884
13 FlashPlayer-10.6 FlashPlayer-10.6@0x4e23cc
14 FlashPlayer-10.6 FlashPlayer-10.6@0x4501aa
15 XUL mozilla::plugins::PluginInstanceChild::AnswerNPP_Destroy dom/plugins/PluginModuleChild.h:356
16 XUL mozilla::plugins::PPluginInstanceChild::OnCallReceived PPluginInstanceChild.cpp:1681
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-flash
Version: Trunk → 10.x
Reporter | ||
Comment 2•14 years ago
|
||
[@ @0x0 | FlashPlayer-10.6@0x46e11a ] is another stack I get when I follow the STR in Comment 0. Still fairly easy to repro with the latest trunk nightly.
Comment 3•14 years ago
|
||
With the combined Flash signatures only, it is #26 top crasher on Mac OS X in 4.0b10 over the last week.
Summary: Firefox 4.0b10pre crash in [@ FlashPlayer-10.6@0x46e11a ] [@ ATIRadeonX2000GLDriver@0xe0f06 ] → Firefox 4.0b10pre crash in [@ FlashPlayer-10.6@0x46e11a ][@ @0x0 | FlashPlayer-10.6@0x46e11a ][@ ATIRadeonX2000GLDriver@0xe0f06 ]
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ FlashPlayer-10.6@0x46e11a ]
[@ @0x0 | FlashPlayer-10.6@0x46e11a ]
[@ ATIRadeonX2000GLDriver@0xe0f06 ]
Reporter | ||
Comment 4•13 years ago
|
||
Resolving this as WFM as there are no current crashes with these stacks. Will reopen if something reappears.
Status: NEW → RESOLVED
Crash Signature: [@ FlashPlayer-10.6@0x46e11a ]
[@ @0x0 | FlashPlayer-10.6@0x46e11a ]
[@ ATIRadeonX2000GLDriver@0xe0f06 ] → [@ FlashPlayer-10.6@0x46e11a ]
[@ @0x0 | FlashPlayer-10.6@0x46e11a ]
[@ ATIRadeonX2000GLDriver@0xe0f06 ]
Closed: 13 years ago
Resolution: --- → WORKSFORME
Comment 5•9 years ago
|
||
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 10.x → unspecified
Updated•2 years ago
|
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•