Bug 11560 - Flash can create deadlock cases in Safari
Summary: Flash can create deadlock cases in Safari
Alias: None
Product: WebKit
Classification: Unclassified
Component: Plug-ins (show other bugs)
Version: 419.x
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2006-11-10 01:57 PST by Kurt Moore
Modified: 2006-11-13 03:24 PST (History)
1 user (show)

See Also:

entire crash log (259.00 KB, text/plain)
2006-11-10 17:09 PST, Kurt Moore
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Moore 2006-11-10 01:57:10 PST
I want to knote, Firefox also does this, I am sure any browser on the mac will, since they will share the Flash plugin.

While I wait for a response on this question:
I was fiddling around trying to see why Safari stalled on flash heavy sites as well.

I download the demo version of Flash 8 and made a simple flash file, a repeat loop of about 1 million times or so.  Loading this into Safari, I peg CPU usage, and get the spinning ball for longer than I care to wait.

Eventually, the Flash PI will pop up a dialogue telling me to stop the action, or let it continue, both buttons do the same, which is allow it to continue.  Eventually, Safari will crash, or you have to force quit the application, and lose data, tabs, sometimes prefs just go poof, any number of bad things.

Should a PI under any case be able to take out a browser, I kind of think not.  During the time this is happening, of course, no other page data is loading, which again, explains why myspace never loads certain pages.

Comment 1 Alexey Proskuryakov 2006-11-10 15:17:40 PST
Yes, a plugin can do anything to the browser, and it can even compromise the security of user's data outside the browser - this is how plugins are different from DHTML and Java. It is probably a bug in the Flash plugin that it cannot stop the action.

It would be interesting to see how Safari crashes (there may be more to this issue than meets the eye). Could you please attach a crash log?
Comment 2 Kurt Moore 2006-11-10 17:09:10 PST
Created attachment 11478 [details]
entire crash log

search for "shockwave" and you should see the threads that are dying.
Comment 3 Alexey Proskuryakov 2006-11-11 00:44:27 PST
Thank you! This indeed looks like a Flash issue entirely, please report it to Adobe (I am not sure what the best way to report bugs to them is, but <http://www.adobe.com/bin/fp9betafeedback.cgi> looks promising).

By the way, the file you attached is so large because it contains a lot of earlier crash logs, too - the easiest way to get the latest one is from the bugreporter window that appears immediately after a crash.
Comment 4 Kurt Moore 2006-11-12 20:13:31 PST
thanks, I sent the entire log, becuase I want to know what those other crashes are, Safari crashes a lot on me.  Maybe you can look at it and give me a rough idea.

I will report to Adobe, somehow, I think it will do little good, perhaps someone in the webkit arena may know someone at Adobe who might actually care, I just do not think my post is going to get their attention.
Comment 5 Alexey Proskuryakov 2006-11-12 22:11:35 PST
A lot of the crashes in the log appear input method-related, I'd try running without TypeIt4Me for a while.
Comment 6 Kurt Moore 2006-11-13 03:24:24 PST
Thanks, I had a feeling, since i see TSM in there a lot, so I updated TypeItForMe and also contacted the developer.

thanks again.