Skip navigation
Currently Being Moderated

Flash Player      11.3.300.257 causes Exception Access Violation in Firefox 13

Jun 8, 2012 2:19 PM

I downloaded the latest version of flash player -- 11.3.300.257 -- and noticed a few odd things.

 

First of all there are two incidents of "FlashPlayerPlugin_11_3_300_257.exe" running in my Windows 7 task manager whenever I use an application with fash content.

 

More important, I happend to look at my Firefox 13 crash reporter and noticed that it had filed a crash report every time I closed out the program since updating the Flash Player.  Prior to that, it had not crashed before.  All told, there were about a dozen crash reports, and they were all identical, with the exception of the incident numbers, etc.

 

Specifically, here is what the report says:

 

 

Signature LdrShutdownProcess More Reports Search

UUID     ea3ee1ce-e26e-42cd-bda5-9ad802120608

Date Processed     2012-06-08 20:58:56

Uptime     0

Install Age     3.2 days since version was first installed.

Install Time     2012-06-05 17:02:27

Product     Firefox

Version     13.0

Build ID     20120601045813

Release Channel     release

OS     Windows NT

OS Version     6.1.7601 Service Pack 1

Build Architecture     x86

Build Architecture Info     GenuineIntel family 6 model 42 stepping 7

Crash Reason     EXCEPTION_ACCESS_VIOLATION_EXEC

Crash Address     0x68d09903

User Comments

App Notes

 

AdapterVendorID: 0x8086, AdapterDeviceID: 0x0102, AdapterSubsysID: 2ac3103c, AdapterDriverVersion: 8.15.10.2462

 

Processor Notes      Priority Job

EMCheckCompatibility     True

Winsock LSP

 

MSAFD Tcpip [TCP/IP] : 2 : 1 : 

MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll

MSAFD Tcpip [RAW/IP] : 2 : 3 : 

MSAFD Tcpip [TCP/IPv6] : 2 : 1 : %SystemRoot%\system32\mswsock.dll

MSAFD Tcpip [UDP/IPv6] : 2 : 2 : 

MSAFD Tcpip [RAW/IPv6] : 2 : 3 : %SystemRoot%\system32\mswsock.dll

RSVP TCPv6 Service Provider : 2 : 1 : 

RSVP TCP Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll

RSVP UDPv6 Service Provider : 2 : 2 : 

RSVP UDP Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll

 

Adapter Vendor ID

Adapter Device ID

--------------------------------------------------------------

 

RAW DUMP (whatever that means) --

 

 

