while (1) { dashboard();}
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com stupid question related to a stupid test: Explanations: I did the following stupid test: Results: or _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... is this considered correct that a toddler can screw a user session with dashboard? - launch dashboard (via F12) - click something like a 500 times on the Translation widget (if you want to regularly muscle your hands, you can alternate the finger every 100 clicks) After a while (there's a little lag between the click and the dashboard widget being displayed on the screen when a bunch of widgets are already there), the dahsboard widgets are just drawing the background image: - you can't click on their popup button - if you launch a stickies widget, when you type text in it, it goes in another widget - if you launch Activity monitor, it crashes - if you try to access the Startup Disk pref pane in System Preferences, the Disks list is missing or you just can't access this pref pane. - if you launch Terminal.app, the windows opened with a terminated command title. Of course and it's there that it's related to darwin is that all of this occurred because at one point, there's a bunch of "can't fork" error. Now, the real question is: is it logical that you can screw a user session that easily? Shouldn't there be a limitation on the number of processes that could be run by dashboard? aren't kern.maxprocperuid and kern.maxproc (I think it's these sysctl values) too small now that dashboard is in town? This email sent to site_archiver@lists.apple.com
participants (1)
-
Stephane Sudre