Participating Frequently

Question

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

Forum|Forum|19 years ago
April 6, 2007
39 replies
5862 views

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.

This topic has been closed for replies.

J

Jack260

Participant

Hi,

I was wondering if there has been any progress made in this case? I am also getting the same issue with multiple Flash 9 players consuming a lot of memory and crashing due to an invalid memory access.

A

alfajoe

Participant

IE 6 or 7 crashes on various www,s. EVERY TIME I ENTER WWW.ADOBE.COM crashes my PC
This is frustrating as I need to access other PC,s to search this appatently common problem.
My work PC is the same as home at it is fine. Flash 9.0.28.0 XP SP2

But a note. I have tried using various REGEDIT PC tools to clean up register.
Under 1 occasion only I could enter the www.adobe.com web site. I thought problem was fixed but no luck.

PC is over a year old and has been fine untill I have helped my young kids play some games on internet. Somewhere a Flashplayer has been down loaded.

M

mrhcky20

Participating Frequently

Well TandyThomas, it was certainly worth the try but I can tell you that I was just at the Weather.com interactive map page, and unfortunately I experienced the same exact crash. Thanks for the effort though.

Incidentally Bentley, I am not one who uses the multiple tabs very often at all, I usually browse with just the initial tab open, call me crazy, but I prefer it that way. Also, yes I only had the single tab open at the Weather.com site. Hope it helps, and sorry for the comments. My frustration level was at an alltime high, as are many of all of yours' as well.

A

Anonymous

Perhaps the details of my completely different experience which results in the same crash might be of help?

I subscribe to an online world at Webkinz.com which uses flash animation. I crash regularly here, and ads cannot be the cause ... because there aren't any. I have the most problems with pages featuring spinning wheels or lots of movement.

What's odd is that I first joined Webkinz in early January and played it for a month or two before I began to notice a slowdown. Since then, it's only gotten progressively worse over time ... now to the point that anything that moves does so excruciatingly slowly.

At first I thought my processor was being overwhelmed, but I exceed the minimum requirements and have a 2.8 Ghz dual chip (P4). I also noticed that my system would crash whenever I ran a diagnostic utility ... specifically, Fix-it 5, which I use to fix misdirected registry entries. I narrowed this problem down to the section dealing with Active X and COM entries. Other programs that scan my system also always result in crashes these days.

And when I say "crash", I don't mean the BSOD or crashing to my desktop. I mean total loss of all power, as if my computer had been suddenly unplugged from the wall.

I crash every time I visit Webkinz now, usually within just a couple of minutes. I use AOL primarily (which uses IE 6 because I haven't upgraded and don't particularly plan to), but I have the same result with Firefox.

I've run the official uninstaller and reinstalled the Flash Player. This didn't help a thing, but it might explain why things got worse ... i.e., my re-installation was a newer version which somehow exacerbated the problem.

I've also unstalled Shockwave, in case it was part of a conflict. No improvement. I also tried installing an older version of Flash Player, but Webkinz doesn't recognize it and forces me to install the most current version. (I would really appreciate advice on how to get around this problem, if anyone has a suggestion.)

I also tried creating a crash log, but it doesn't seem to exist. Probably because my crashes are fatal.

That's all I can think of at the moment that differs from what's been reported above, but feel free to ask me any questions if it would be helpful.

I look forward to the earliest resolution to this problem.

Mardi

B

boostm3

Participating Frequently

Just had another IE7 crash of the kind weve been talking about.. A similarity of conditions when all my IE7 crashes have occurred, I believe, is that they seem to occur when Ive got maybe 10 or more tabs going in a single IE7 window.

S

SJPerl

Participant