OS|Windows NT|6.1.7601 Service Pack 1 CPU|x86|GenuineIntel family 6 model 42 stepping 7|2 Crash|EXCEPTION_ACCESS_VIOLATION_EXEC|0x68d09903|0 Module|plugin-container.exe|13.0.0.4535|plugin-container.pdb|9C926C46 B24D40D2A0BC60A8C08F9E542|0x010c0000|0x010c5fff|1 Module|msvcp100.dll|10.0.30319.1|msvcp100.i386.pdb|CE550582BFCA474A83 21ECC0CE61C54C1|0x60210000|0x60278fff|0 Module|xul.dll|13.0.0.4535|xul.pdb|BCDADA8102EF4787BA380AD9EADDFD182| 0x60280000|0x611d6fff|0 Module|mozjs.dll||mozjs.pdb|EBBD620BFB9745549057DE0D37E17A332|0x611e0 000|0x613d3fff|0 Module|nss3.dll|3.13.4.0|nss3.pdb|29A53C184AE04EA385678451314758AE1|0 x613e0000|0x6147dfff|0 Module|mozsqlite3.dll|3.7.10.0|mozsqlite3.pdb|2237F1E8CBFC4C61996FBC6 1DF7A7ED32|0x61480000|0x6154cfff|0 Module|msvcr100.dll|10.0.30319.1|msvcr100.i386.pdb|B74A49314FD64956BA F50772F83598012|0x61550000|0x6160dfff|0 Module|smime3.dll|3.13.4.0|smime3.pdb|F808F592C48D49C5BE348F3A9FDA816 81|0x61630000|0x61647fff|0 Module|ssl3.dll|3.13.4.0|ssl3.pdb|00470A9303F7418B88B058A05751791E1|0 x61650000|0x61674fff|0 Module|nssutil3.dll|3.13.4.0|nssutil3.pdb|973070F8806A4A7185CC3192F9C D62611|0x616b0000|0x616c7fff|0 Module|mozalloc.dll|13.0.0.4535|mozalloc.pdb|C0FC6C9BDAEF4F3384108A35 C8F3187A2|0x65cf0000|0x65cf5fff|0 Module|nspr4.dll|4.9.0.0|nspr4.pdb|FA51334D0E2F4763B834E29949BC2ED42| 0x65d10000|0x65d3bfff|0 Module|plds4.dll|4.9.0.0|plds4.pdb|E2EC23C09A0E4BBF86CCAB921A1E88FA2| 0x65d40000|0x65d46fff|0 Module|plc4.dll|4.9.0.0|plc4.pdb|B0FD4135D3E74EDEA0E29C7C7E6DF4C72|0x 65d50000|0x65d56fff|0 Module|mozglue.dll|13.0.0.4535|mozglue.pdb|24C2A56D2FC34B679916C9510E D6B1B12|0x65d60000|0x65d6cfff|0 Module|ntshrui.dll|6.1.7601.17755|ntshrui.pdb|B1397869A4914797AEA1040 E4BD4F1932|0x684b0000|0x6851ffff|0 Module|winmm.dll|6.1.7601.17514|winmm.pdb|7AFD98FCAAD34F6B8B31A4667C4 E2BFC2|0x68520000|0x68551fff|0 Module|slc.dll|6.1.7600.16385|slc.pdb|8728388BE5444934AA1B81ADF065B0E 41|0x685d0000|0x685d9fff|0 Module|powrprof.dll|6.1.7600.16385|powrprof.pdb|B1F8F66CCBAD4869BADFD 20C1F24AC832|0x685e0000|0x68604fff|0 Module|dsound.dll|6.1.7600.16385|dsound.pdb|F38F478065E247C68EDA69960 6F56EED2|0x68610000|0x68681fff|0 Module|cscapi.dll|6.1.7601.17514|cscapi.pdb|CC82DBD0C27D422C8E970BD83 ECE179F2|0x6f930000|0x6f93afff|0 Module|uxtheme.dll|6.1.7600.16385|wuxtheme.pdb|20C669C0018E406295BFA5 6B7C93850F2|0x70590000|0x7060ffff|0 Module|apphelp.dll|6.1.7601.17514|apphelp.pdb|F442BEDCC0F646D3840D298 98C5899CB2|0x71fe0000|0x7202bfff|0 Module|wsock32.dll|6.1.7600.16385|wsock32.pdb|0AAE6683A7F540DFB265DCD 12B7BD0FB2|0x72330000|0x72336fff|0 Module|winnsi.dll|6.1.7600.16385|winnsi.pdb|F7A0C25B1B0E4FA6876494D3F 6BFD1012|0x72340000|0x72346fff|0 Module|IPHLPAPI.DLL|6.1.7601.17514|iphlpapi.pdb|F162D2E137ED42978BF38 C99AEE2DAAB2|0x72350000|0x7236bfff|0 Module|srvcli.dll|6.1.7601.17514|srvcli.pdb|B83FAA07A5A644DEAF314DD74 6429E092|0x725e0000|0x725f8fff|0 Module|netutils.dll|6.1.7601.17514|netutils.pdb|5B6CAE02A29D4364ADC01 2962BE6A6552|0x72600000|0x72608fff|0 Module|ntmarta.dll|6.1.7600.16385|ntmarta.pdb|654E30BBAE864799893AF65 7FEA771722|0x72a70000|0x72a90fff|0 Module|comctl32.dll|6.10.7601.17514|comctl32.pdb|B4CE90AAB95E4B89A22A 7711DFD7E6EF2|0x72ab0000|0x72c4dfff|0 Module|version.dll|6.1.7600.16385|version.pdb|52234E5C7EC44646B62D563 57B2C94872|0x72d50000|0x72d58fff|0 Module|RpcRtRemote.dll|6.1.7601.17514|RpcRtRemote.pdb|16827EB67C584E0 D8B17B60D76B2B0CE2|0x73450000|0x7345dfff|0 Module|rsaenh.dll|6.1.7600.16385|rsaenh.pdb|F03813E5A0554853A6BC085C1 7A3AB352|0x73460000|0x7349afff|0 Module|cryptsp.dll|6.1.7600.16385|cryptsp.pdb|9536207F9C264D92B2C50D4 4E77AC0A91|0x734d0000|0x734e5fff|0 Module|profapi.dll|6.1.7600.16385|profapi.pdb|CA045CA9E5C74D899B90E77 6B38A18B32|0x73650000|0x7365afff|0 Module|dwmapi.dll|6.1.7600.16385|dwmapi.pdb|D8D91B3F339A4FDC960FC7121 D146DF42|0x737d0000|0x737e2fff|0 Module|AudioSes.dll|6.1.7601.17514|AudioSes.pdb|A88FCF91944949A8A1863 D1592BB2FD12|0x749b0000|0x749e5fff|0 Module|propsys.dll|7.0.7601.17514|propsys.pdb|D0EDA507E53D4579A337F87 5012D7B482|0x749f0000|0x74ae4fff|0 Module|MMDevAPI.dll|6.1.7601.17514|MMDevAPI.pdb|941E45A63E8F457D90CE2 9CC508C34B92|0x74af0000|0x74b28fff|0 Module|msimg32.dll|6.1.7600.16385|msimg32.pdb|13C89B70614E4E7FB1C677D 443D15D182|0x74b70000|0x74b74fff|0 Module|CRYPTBASE.dll|6.1.7600.16385|cryptbase.pdb|E62FEAE559EE4CD9956 14215B01AC2102|0x74ec0000|0x74ecbfff|0 Module|sspicli.dll|6.1.7601.17725|wsspicli.pdb|FE5709E8439B4232A45608 4643D47B861|0x74ed0000|0x74f2ffff|0 Module|setupapi.dll|6.1.7601.17514|setupapi.pdb|C6B7CC380FCD42C29EDB1 B61757DFD922|0x74f30000|0x750ccfff|0 Module|sechost.dll|6.1.7600.16385|sechost.pdb|7AF14D02D41E4CD6942745F E0E6372B11|0x750d0000|0x750e8fff|0 Module|kernel32.dll|6.1.7601.17651|wkernel32.pdb|DFB4E9EBD1654DB2ACF1 290CD316CEA22|0x750f0000|0x751fffff|0 Module|ws2_32.dll|6.1.7601.17514|ws2_32.pdb|18C960B958404C4F80F686EE9 78A33D42|0x75380000|0x753b4fff|0 Module|usp10.dll|1.626.7601.17561|usp10.pdb|220A06FAFEF54D1CB1DD2D842 5B260321|0x753e0000|0x7547cfff|0 Module|nsi.dll|6.1.7600.16385|nsi.pdb|D15A81679FAE4A7392344B6FD268679 42|0x75480000|0x75485fff|0 Module|user32.dll|6.1.7601.17514|wuser32.pdb|0FCE9CC301ED4567A819705B 2718E1D62|0x75490000|0x7558ffff|0 Module|Wldap32.dll|6.1.7601.17514|wldap32.pdb|A0183052C47E4652BFC983C C603C12442|0x75750000|0x75794fff|0 Module|cfgmgr32.dll|6.1.7601.17621|cfgmgr32.pdb|E4C73E93B825413F99E80 BA656C483172|0x757a0000|0x757c6fff|0 Module|msctf.dll|6.1.7600.16385|msctf.pdb|173DAEF86B2548DBA6134EB74C4 D2F232|0x75800000|0x758cbfff|0 Module|devobj.dll|6.1.7601.17621|devobj.pdb|583F4457964D46CA8C36ED490 3BE6AA22|0x758d0000|0x758e1fff|0 Module|ole32.dll|6.1.7601.17514|ole32.pdb|5061F11A9A57433595EA5EA75A1 56F4B2|0x758f0000|0x75a4bfff|0 Module|oleaut32.dll|6.1.7601.17676|oleaut32.pdb|68047829A4754E789AC1C 8035BA168CD2|0x75ba0000|0x75c2efff|0 Module|KERNELBASE.dll|6.1.7601.17651|wkernelbase.pdb|FDF353DA71FE45CD 953EBEC8ED6D14AB1|0x75c30000|0x75c75fff|0 Module|clbcatq.dll|2001.12.8530.16385|CLBCatQ.pdb|00A720C79BAC402295B 6EBDC147257182|0x75c80000|0x75d02fff|0 Module|advapi32.dll|6.1.7601.17514|advapi32.pdb|3F32049F550C42B09CF11 4A1FB8A97E92|0x75ec0000|0x75f5ffff|0 Module|msvcrt.dll|7.0.7601.17744|msvcrt.pdb|F1D253F9555C46DF8076400A5 2B3A9292|0x75f60000|0x7600bfff|0 Module|shlwapi.dll|6.1.7601.17514|shlwapi.pdb|E128B1CEE2EB438C8646E69 67118F33E2|0x76010000|0x76066fff|0 Module|imm32.dll|6.1.7601.17514|wimm32.pdb|35DD4069EB2A43BF869D6E311F AD09452|0x76080000|0x760dffff|0 Module|rpcrt4.dll|6.1.7601.17514|wrpcrt4.pdb|FAC24015130D4D7FAAA77EA3 6ED5AF1C2|0x760e0000|0x761cffff|0 Module|gdi32.dll|6.1.7601.17514|wgdi32.pdb|08A541B5942242BDB4AEABD8C8 7E4CFF2|0x76250000|0x762dffff|0 Module|shell32.dll|6.1.7601.17755|shell32.pdb|79A2F5058E0F4F79B66FDDE 6689424F82|0x762e0000|0x76f29fff|0 Module|lpk.dll|6.1.7600.16385|wlpk.pdb|C39166A53CCE43F0ADF876B9C637A1 EA1|0x777c0000|0x777c9fff|0 Module|ntdll.dll|6.1.7601.17725|wntdll.pdb|D74F79EB1F8D4A45ABCD2F476C CABACC2|0x777f0000|0x7796ffff|0 0|0|||||0x68d09903 0|1|ntdll.dll|LdrShutdownProcess|||0x96 0|2|ntdll.dll|RtlExitUserProcess|||0x73 0|3|kernel32.dll|ExitProcessStub|||0x12 0|4|msvcr100.dll|__crtExitProcess|f:\\dd\\vctools\\crt_bld\\self_x86\ \crt\\src\\crt0dat.c|708|0x8

 

