site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Am 02.11.2004 um 19:07 schrieb Eric R Johnson: Third, you make sure they are aware of the problem. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Anyone with a dual cpu mac and an extended time to let the app run (while downloading and seeding torrents) will probably see a panic, though. This should be already enough for a bug report. Apple engineers have few time but many Macs so they just have to set up one and wait (while working on other things ;-) ) for the panic to occur. Then, they have sources for the java engine so they can get a more meaningful backtrace. Hopefully, they agree they have to fix something in their engine. I'll see if I can push to get users to submit information to get a rough idea of MTBF or TDR trends. It's pretty hard to get good data out of your average user, though. Azureus always works fine here. Great work. But then, I have single-CPU Macs, only. :-) This email sent to site_archiver@lists.apple.com