Re: can't debug safari plugin when using 64 bit
Re: can't debug safari plugin when using 64 bit
- Subject: Re: can't debug safari plugin when using 64 bit
- From: Jens Alfke <email@hidden>
- Date: Mon, 14 Jun 2010 19:36:34 -0700
On Jun 14, 2010, at 4:20 PM, Bill Appleton wrote: here is a key question: why does the 64 bit safari behave differently than 32 bit? Safari in 64-bit already has to support running legacy 32-bit plugins as separate processes, because there’s no way to intermix 32 and 64-bit code in a single process. As long as it’s doing that, it makes sense to run all plugins separately, for security and stability reasons. (Remember that Flash is the #1 cause of crashes in the entire Mac OS, as measured by the automatic crash reports Apple receives.)
Chrome already runs all web pages (not just plugins) in separate processes from the browser; Safari will be doing so in the future, judging by the “WebKit2” effort underway in the public WebKit project.
—Jens |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden