5 ms·
Bear in mind that you are one person, and your mileage may vary. I'm glad you've had better luck than I. Software changes over time (both the browser, and the
by pohl 16y ago
Bear in mind that you are one person, and your mileage may vary. I'm glad you've had better luck than I.
Software changes over time (both the browser, and the flash plugin, and the flash code deployed on web pages) so asking someone to reference a particular site that will crash your particular browser won't help you understand what's going on. A better idea might be a few clever search strings:
http://lmgtfy.com/?q=safari+crash+log+flash http://lmgtfy.com/?q=safari+crash+log+flash
Or, alternatively, you can look at the architecture of chrome and ask why they put tabs in separate processes, and why mozilla is also putting protection in place:
http://arstechnica.com/open-source/news/2010/03/mozilla-previews-new-feature-to-guard-against-flash-crashes.ars http://arstechnica.com/open-source/news/2010/03/mozilla-prev...
Apple isn't just making a wild conjecture when they say that Flash is the leading cause of browser crashes. They get stack traces sent to them by the crash reporting mechanism, and they get to count how many crashes come from what region of code. Drawn from sample sizes in the millions, this constitutes measurement.
- 16g 16y agoOP says "your browser will crash frequently". Most of the replies (including yours) to my question only points to crash logs that cant be reproduced .Your answer is a very generic explanation on software development. And that is exactly what i am saying. I keep seeing all these people complaining about Flash , but no one has a proof that actually works. As i mentioned before, Flash is a complete resource hog on the mac but no one here has a solid reproducible proof for "frequent crashes". I choose not to believe in Apple's claims and numbers, as they are in open war with Adobe now on the issue. Opening up Flash on iPad and iPhone is lost business for app store(if you own an iPad/iPhone, you already know that currently there is no decent html5 application that work properly on these devices.)
- pohl 16y agoCall stack traces are not generic. They point to specific places. Those places are aggregated and counted. You're free to disbelieve that Apple is reporting their #1 source of crashes honestly, but you should take a look at the Top Crash link provided by ZeroGravitas. If you're not seeing the same pattern, you're not looking without bias. http://crash-stats.mozilla.com/topcrasher/byurl/Firefox/3.6.4 http://crash-stats.mozilla.com/topcrasher/byurl/Firefox/3.6....