Copy link to clipboard
Copied
Jeromie Clark,
OK, I have the flash 18 and firefox 40, which I presume would have the fixes your cohorts devised.
I still have crashes in shockwave flash
The funny thing is, the first crash report I reviewed says Firefox 40.0
I look at the subsequent reports, and they all say
ID: 43fc7890-897b-4d1d-acf7-4e2642150817
Plainly, I do have firefox 40 installed. So that's weird. Really weird.
I am going to restart firefox, which then will run flash OK for a few days.
It's never changed.
bp-dd38045b-4884-4254-a166-ebb7a2150817
8/17/2015 7:51 AM
bp-afb21d56-a5b7-40e7-a2d0-f809f2150817
8/17/2015 7:51 AM
bp-d45ac032-677e-4da5-8c2a-5263b2150817
8/17/2015 7:51 AM
bp-32c2c780-125f-435c-be59-6926c2150817
8/17/2015 7:51 AM
bp-43fc7890-897b-4d1d-acf7-4e2642150817
8/17/2015 7:51 AM
bp-f3805091-043f-4eb0-981e-993312150817
8/17/2015 7:51 AM
bp-f148361a-6f1b-410a-be6f-cb75f2150817
8/17/2015 7:51 AM
bp-2fc063b3-ef34-488e-aa62-353f42150817
8/17/2015 7:51 AM
bp-e373305e-36c9-4170-ab47-bd8ac2150817
8/17/2015 7:51 AM
bp-5ee52b73-718e-4618-beff-d64da2150817
8/17/2015 7:51 AM
bp-21273b3e-5a78-4e32-b0f0-db3ed2150817
8/17/2015 7:51 AM
bp-dca60551-5a95-41c2-b0f7-0d8bc2150817
8/17/2015 7:51 AM
bp-8d217934-e36a-4b02-b601-59fa82150817
8/17/2015 7:51 AM
1ecca42c-a5cc-4347-995e-d07cf8e8a457
8/8/2015 12:13 PM
Copy link to clipboard
Copied
I have the fixes you guys pushed, but I still have the same problem.
It is a little different now. still NPSWF32 crashing, but the crash report is different.
Report ID Date Submitted
bp-676fa6be-a5b2-4010-bf5a-224012150820
8/20/2015 7:51 AM
bp-7283c070-08fe-4195-958c-e8db72150820
8/20/2015 7:51 AM
bp-d1ce69fb-1de4-4192-97b7-35f8e2150820
8/20/2015 7:51 AM
bp-d1a5f309-fce2-416d-869b-5c1c12150820
8/19/2015 5:13 PM
bp-dd38045b-4884-4254-a166-ebb7a2150817
8/17/2015 7:51 AM
bp-afb21d56-a5b7-40e7-a2d0-f809f2150817
8/17/2015 7:51 AM
Signature | F1398665248_____________________________ More Reports Search |
---|---|
UUID | 676fa6be-a5b2-4010-bf5a-224012150820 |
Date Processed | 2015-08-20 14:51:58.482733 |
Process Type | plugin Filename:NPSWF32_18_0_0_232.dll |
Uptime | 3 |
Install Age | 257974 since version was first installed. |
Install Time | 2015-08-17 15:02:30 |
Product | Firefox |
Version | 40.0.2 |
Build ID | 20150812163655 |
Release Channel | release |
OS | Windows NT |
OS Version | 6.1.7601 Service Pack 1 |
Build Architecture | x86 |
Build Architecture Info | GenuineIntel family 6 model 15 stepping 7 | 8 |
Crash Reason | EXCEPTION_BREAKPOINT |
Crash Address | 0x5079331d |
User Comments | |
App Notes | AdapterVendorID: 0x10de, AdapterDeviceID: 0x0165, AdapterSubsysID: 033410de, AdapterDriverVersion: 9.18.13.908 D3D11 Layers- |
Processor Notes | ip-172-31-5-60.1268:2015; MozillaProcessorAlgorithm2015; non-integer value of "SecondsSinceLastCrash"; skunk_classifier: reject - not a plugin hang |
EMCheckCompatibility | True |
Winsock LSP | MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [UDP/IP] : 2 : 2 : MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [TCP/IPv6] : 2 : 1 : MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IPv6] : 2 : 3 : RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll RSVP TCP Service Provider : 2 : 1 : RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 2 : 2 : MSAFD RfComm [Bluetooth] : 2 : 1 : %SystemRoot%\system32\mswsock.dll |
Adapter Vendor ID | 0x10de |
Adapter Device ID | 0x0165 |
Copy link to clipboard
Copied
I still have flashplayer crashes. You said you wanted to look into this since the fixes you pushed didn't fix this for me.
Report ID Date Submitted
bp-23d4afd9-ac20-4d3b-a25f-7a1a72150901
9/1/2015 9:57 AM
bp-7411ffd7-6072-46e5-b9c7-290df2150901
9/1/2015 9:57 AM
bp-c64189f3-7024-4af5-9cdd-e49cb2150901
9/1/2015 9:57 AM
bp-073d64d5-bdcf-4dd3-9bf2-5801d2150901
9/1/2015 9:57 AM
bp-5ef9118b-a9c5-4461-8984-9ec652150901
9/1/2015 9:57 AM
bp-ccb568af-b7c4-4def-8ddf-c160f2150901
9/1/2015 9:57 AM
bp-e1a51ea1-0c56-41f9-9b3d-a8d792150901
9/1/2015 9:57 AM
bp-dadbe9e4-57d8-42fb-8c42-c03ea2150901
9/1/2015 9:57 AM
bp-f804c352-f835-46ad-8852-23d842150901
9/1/2015 9:57 AM
bp-c037c669-7cae-46ce-aff1-da0f62150901
9/1/2015 9:54 AM
bp-9c3e6d40-f1a1-4a0c-981e-9f94a2150901
9/1/2015 8:32 AM
bp-b9d03d0d-5870-41c1-805c-1a2f92150901
8/31/2015 4:19 PM
bp-ac1f296f-fce2-483a-b159-f2b872150901
8/31/2015 4:14 PM
bp-c93f8ec1-7682-4b7a-bd9a-2f3a12150901
8/31/2015 4:14 PM
bp-f071293d-afac-442b-87d0-6515c2150901
8/31/2015 9:56 AM
bp-74c57fe4-9029-42f8-b7ac-ce9ee2150901
8/20/2015 8:23 AM
bp-5aacf780-1020-454f-8ec5-c2cd92150901
8/20/2015 8:06 AM
bp-8e5db193-5b4a-4597-a587-2db9b2150901
8/20/2015 8:04 AM
bp-676fa6be-a5b2-4010-bf5a-224012150820
8/20/2015 7:51 AM
bp-7283c070-08fe-4195-958c-e8db72150820
8/20/2015 7:51 AM
bp-d1ce69fb-1de4-4192-97b7-35f8e2150820
8/20/2015 7:51 AM
bp-d1a5f309-fce2-416d-869b-5c1c12150820
8/19/2015 5:13 PM
bp-dd38045b-4884-4254-a166-ebb7a2150817
8/17/2015 7:51 AM
bp-afb21d56-a5b7-40e7-a2d0-f809f2150817
8/17/2015 7:51 AM
bp-d45ac032-677e-4da5-8c2a-5263b2150817
8/17/2015 7:51 AM
bp-32c2c780-125f-435c-be59-6926c2150817
8/17/2015 7:51 AM
bp-43fc7890-897b-4d1d-acf7-4e2642150817
8/17/2015 7:51 AM
bp-f3805091-043f-4eb0-981e-993312150817
8/17/2015 7:51 AM
bp-f148361a-6f1b-410a-be6f-cb75f2150817
8/17/2015 7:51 AM
bp-2fc063b3-ef34-488e-aa62-353f42150817
8/17/2015 7:51 AM
bp-e373305e-36c9-4170-ab47-bd8ac2150817
8/17/2015 7:51 AM
bp-5ee52b73-718e-4618-beff-d64da2150817
8/17/2015 7:51 AM
Copy link to clipboard
Copied
These are the standard generic crash signature, indicating a hang between Flash and Firefox.
Given that you have big blocks of crashes recorded in the same minute for many of these, I'm imagining you're loading a page with a ton of embedded ads or videos that all fire up simultaneously (news site, etc). That could be a good way to create this kind of race condition.
If it's reproducible, and you're having a lot of problems with a particular page, that would make it pretty straightforward to investigate. I'd be really interested in knowing what the page is.
bp-23d4afd9-ac20-4d3b-a25f-7a1a72150901 9/1/2015 9:57 AM
bp-7411ffd7-6072-46e5-b9c7-290df2150901 9/1/2015 9:57 AM
bp-c64189f3-7024-4af5-9cdd-e49cb2150901 9/1/2015 9:57 AM
bp-073d64d5-bdcf-4dd3-9bf2-5801d2150901 9/1/2015 9:57 AM
bp-5ef9118b-a9c5-4461-8984-9ec652150901 9/1/2015 9:57 AM
bp-ccb568af-b7c4-4def-8ddf-c160f2150901 9/1/2015 9:57 AM
bp-e1a51ea1-0c56-41f9-9b3d-a8d792150901 9/1/2015 9:57 AM
bp-dadbe9e4-57d8-42fb-8c42-c03ea2150901 9/1/2015 9:57 AM
bp-f804c352-f835-46ad-8852-23d842150901 9/1/2015 9:57 AM
The folks at Mozilla are working at bringing sandboxing to 64-bit Firefox at the moment. It's based on the same technology we're using with the 32-bit sandbox, but we had to retrofit it to Firefox at the time, and they're in a much better position to do the work, as they can cleanly integrate it into the browser. Once there's a clear delineation between what's Flash and what's Firefox, it will also make debugging problems much more straightforward.
By and large, these reports aren't actionable, which is why they linger. The data we get from the crash dump doesn't really give us a lot of clues in this particular scenario. I'm pretty excited about the prospect of a standard 64-bit Firefox implementation resolving the majority of this stuff, and there are huge advantages to moving to 64-bit, but we're talking a timeline in months, not days.
In the meantime, if this is getting super frustrating, you might want to consider using an alternate browser.
Copy link to clipboard
Copied
The funny thing is, no, I am not loading anything with a large amount of flash.
In fact, I just looked at the media info on all my open firefox tabs, and there is no page with any flash on it at all.
BTW, I do use adblock plus. I don't see many ads.
I did load my fitbit dashboard, which uses flash for the charts. No animation.
But at the moment all crashed.
I know restarting firefox will allow that to display, but I haven't done it yet.
The biggest problem was facebook, and as I said I quit using that on firefox, now I only use that on chrome.
I have no problems at all with that.
I just loaded this.
Adobe - Test Adobe Shockwave Player
It says the plugin is disabled.
shift-reload does not fix that, but clicking the link below the disabled message does make the flash play.
Well, it played once, then crashed .
That page says crashed. So the only page with flash on it that is open at the moment is the flash test page, which is crashed.
In fact it crashed on that very page. No other pages have flash.
The adobe test page crashed flash. Something else is amiss.
Report ID Date Submitted
bp-8b490ed9-8d91-413a-8952-95ec02150901
9/1/2015 11:26 AM
bp-97b50abb-6fef-407c-83e6-21b992150901
9/1/2015 11:26 AM
bp-8ea7cd67-6811-4b93-b95d-fc75c2150901
9/1/2015 11:26 AM
bp-d17d654f-4d70-44ee-b8a8-4ac142150901
9/1/2015 11:26 AM
bp-4f12ea8f-2ef6-43f2-8c84-28c102150901
9/1/2015 11:26 AM
bp-3d030f46-4590-46de-837c-f8b3a2150901
9/1/2015 11:26 AM
bp-96858ccb-e83d-4cb9-b320-8d6a22150901
9/1/2015 11:26 AM
bp-c93f8ec1-7682-4b7a-bd9a-2f3a12150901
9/1/2015 10:08 AM
Flash just crashed on this adobe page.
Copy link to clipboard
Copied
For the sake of testing, can you try this with a clean Firefox profile?
Use the Profile Manager to create and remove Firefox profiles | Firefox Help
If it persists, can you also go to Help > Restart with Add-Ons Disabled and see if that helps.
I'd like to eliminate those possibilities.
Copy link to clipboard
Copied
Well, restarting firefox normally cures the flash crashes for a few days or even weeks.
Not sure how much time I could devote to that.
I'll look into it.
I just restarted firefox and everything works at the moment.
Copy link to clipboard
Copied
Okay, so it's a situation where memory gets in a bad state at some point and things get flaky. Since Flash is exiting between page loads, you shouldn't see things like that persist, unless the system is just really low on memory. It's most likely something on the Firefox side of the interface, which does stay around to service Flash, gets in a wonky state, then you see a ton of hangs.
For issues like this, we have the same problem that you do. We need to reproduce it a bunch of times in order to full debug it and confirm it as fixed. If it's an issue that takes days or weeks to randomly manifest once, you're talking about a huge engineering effort with no guarantee that you'll even get anything done. We still prioritize these kinds of issues periodically, but they typically come at the expense of a dozen other things we *know* we can fix.
The move on Firefox from 32 to 64-bit will open up a much larger memory address space, which in and of itself stands a good chance of reducing the possibility of collisions. Between that and a revised sandboxing implementation with active participation from Mozilla, I'm optimistic that some of these long-standing stability things are going to disappear.
One of the things you might be running into is that we don't force you to exit Firefox for updates anymore. People really didn't like having to shut down the browser, and we took that to heart, but nothing comes for free. In this case, the trade-off is that you risk being in an inconsistent state where the process that's running in memory doesn't match the version of Flash that's on disk, or you're running some tabs in one version and other tabs (after the next refresh or new tab) in the latest version. Depending on what changed between versions, things can get wonky. You'll definitely want to exit the browser once in a while, particularly on 32-bit.
Copy link to clipboard
Copied
Well, I kind of worked around the problem on my main big computer by using chrome instead of firefox for facebook, and if I did that I never saw this problem. Ever.
It seems the changes you guys made finally trickled down to the releases and I have them on all my systems now.
So I don't really notice this specific problem, with referencing the about:crashes entry for flash.
But now, on all my other systems, three different windows versions, I now get firefox to either stop responding completely, and when I use taskmanager to quit it, I get a message that "plugin container" has crashed. It's when using facebook, still.
So I do not believe what your guys and the firefox people did has resolved this problem at all, but maybe you hid it a little.
Copy link to clipboard
Copied
If you're on a 64-bit system, I'd recommend checking out the 64-bit version of Firefox. It includes a native NPAPI sandbox, which replaces Flash Player's bolt-on sandbox. This is a significant architectural improvement that reduces the overall amount of messaging that happens between Flash and Firefox. Everyone that I've talked to that has switched seems to be happy with the results.
You can get the 64-bit version of Firefox here:
Mozilla Firefox Web Browser — Download Firefox in your language — Mozilla
Copy link to clipboard
Copied
Yeah, I have it on a 64 bit system.
The system I am using today is 32 bit Vista, and it silently crashes.
Plug in container. I have to quit firefox, and then quit what's left of it in task manager, then I restart and it works again.
I just noticed the fb notifications were not coming, that was the only clue that something was amiss.
The notifications on screen were working, the ding plays, but they do not appear on the fb notification icon.
No entry in about crashes, at least some of the time. Well, I have a lot today. Here they are.
I don't think what your engineers did changed anything except maybe hiding the problem, a little.
Report ID Date Submitted
bp-924e521a-e776-48b5-8ae8-c0eb02160611
6/11/2016 9:56 AM
bp-8db33119-3c2e-4ebb-8b19-d84812160611
6/11/2016 9:56 AM
bp-fd9a91d7-2ce9-407a-9fb3-b18772160611
6/11/2016 9:51 AM
bp-19be64c1-9a89-4adc-9ee8-c6fbe2160611
6/11/2016 9:51 AM
bp-92e4714c-335f-49e9-aea7-0fdee2160611
6/11/2016 9:51 AM
bp-f271f947-affa-4ed7-9880-008ca2160611
6/11/2016 9:51 AM
bp-33138a98-9134-4669-813d-9cb462160611
6/11/2016 9:51 AM
bp-ba537025-9e2c-4dce-8ce7-1992c2160611
6/11/2016 9:51 AM
bp-8daf1ca7-35a2-4ba6-90e9-cb3432160611
6/11/2016 9:51 AM
bp-be8a3e0e-e249-42d7-a5fe-4c1f82160609
6/9/2016 1:44 PM