3 ms·
Not that I agree with him but this article kind of murdered his quote. He was replying to the fact that Jobs had implied that Flash was responsible for the majo
by akmiller 16y ago
Not that I agree with him but this article kind of murdered his quote. He was replying to the fact that Jobs had implied that Flash was responsible for the majority of Mac crashes.
I think jobs just meant that Flash simply crashed a lot on Macs but he seemed to infer that Flash actually caused the OS to crash. If Flash is causing the OS to crash then yes there is a problem as you'd hope a program residing in the user space wouldn't crash the kernel.
- steveklabnik 16y agoI think when they say "crash" they mean crashing Safari, not crashing OSX. That stat came from Apple's automated crash reporting tool, and I can't imagine that'd work after a kernel panic.
- deleted 16y ago[deleted]
- Zev 16y agoOS X saves a log and sends (or asks to send) the report back to Apple the next time the user logs in.
- Locke1689 16y agoA program in user space cannot be the root cause for a kernel panic. He meant Safari.
- Zev 16y agoI was simply referring to OS X's automated crash reporting tool. Which does work after a kernel panic, regardless of what messed up badly enough to cause such an event.
- steveklabnik 16y agoCool, thanks for the info.
- wtallis 16y agoJobs didn't imply that Flash is responsible for the majority of crashes. What he did say explicitly, and not for the first time, is that Flash is the number one source of crashes on Macs. That's not the kind of claim a chief executive would make without the data to back it up. Regardless of whether the crashes are due to poor code in OS X or poor code in Flash, if Apple wants to maintain a reputation for stability, their biggest enemy is the crashes involving Flash. Since they don't control the quality of code in Flash, they've got reason enough to try to kill Flash without their mobile strategy coming into the picture.