Skip to main content
Participant
March 9, 2017
Question

Flash Player Update 221 crashes IE 11

  • March 9, 2017
  • 2 replies
  • 644 views

We updated to Flash Player 24.0.0.221 on 2/21/2017.  Immediately we started getting support calls saying our compliance CBT's were crashing.  After a little investigation we found that the user would get to a certain point in the CBT and the browser would close.  It would also close the parent window and anything attached to that window.  This is a CBT that has been out there for years with no problems.  I verified that it was happening with other CBT's as well.  We backed out Flash to 24.0.0.194 and everything started working fine again.  Next we updated to 221 and everything started crashing again.  Finally, we backed out to 194 again and everything worked fine.  It's clear something in this update has broken something in our CBT.  Reading some of the posts on this forum I can see we're not the only ones having this problem.  Our IT department is worried about the vulnerability that was patched with 221 so we need to get that fixed, but the CBT's are critical to our operations and must be available.  Can you let me know what we can do to fix this issue?

Have a great day!

James Jordan

This topic has been closed for replies.

2 replies

jeromiec83223024
Inspiring
March 10, 2017

There is a crash that I'm aware of that will be patched with the Tuesday release, which impacts some very old content.

That said, "it crashes" is not a diagnosis, it's an outcome -- much in the same way that "he's dead" isn't a diagnosis.  To provide you with any kind of useful feedback, I need to be able to differentiate the reason that it crashed, and understand the sequence of events that led to the crash.

The most useful way to do that is to get some details (in order of helpfulness):

  1. A reproducible example, steps to reproduce and a description of the affected configuration (browser/os, with versions)
  2. A crash dump for Firefox on Windows (their crash data is public, which is super useful), which you can get by:
    1. Crash the plug-in
    2. Type about:crashes in the address bar
    3. Click the relevant link(s) to submit them
    4. Post links to the result pages here
  3. A minidump or crash report for another browser, using the instructions above on reporting a crash

Also, what does CBT stand for in your context?


Thanks!

Participant
March 13, 2017

I too face crashes on all browsers with Flash Player 24.0.0.211 when running some old content published for Flash 6 and 7. The crash usually happens when the actionscript 2.0 executes a loadMovieNum of another swf file, though this is not always the case.

Here's my Firefox crash report:

[@ F_855855466_____________________] - Firefox 52.0 Crash Report - Report ID: a9faa168-1858-47b1-98bb-cadd32170313 https://crash-stats.mozilla.com/report/index/a9faa168-1858-47b1-98bb-cadd32170313

Appreciate your swift advice on this.

Regards,

Hayden

jeromiec83223024
Inspiring
March 13, 2017

This is the same signature as the one that I'm tracking.  It should be fixed in tomorrow's update.

Rave
Participating Frequently
March 10, 2017

Hi James,

I would request you to add a bug in the Adobe bug base with the crash logs.

Refer the doc for the steps to capture crash logs and log a bug: Report a Flash Player crash or error

Regards,
Rave