The problem has not been sovled - I have it also Explorer crashes with an error message ( Flash 9.ocx - so what is the quick solution?? Which Flash player was considered OK? 7? 8? or the latest version of 9? Should we go back to Explorer 6?

Please some help here! And not just discussion. I have this problem since I upgraded to Explorer 7 - more than a year.

B

Bbbent

Inspiring

quote:

Originally posted by: SJPerl
The problem has not been sovled - I have it also Explorer crashes with an error message ( Flash 9.ocx - so what is the quick solution?? Which Flash player was considered OK? 7? 8? or the latest version of 9? Should we go back to Explorer 6?

Please some help here! And not just discussion. I have this problem since I upgraded to Explorer 7 - more than a year.

If you read my previous posts you'll see that we -think- the root cause of the problem is many Flash Player instances consuming all the available memory and causing a crash.. It's not something we can fix quickly.

So until we get more specifcs your choices are:
-- Use fewer tabs
-- Revert to an older version of Flash Player.. If we're correct the root cause is memory management in FP9. The memory manager was completely rebuilt from scratch for Flash Player 9. So any pre-9 version should be OK. But obviously you wont' be able to see any new FP9 features. So no ActionScript 3 sites or Flex sites..

Switching to IE6 would help because you wouldn't have tabbed browsing. But that's your choice (if you can figure out a way to do it!)

I realize it's not a good situation. My team and I are doing what we can to keep Engineering attention on this issue...

A

alponce

Participant

Where can I get an older version of the OCX and how do I replace 9c?

C

CalvinoHobbes

Participant

The youtube link i send in earlier is constantly crashing my mac. Only that page open, nothing else, no tabs. I also asked for instructions on enabling crash logs on mac, didn't get a response....

B

Bbbent

Inspiring

quote:

Originally posted by: CalvinoHobbes
The youtube link i send in earlier is constantly crashing my mac. Only that page open, nothing else, no tabs. I also asked for instructions on enabling crash logs on mac, didn't get a response....

http://www.youtube.com/watch?v=flKzjuDhFDs right? Hasn't crashed FF or IE Windows for me yet (running at the same time).

Bam, crashed my Macbook Pro after a number of minutes (I wasn't watching where it was when it crashed..)
I wrote it up this morning and sent it to Engineering for investigation...

There is no ability to generate a Flash Player crash log on the mac, btw...

UPDATE 5/24: This Mac only crash has been isolated and will be repaired in the next public update to Flash Player 9 plugin for OSX. HOWEVER, I cannot provide any information on when that update will be available.

A

Anonymous

Hi svensson88,

We received your .mdmp cash file and will escalate this to engineering. Also, I will personally take over your case. Thanks for sending this info.

As Bentley mentioned, all of these cases are related to having multiple instances of Flash Player running simultaneously. If you have a reproducible crash, I would suggest that you progressively minimize the number of tabs you have open to narrow down the crash. If you’re able to isolate a single instance of Flash Player crashing, please send us that URL.

M

mrhcky20

Participating Frequently

You know what, Bentley Wolfe -ADOBE, this is something that seems to me is like a big 'ol merry-go-round. All u keep asking for is this and that with no real answers at all, just more questions! Kinda like a dog chasing its own tail, you know????

B

Bbbent

Inspiring

quote:

Originally posted by: mrhcky20
You know what, Bentley Wolfe -ADOBE, this is something that seems to me is like a big 'ol merry-go-round. All u keep asking for is this and that with no real answers at all, just more questions! Kinda like a dog chasing its own tail, you know????

Here's the situation as discussed yesterday with Flash Player engineering... we're not sure if this is true for all these crashing cases, but it definitely is for some of them.

The introduction of tabbed browsing may be a large contributor to this problem. Most ad servers are serving Flash ads, and many, many sites embed SWF content. We're not entirely sure, but what seems to be happening is that there are multiple instances of Flash Player running on each tab, each consuming memory. And at some point they eat up all the available virtual memory and cause the crash.

The problem at that point is that there's no memory left so FP can't write a crash log and fails most ungracefully. At least that's what we think is happening. I have yet to be able to find a single page that will consistently crash (without multiple tabs).. that might change the thinking.

Darren has been furiously grabbing Flash Player crash mdmp files and escalating them to Engineering. Each one helps to a degree. And I appreciate his efforts, because it's a lot of effort for each case.

But because every machine is going to crash at a different point the stack trace is going to be entirely different for every crash. So there's a limit to the usefulness of the crash dump (and to be honest the IE crash debug doesn't help much at all).

We're working with someone else on this forum to possibly get a consistently crashing machine in house, and I've got to find some way to get this info into a technote of some kind to try to help folks. The key for now is if you can consistently crash, try reducing the number of open tabs you're working with. If you can get a machine to crash with one tab then open a case and let me know.

So that's where we're at. The above is really just a theory that we're discussing. Finding a way to prove it is what I'm really after.

E

etolman

Participant

If it is any help, here is a debugger call stack from 9.0.45.0 FlDbg9c.ocx:

We are trying to get a sample app built that has the least amount of data and still be able to reproduce the crash:

FlDbg9c.ocx!3006c8f9()
[Frames below may be incorrect and/or missing, no symbols loaded for FlDbg9c.ocx]
FlDbg9c.ocx!3008f4f7()
FlDbg9c.ocx!3009e042()
FlDbg9c.ocx!300c0f55()
FlDbg9c.ocx!300c16bb()
FlDbg9c.ocx!300adc71()
FlDbg9c.ocx!300ae00c()
user32.dll!77d48734()
user32.dll!77d48816()
user32.dll!77d4c63f()
user32.dll!77d4e905()
App.exe!CWnd::DefWindowProcA(unsigned int nMsg=512, unsigned int wParam=0, long lParam=38142591) Line 1029 + 0x20 bytes C++
> App.exe!CWnd::WindowProc(unsigned int message=512, unsigned int wParam=0, long lParam=38142591) Line 1742 + 0x1c bytes C++
App.exe!AfxCallWndProc(CWnd * pWnd=0x0012fdb8, HWND__ * hWnd=0x0090065c, unsigned int nMsg=512, unsigned int wParam=0, long lParam=38142591) Line 240 + 0x1c bytes C++
App.exe!AfxWndProc(HWND__ * hWnd=0x0090065c, unsigned int nMsg=512, unsigned int wParam=0, long lParam=38142591) Line 389 C++
user32.dll!77d48734()
user32.dll!77d48816()
user32.dll!77d489cd()
user32.dll!77d496c7()
App.exe!AfxInternalPumpMessage() Line 183 C++
App.exe!CWinThread::PumpMessage() Line 896 C++
App.exe!AfxPumpMessage() Line 190 + 0xd bytes C++
App.exe!CWnd::RunModalLoop(unsigned long dwFlags=5) Line 4322 + 0x5 bytes C++
App.exe!CDialog::DoModal() Line 544 + 0xc bytes C++
App.exe!CreatorApp::InitInstance() Line 61 + 0xb bytes C++
App.exe!AfxWinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00161f07, int nCmdShow=1) Line 37 + 0xd bytes C++
App.exe!WinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00161f07, int nCmdShow=1) Line 29 C++
App.exe!__tmainCRTStartup() Line 315 + 0x35 bytes C
App.exe!WinMainCRTStartup() Line 187 C
kernel32.dll!7c816fd7()

Registers:

EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 00000000 ESI = 00000000 EDI = 00000000 EIP = 00533B30 ESP = 0012FAA4
EBP = 0012FAB8 EFL = 00000000

This is a debug build, so parameters in the call stack should be accurate.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.