On Nov 6, 2010, at 4:19 PM, Robert Rice wrote: > I determined that my system crash was not due to an endless loop - rather due > to a very inefficient algorithm. MacRuby seems to run at such a high priority > that it can cause the system to crash - especially if a streaming video is > running.
MacRuby does not run at any particular elevated priority itself. If you're doing something like producing or consuming A/V streams in real-time, on the other hand, then any number of real-time threads may be created on your behalf by the various Frameworks responsible for doing that sort of processing, but that's no different a scenario than calling them from ObjC and the priority of your application itself will still be irrelevant in such a scenario. It may be that you're [mis]using the APIs such that more work is being done than necessary. You may wish to review some of the sample code that most directly corresponds to whatever it is you're doing. Also, as others have intimated, if you were able to panic your system for any reason (and I do mean panic and not some other hang or application-specific crash) then that's a bug that really needs to be reported since Apple takes panic reports pretty seriously. - Jordan
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
