Flash Player 9,0,28,0 Causes IE 7.0 to die.

[IDisposable]

If I happen to have an instance of a debugger (for example Dev Studio 2005)
run, I get a chance to debug the exception. EVERY time this has happened, the
stack was in the Flash.OCX and the problem was an invalid memory access.

You guys are accessing freed memory.

[DannyDK]

Good observation, IDisposable...!

I think we are quite many that are haunted by this exception and would like
for Adobe to get their hands dirty to fix it - and the sooner, the better!!!

I'm not that skilled with a debugger as you are (I was with good old DOS
stuff, though). To me, it seems as if Adobe is about to get a security issue on
their hand, if someone evil attempts to exploit this memory accessing - or is
the exception simply benign?

To be able to document this exception further, IDisposable, could you briefly
demonstrate how to detect if/that the exception is accessing freed memory? I
too have DevStudio, but perhaps less could do the trick so others could
participate? I think the key point is to "see" what is happening at the point
where Flash9b.ocx is calling other dll's, and specifically how the referenced
memory is or is not allocated. All of this to point Adobes developers to the
right point in their code (to fix it).

If you think that the task isn't feasible, could you then please document your
finding the next time you trip over one, so Adobe can get their hands dirty
fast? :grin;

/Dan

[IDisposable]

I'm dazzled with the Adobe response to this issue! Thanks! Here's a stack
dump....

> Flash9c.ocx!3004d7c3()

[Frames below may be incorrect and/or missing, no symbols loaded for
Flash9c.ocx]
Flash9c.ocx!3004dab0()
Flash9c.ocx!3004ea0c()
mshtml.dll!7e906a96()
mshtml.dll!7e906b62()
mshtml.dll!7e906b1d()
mshtml.dll!7e8e7322()
mshtml.dll!7e8d21c5()
ntdll.dll!_RtlpAllocateFromHeapLookaside@4() + 0x31 bytes
ntdll.dll!_RtlAllocateHeap@12() + 0xd7 bytes
Flash9c.ocx!3019d4b2()
Flash9c.ocx!300517a4()
Flash9c.ocx!301874c8()
Flash9c.ocx!301877e2()
Flash9c.ocx!3004ed04()
Flash9c.ocx!30051a0f()
Flash9c.ocx!3005249e()
Flash9c.ocx!300575da()
Flash9c.ocx!30056f09()
Flash9c.ocx!3009df2c()
Flash9c.ocx!300b45e9()
Flash9c.ocx!300b5ec9()
Flash9c.ocx!300a12ce()
Flash9c.ocx!300a1222()
mshtml.dll!7eabadcb()
mshtml.dll!7e90ffb7()
mshtml.dll!7e90d2e6()
msls31.dll!746c2a90()
msls31.dll!746c27f8()
mshtml.dll!7e8fb951()
mshtml.dll!7e8fbab9()
ntdll.dll!@RtlpLowFragHeapFree@8() + 0x94 bytes
mshtml.dll!7e8d2716()
mshtml.dll!7e90e0b2()
mshtml.dll!7e8ea33d()
mshtml.dll!7e90c56c()
mshtml.dll!7e90bd28()
mshtml.dll!7e8e17e7()
mshtml.dll!7e8fd2f1()
mshtml.dll!7e90e1a0()
mshtml.dll!7e90e1ab()
mshtml.dll!7e8e1d7a()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90c491()
mshtml.dll!7e906b1d()
mshtml.dll!7e8e7322()
mshtml.dll!7e8d21c5()
mshtml.dll!7e988da4()
mshtml.dll!7e8d1eb4()
mshtml.dll!7e8f629a()
mshtml.dll!7e8d1ede()
mshtml.dll!7e8ea33d()
mshtml.dll!7e90c56c()
mshtml.dll!7e90bd28()
mshtml.dll!7e8e9b37()
mshtml.dll!7e8ea062()
mshtml.dll!7e8f7dd1()
mshtml.dll!7e904d30()
mshtml.dll!7e8de28e()
mshtml.dll!7e8e6de0()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90c491()
mshtml.dll!7e8e856d()
mshtml.dll!7e8ea33d()
mshtml.dll!7e90c56c()
mshtml.dll!7e90bd28()
mshtml.dll!7e90e1a0()
mshtml.dll!7e90e1ab()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90c491()
mshtml.dll!7e8fdbf7()
mshtml.dll!7e8e85b5()
mshtml.dll!7e8e85d7()
mshtml.dll!7e8e8039()
mshtml.dll!7e8ea33d()
mshtml.dll!7e90c56c()
mshtml.dll!7e90bd28()
mshtml.dll!7e8e17e7()
mshtml.dll!7e8fd2f1()
mshtml.dll!7e90e1a0()
mshtml.dll!7e90e1ab()
mshtml.dll!7e8f7dd1()
mshtml.dll!7e904d30()
mshtml.dll!7e8de28e()
mshtml.dll!7e8e6de0()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90d7d2()
mshtml.dll!7e90c874()
mshtml.dll!7e90c7fc()
mshtml.dll!7e8e67fe()
ntdll.dll!@RtlpLowFragHeapAlloc@8() + 0x15f bytes
mshtml.dll!7e9a44c9()
mshtml.dll!7e8fdbf7()
mshtml.dll!7e90e0b2()
mshtml.dll!7e8ea33d()
mshtml.dll!7e90c56c()
mshtml.dll!7e90bd28()
mshtml.dll!7e8e17e7()
mshtml.dll!7e8fd2f1()
mshtml.dll!7e90e1a0()
mshtml.dll!7e90e1ab()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90d7d2()
mshtml.dll!7e8e9b37()
mshtml.dll!7e8ea062()
mshtml.dll!7e9add27()
mshtml.dll!7e90bd28()
mshtml.dll!7e8ea503()
mshtml.dll!7e90f039()
mshtml.dll!7e90f004()
mshtml.dll!7e90c56c()
mshtml.dll!7e90ef74()
mshtml.dll!7e90cb39()
mshtml.dll!7e90cd8e()
mshtml.dll!7e90c491()
mshtml.dll!7e8e9e4c()
mshtml.dll!7e90f308()
mshtml.dll!7e90f2d3()
mshtml.dll!7e90f26f()
mshtml.dll!7e90bd28()
mshtml.dll!7e90ee37()
mshtml.dll!7e90edc8()
ntdll.dll!@RtlpLowFragHeapFree@8() + 0x94 bytes
ntdll.dll!_RtlFreeHeap@12() + 0x130 bytes

