Closed Bug 830982 Opened 13 years ago Closed 9 years ago

Flash 11.5.502.146 crashes with FF 19

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Version:
19 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: keepitsimplestupid, Unassigned)

Details

(Keywords: hang)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130109111322 Steps to reproduce: This bug has been around for a LONG TIME and The Mozilla site: http://support.mozilla.org/en-US/kb/adobe-flash-plugin-has-crashed recommends downgrading to 10.3 So it's still not fixed. Actual results: Message "the Adobe Flash Player has crashed" . Send Crash report. It's very annoying when say watching a program on www.cwtv.com and it crashes during the last commercial segment. You then have to listen to ALL of the commercials to the crash point. That particular website does have lots of commercials. Upgrading to the latest Flash Player to fix security issues and downgrading to 10.3 are 180 degrees apart. The last crash did happen when the website returned to the main program from a commercial. Not sure if it could be related, but at times Flash Player resizes the window from Full screen to small when a commercial plays and then it stays that way.
Can you please post the crash ID from about:crashes ?
I get "unresponsive script" when I go about:crashes even when I continue.
Which slow script is reported in the dialog ? (you can copy+paste it) Please try a new profile: http://support.mozilla.org/kb/Managing%20profiles
I'll bet I discovered a new bug. when there are no crash reports "about:crashes" hangs. I doubt I submitted a crash report for the last crash. The URL shown is "chrome://global/content/crashes.js:133 No crash reports are shown. Another profile thats been set up for testing purposes does the same.
Sorry, my fault. Crash reports are shared between the profiles :-( I thought that you had for some unknown reasons too many or corrupted reports in that folder but I thought a new profile would use a different folder. That is course wrong. Please open about:support, there is a button to show the profile folder. It should open a explorer window with the profile folder : C:\Users\Matti\AppData\Roaming\Mozilla\Firefox\Profiles\91oytk9g.default from this point go 2 levels down to: C:\Users\Matti\AppData\Roaming\Mozilla\Firefox\ The crash reports are inside the Crash Reports folder. Do you have many crash reports there ? Delete the whole folder and let Firefox crash again. The about:crashes page should work now.
I removed about 180 crashes and about:crashes still doesn't work. I guess, I'll have to remove all of them and start from scratch. The 1/15/2013 is probably the last Adobe crash ID from last night: bp-78841bf2-dea0-438c-ab13-35ca42130115 1/15/2013 bp-4be7eed5-d1fa-4793-b555-ddc022130114 1/13/2013 bp-1bc46243-60f3-4066-9a75-a7ef92130103 1/02/2013 bp-288bd2ac-10fd-4679-9e77-c8ac92130102 1/2/2013 I can't guarantee that the Jan 13 or 2 files are from Adobe. These were in the submitted folder. The properties for the "pending" folder lists 69,001 files. It's 2.28 GB big. I guess that's what I've been unhappy with Firefox?
The 2.1GB explains why you got a hang in about:crashes :-( I can't explain that amount of crash reports except if you have an old Netscape ActiveX plugin installed that crashed several times in the background if you accessed on single page. We blocked that plugin a few months ago. Anyway, your crash report from the 15 Jan looks like the same hang that the user in bug 830786 reported. Can you try to disable the protected mode in flash ? Scroll down to "last resort": http://forums.adobe.com/message/4468493
Severity: normal → critical
Crash Signature: [@ hang | WaitForMultipleObjectsEx | RealMsgWaitForMultipleObjectsEx | MsgWaitForMultipleObjects | F_1152915508___________________________________ ]
Component: Untriaged → Plug-ins
Keywords: hang
Product: Firefox → Core
In my case Firefox did not hang. Disabling Protected Mode looks dooable. I'll try to clear ALL of the crash reports.
All Crash reports Cleared. Can now access about:crashes Protected Mode Disabled with the help of "Take Ownership" Now all we have to do is wait.
Ok, I disabled protected mode, but it did not take effect until the system was re-booted. I checked for the existence of the container in the task manager. When the container existed and you killed the container, the Adobe Plug-in crashed. This URl https://dl.dropbox.com/u/95157096/85f61cf7/f3d6ffe9.html was suggested as a test case for the hang. there was no container in the Task Manager so I'm confident that Protected mode was disabled. This does create a hang to the point that I was unable to type something using the bug submission page. The hang "sort of" resolved on it's own, at least in Adobe. It MAY have required the attention of the Task Manager to resolve in FF or I just needed to wait. The crash ID for the protected mode disabled is: bp-d5a6644a-0820-42b4-abac-70ed32130116 Is this the same as my earlier crash? Another odd thing, all of the pending crashes seemed to have come back when I did a restore last session so the script stalled in about:crashes. Should this have happened? Firefox says that it cannot be undone. I got the crash ID the hard way. The Submitted folder only had two Crash ID's in it like I expected. So, I still will have to see if the bug appears when I watch cwtv.
>Is this the same as my earlier crash? No, that looks like the Adobe plugin opened a dialog box maybe a slow script warning ? >Another odd thing, all of the pending crashes seemed to have come back when I did a >restore last session so the script stalled in about:crashes. You have probably deleted the pending crash reports while Firefox was open. You should clear the list of crash reports in about:crashes and everything should be fine. Note: The issue itself is a hang caused by the flash plugin. It's very likely that this can only be fixed by Adobe.
It turns out that delete crash reports doesn't delete the pending reports and the bug is assigned. Thanks. OK, so I'll have to do some watching and see if the problem occurs then. The dropbox URL thing is a separate problem. Again, thanks.
It really looks like disabling protected mode fixed this bug. I'd need more use time to know for sure. It also seemed to fix a side-effect: The crashes generally happened when the "commercials" appeared or went back to normal. At times the video would go to reduced-size mode when a commercial came on and would not go back to full screen. This seems to be gone too.
Well, protected mode didn't fix the Flash Crashes. The latest Crash ID's are: 08d01c03-ccfb-40f2-89a6-87dd9aaac8d1-browser 08d01c03-ccfb-40f2-89a6-87dd9aaac8d1
When I click on the first ID, I see throttling in the URL. When I click on the second, I get it may be in the queue.
I'm marking this bug as WORKSFORME as bug crashlog signature didn't appear from a long time (over half year).
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.