Skip to main content
Known Participant
August 17, 2015
Question

firefox crashes all the time now- Re-Revisited

  • August 17, 2015
  • 3 replies
  • 1483 views

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

Firefox 39.0.3 Crash Report [@ F1398665248_____________________________ ]

  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

    This topic has been closed for replies.

    3 replies

    Steevo1Author
    Known Participant
    June 11, 2016

    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

    Steevo1Author
    Known Participant
    May 15, 2016

    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.

    jeromiec83223024
    Inspiring
    May 16, 2016

    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

    Steevo1Author
    Known Participant
    August 20, 2015

    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
    UUID676fa6be-a5b2-4010-bf5a-224012150820
    Date Processed2015-08-20 14:51:58.482733
    Process Typeplugin Filename:NPSWF32_18_0_0_232.dll
    Uptime3
    Install Age257974 since version was first installed.
    Install Time2015-08-17 15:02:30
    ProductFirefox
    Version40.0.2
    Build ID20150812163655
    Release Channelrelease
    OSWindows NT
    OS Version6.1.7601 Service Pack 1
    Build Architecturex86
    Build Architecture InfoGenuineIntel family 6 model 15 stepping 7 | 8
    Crash ReasonEXCEPTION_BREAKPOINT
    Crash Address0x5079331d
    User Comments
    App Notes
    AdapterVendorID: 0x10de, AdapterDeviceID: 0x0165, AdapterSubsysID: 033410de, AdapterDriverVersion: 9.18.13.908 D3D11 Layers- 
    Processor Notesip-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
    Steevo1Author
    Known Participant
    September 1, 2015

    Jeromie Clark

    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

    jeromiec83223024
    Inspiring
    September 1, 2015

    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.