---------------------------------------------------------------------- --

 

Don't know what other information is needed at this point

 

I'm using Windows 7 Home Premium Service Pack 1, Firefox 13--graphics acceleration disabled.

 

Hope someone can figure this out soon.  I'd downgrade to the earlier version, but I don't know how.

 

Ortho_Fan

Branched to a new discussion.
 
Replies 1 2 Previous Next
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Jun 8, 2012 2:55 PM   in reply to Ortho_Fan

    Ortho_Fan,

    Thanks for taking the time to report this to us.  Would you mind opening a new bug at bugbase.adobe.com with this info (and a link to this thread).  If possible, we'd also like to get one or two of your Mozilla report ID's so we can investigate further.  Finally, could you try disabling the Flash Player's protected mode to see if that resolves the problem?

     

    How do I disable Flash Player's protected mode for Firefox?

     

    Please post back with the bug URL and I'll investigate further.

     

    Thanks,

    Chris

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Jun 8, 2012 3:36 PM   in reply to Ortho_Fan

    Thanks for adding the bug so quickly.  I suspect you might run into a problem saving with notepad in this location.  I ended up saving the mms.cfg to my desktop, then I moved it using windows explorer.  I'm attaching a copy here if you'd like to use that instead.

     

    Chris

    Attachments:
     
    |
    Mark as:
  • Currently Being Moderated
    Jun 8, 2012 3:57 PM   in reply to Ortho_Fan

    If you could attach the actual crash report files to the bug, that would be very helpful.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 8, 2012 4:39 PM   in reply to Ortho_Fan

    Hi,


    The crash report link you provided was definitely a known issue in the beta, but we believe it's resolved at this point.  Firefox saves all of your crash logs, so if you were running the beta, that may be what you're seeing.  It's also possible that our fix isn't 100% effective -- it's timing-related and really hard to reproduce -- but you can see a drastic reduction in the incidence of the crash (the Mozilla folks point this out as well) in the statistics.

     

    The release version of Flash Player 11.3 contains a fix for this crash.  I'm not able to reproduce the issue on my end using Firefox 13 and Flash Player 11.3.300.257 at this point.  I'll leave my stress-testing suite running over the weekend to see if I can catch anything, though.  If you happen to run across steps that consistently cause a crash (it might be specific to doing those things while visiting specific content), that would be super helpful.

     

    Anyway, by making those mms.cfg modifications, you've disabled Protected Mode. 

     

    If you're interested in the implementation and why you see a difference in processes displayed, there's a good write-up here:

    http://blogs.adobe.com/asset/2012/06/inside-flash-player-protected-mod e-for-firefox.html

     

    To get the crash dumps -- which are what we feed to the debugger, do the following:

     

    If you look under C:\Users\<you>\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\

     

    Just grab anything from today.  If you submitted them already, they'll be copied to \submitted\ instead.

     

    If you're not finding the AppData directory, it's because it's hidden.  Do the following to make them visible.


    You can zip that stuff up, or just attach the files to the bug one at a time.  Either way is fine.

     

    From Windows Explorer

    Click Organize > Folder and Search Options

    Click the View tab

    Under Hidden Files and Folders, click Show hidden files, folders or drives

    Uncheck Hide protected operating system files and acknowledge the warning.

     

    Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 8, 2012 5:27 PM   in reply to Ortho_Fan

    That looks like it, but it's a binary file, so pasting it into the forum isn't going to result in something we can use.

     

    Please go back to the bug below, browse to the file using the Browse button on the right, and click Attach.

    https://bugbase.adobe.com/index.cfm?event=bug&id=3209832

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Jun 8, 2012 5:37 PM   in reply to Ortho_Fan

    If you'd like, you can zip them up and email them to me (ccampbel@adobe.com).  I'll attach them to the bug report.

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 10, 2012 3:20 AM   in reply to Ortho_Fan

    I think it is the same as:

    [Platform_Windows] Firefox - Crash Report [@ LdrShutdownProcess ]

    https://bugbase.adobe.com/index.cfm?event=bug&id=3172259

     

    Adobe: "We have an internal bug for tracking this problem."

    (12:28:47 AM PDT May 17, 2012)

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 10, 2012 3:49 PM   in reply to Ortho_Fan

    Hi Orto_Fan,

    look here please, perhaps the same (critical) issue:

    http://forums.adobe.com/thread/1020115?tstart=0

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 10, 2012 9:43 PM   in reply to Ortho_Fan

    Out of curosity I looked at my about:crashes and yeah I have quite a number of them.  All related to this. Here's one of mine: https://crash-stats.mozilla.com/report/index/cb60f1e1-bfbf-4cb0-aa88-f 6b482120611

     

    Due to the number of threads and bugs I'm seeing on this, I'm not real sure where to tack on my information. Because I never had any notice that a crash had occurred and videos were playing fine, I thought everything was fine.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 10, 2012 11:53 PM   in reply to mrheadrick
     
    |
    Mark as:
  • Currently Being Moderated
    Jun 11, 2012 4:40 AM   in reply to John6060

    Dear Ortho,

     

    this bug is present in new machine too (a lot of friends with seven and...w8 too).

     

    https://bugbase.adobe.com/index.cfm?event=bug&id=3210025

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 11, 2012 2:18 AM   in reply to John6060

    I dont want to reset my firefox. it is too much important for me (all my settings).

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 11, 2012 8:24 AM   in reply to Ortho_Fan

    Hi dear Ortho_Fan,

     

    thank you for your reply. I agree with all you wrote!

    I disabled now the proteced mode (=0). . no problems. but, I know, this is a workaround only for troubleshooting purposes.

    I added my dxdiag for the adobe developer, because he was UNable to reproduce the bug. (?!). I hope that this attch will help the developers

     

    => https://bugzilla.mozilla.org/show_bug.cgi?id=747683

    https://bugbase.adobe.com/index.cfm?event=bug&id=3210025

     

    best,

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 11, 2012 8:30 PM   in reply to Ortho_Fan

    Thanks for the feedback.  I found a 100% reliable way to reproduce this crash today, and your callstack matches mine.


    We're actively investigating this issue, and will update the bug as we have more information.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 12, 2012 2:02 AM   in reply to Ortho_Fan

    Hi, very good news from you.

    is this the same bug that could be fixed soon?

    http://forums.adobe.com/message/4478370

     

    thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 12, 2012 1:55 PM   in reply to Ortho_Fan

    Adobe installed it like that with version 11.2.202.235 as well.  It looks like they are installing the 32bit files into the 64bit area and visa versa. I thought this was odd as well.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 12, 2012 3:03 PM   in reply to Ortho_Fan

    I have flash32 only and the same issue.

    Perhaps this is not related to the bug, I guess.

    from where did you install flash?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 12, 2012 3:24 PM   in reply to Ortho_Fan

    I install from the official adobe site ("get flash") as soon it becomes available, without to wait, because it is very important to upgarde flash as soon as it becomes available for security fixes  

     

    (unchek all the boxes regarding mcafee...)

     
    |
    Mark as:
  • Chris Campbell
    9,454 posts
    May 4, 2010
    Currently Being Moderated
    Jun 12, 2012 6:11 PM   in reply to schützenkönig

    On 64 bit windows, the System32 folder is actually for 64 bit components and the SysWow64 folder is for 32 bit.

     

    http://en.wikipedia.org/wiki/WoW64

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 8:23 AM   in reply to Ortho_Fan

    there are people that doesnt spend time to follow all the steps (or are unable to take this task at the moment), therefore they skip to the last step in the guide

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 8:28 AM   in reply to Ortho_Fan

    http://support.mozilla.org/en-US/kb/flash-crashes-or-does-not-load-fir efox-13#w_disable-protected-mode-in-flash

     

    here an option has been omitted:

    silent crash! i.e container's crash after closing firefox! while you may notice none issue during web surfing/YT watching... !

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 3:14 PM   in reply to schützenkönig

    it seems that mozilla did find the bug? maybe?

    https://bugzilla.mozilla.org/attachment.cgi?id=632900&action=edit

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 3:25 PM   in reply to schützenkönig
     
    |
    Mark as:
1 2 Previous Next