[Bentley Wolfe -ADOBE]

These are user-to-user forums. If you need a response please open a case (as
described at the bottom of this forum).

I'm actively looking for IE7 crash cases, so I appreciate it.

After you open the case, see if the support agents tells you about the Flash
crash log. It's a tool we use to work on cases such as this. If they don't
please PM me the case number.

[IDisposable]

[q]Originally posted by: Bentley Wolfe -ADOBE
These are user-to-user forums. If you need a response please open a case (as
described at the bottom of this forum).[/q]

I did precisely that, and they promptly closed the case telling me to call a
flipping phone number for support. Nope, I'll just disable Flash Player until
you guys get around to implementing a decent error reporting strategy that
doesn't waste MY time.

[Bentley Wolfe -ADOBE]

Well I'd be happy to dig into the case details if you're interested in
providing me the case number. This kind of feedback is really helpful. We DO
want to improve!

Additionally it's just plain wrong to redirect a Flash Player user to phone
support (becuase there is no phone support for FP). So I'd like to see what
happened.

[IDisposable]

[q]Originally posted by: Bentley Wolfe -ADOBE
Well I'd be happy to dig into the case details if you're interested in
providing me the case number. This kind of feedback is really helpful. We DO
want to improve![/q]

The reply message in e-mail:
[q]Dear Marc Brooks

A Technical Support specialist has responded to your support request
172583030. You may view the response to your web case in the attached PDF,
or you may view the response online and reference your case history at any
time by visiting [url]http://www.adobe.com/go/supportportal/[/url]. Simply log in,
and then
click Case History.

We believe the information we have provided will resolve your issue;
therefore,
we have closed your case. Your web case will remain in your case history
list for
future reference even after it has been closed.
[/q]

[q]Additionally it's just plain wrong to redirect a Flash Player user to phone
support (becuase there is no phone support for FP). So I'd like to see what
happened.[/q]

Here's what was in the attached PDF telling me to call:

[q]Your new TS Web Case# is:#172583030"I apologize for the inconvenience you
are experiencing. However,Customer Service (800) 833-6687 is the right
department that can resolvethis query, as this is beyond our support
boundaries.[/q]

I would love to resolve this...

[Bentley Wolfe -ADOBE]

Thanks IDisposable. We're getting a lot of traction on these Web Player
support processes, and this info is really useful to me. I'll dig into this
case tomorrow..

Now if I could snap my fingers and fix the IE7 crashing problem I'd be a
genius. But that's what I have Darren for. ;0

[Darren McNally - Adobe]

Hi IDisposable,

Boy, I'm feeling the pressure now. I wish it was as simple as snapping my
fingers.

As Bentley mentioned, we are actively looking for IE7 crash cases, and your
efforts are appreciated.

Here are some instructions to capture a crash log. We will have a better
chance in diagnosing the problem.

1. First open notepad or another text editor
2. Create a text file with one line: CrashLogEnable=1
3. Save the file as: c:\windows\system32\macromed\flash\mms.cfg
4. Generate a crash in the browser and record all URLs open at the time
(windows or tabs)
5. Open up a command line prompt. Select Start > Run and type cmd in the
dialog.
6. Type cd "Local Settings\Temp" at the command line prompt. Be sure that
Local Settings is in quotation marks.
7. Type dir *.mdmp at the command line prompt. These are the log files that
are to be sent to adobe.

