Linked by David Adams on Fri 5th Aug 2011 16:38 UTC, submitted by tjavailable
Linux Linux on the desktop seems to be the perennial second class citizen, but with Adobe's upcoming 64 Bit Flash 11 beta, Linux is getting a seat at the adults' table. It's being released for Windows, Mac, and Linux simultaneously.
Thread beginning with comment 483973
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by kaiwai
by kaiwai on Sun 7th Aug 2011 00:44 UTC in reply to "RE: Comment by kaiwai"
kaiwai
Member since:
2005-07-06

I'd argue that if a random process running in user mode manages to crash the system this way (or if Flash needs more than normal user mode privileges to do its job), something's deeply wrong with the OSX graphics stack (or at least the version supplied in Lion). I'm used to see this kind of crashes on Linux distros, not on "professional" OSs that are sold in bundle with hardware for a hefty price.


The system obviously hasn't crashed if I am able to move the cursor around and people with similar problems can ssh - the issue is related to the application itself. If something runs in user space and affects something else that runs in user space then the issue is with the application going rogue and the vendor failing to fix it.

Reply Parent Score: 3

RE[3]: Comment by kaiwai
by Neolander on Sun 7th Aug 2011 14:26 in reply to "RE[2]: Comment by kaiwai"
Neolander Member since:
2010-03-08

Something running in user space being able to affect something else that runs in a separate user space process is a failure of OS security, more specifically process sandboxing, IMO.

When my mail client crashes, I don't have to reboot my PC because the UI has basically turned unresponsive, only leaving me with a useless mouse pointer floating around. Why should it be different with Flash ?

Reply Parent Score: 1

RE[4]: Comment by kaiwai
by No it isnt on Mon 8th Aug 2011 12:50 in reply to "RE[3]: Comment by kaiwai"
No it isnt Member since:
2005-11-14

Flash has two basic features: 1) It can run fullscreen, hogging all input, and 2) it can hang. At that point, the user won't be able to regain control of the console without some equivalent of the Windows three finger salute, or a remote login.

Reply Parent Score: 2