We look forward to hearing from you soon.

[vineyardathens]

I too have been having crash problems w/ IE7 related to Flash9. One page I
know causes the crash is when I check my yahoo e-mail, in the new beta
version. There are those ads for mortgages on the side that run a flash
video. If I open that, I'll crash within minutes. I do get a warning, and I
send an error report everytime. It's getting very annoying. It crashes all the
time. Also when I am at myspace.com, or anysite with flash banners, it will
crash, especially if I have open multiple tabs.
Hope this helps, and I will try to log the url's for you.

[Darren McNally - Adobe]

Hi vineyardathens,

Thanks for the info. Please use the directions above to generate a crash log.
The URL is needed as well.

*If anyone is able to generate a crash log, please let use know and we will
open a case for you.

[mrhcky20]

I too keep having these problems.

The url is [url]www.lakings.com[/url]. As soon as i try to do anything in the main page, BOOM!!

[Darren McNally - Adobe]

Hi mrhcky20,

This does not seem to be a valid URL: [url]www.lakings.com[/url] ?

Please try using the steps above for generating a crash log. If anyone is able
to create a crash log, please send it to my personal email with all the details
including your diagnostic file (dxdiag) and URL: [email]support_flash@hotmail.com[/email]

If we can?t generate a crash in house, we will not be able to support the
issue unless we receive all the following information:

Details to include:

1. crash log
2. dxdiag (machine specs ? instructions below)
3. URL
4. web browser
5. OS
6. Flash Player version

How to get your dxdiag:

1. Select Start > Run
2. Type in ?dxdiag?
3. Save as a text file

[Darren McNally - Adobe]

Hi mrhcky20,

Thanks for sending the crash log and information needed to open a case. I will report back to you shortly after I submit this to our engineering team for further review.

[adobeisdumb]

glad the people at adobe finally acknowledge the problem... i mentioned it here 3 to 4 months ago and they told me to call support... which lead to "its you computer"

[Bentley Wolfe -ADOBE]

[q]Originally posted by: adobeisdumb
glad the people at adobe finally acknowledge the problem... i mentioned it
here 3 to 4 months ago and they told me to call support... which lead to "its
you computer"[/q]

We've jumped on top of these type of 'process problems' in the Player world
too. I'm certain we can make this a better exerience, but it'll take some
time..

[boostm3]

Im running XP Pro and Internet Explorer 7, and for the last few weeks, Ive been
getting periodic Inet Explorer crashes which displays the same message before
closing:

"Internet Explorer has encountered a problem a problem with an add-on......The
following add-on was running when this problem occurred: FLASH9C.OCX..."

This is a very annoying crash, as anything which is open in any Internet
Explorer window, ie, any posts being created, or forms in the middle of being
filled out are completely lost. So, I had no choice but to Uninstall Adobe
Flash9c.ocx....

Can you give me an indication when I can reinstall a WORKING copy? Ive
already uninstalled and reinstalled a few times, and still, the error comes
back..

What is being done about this? This is NOT beta software, so it should not be
happening...

[DannyDK]

IDisposable,

could we get back to how you detected this:
[Q]You guys are accessing freed memory. [/Q]

Is it possible for you to describe how someone without a programmers skills,
but perhaps with an admins skills, would be able to document the things you did
- in the event of a crash? Perhaps by brief descibtion of (free) tools, traps
to set up, settings to tweak, etc.?


Adobe,
I'm in favor of asking you to give that quote a very high attention, as it
seems to be the a very likely cause - both from the symptoms we all see
(well, a lot of us see) and from IDisposables finding, who, if I may say so,
seems to know what he's talking about.

/Dan

[DannyDK]

boostm3,

You may be able to limit your losses by separating browser instances so
just the windows belonging to one process dissapears when crashing. In XP you
do this in the Folder Options (found in Classical View of the Control Panel).
On the second tab you have the Advanced Settings. One is called "Launch folder
windows in a separate process" and also seems to have an effect in IE windows
(Explorer and IExplore are kinda cousins).
I always set this setting on machines I deal with, and if IE crashes, just the
windows from that single crashing process are gone. Each process is started
independantly from others from the desktop IE icon (not Ctrl-N or
Shift-Clicking !).
It seems that some of the crashes are related to sites having extensive use of
flash and pop-up windows or spin-off windows.
In some cases I even have the time to save information from some of the other
windows belonging to the crashing process (before pressing the OK button on the
crash message).

I hope this helps you a bit further, if you decide to use Flash - before this
is soon, hopefully, fixed...

/Dan

[boostm3]

Thanks Danny... I did that, and Ill see if it works.. Has Adobe even copped to the idea that a fix is needed??