[core-dev] latest NIO changes trigger OS X crashes

Appearently the latest versions of LimeWire with NIO (at least NIO
appears to be the best candidate as per the recent changes) do trigger
an OS X kernel bug. At least on two machines I have found the following
system crashes happening while LimeWire was running (from
/Library/Logs/panic.log):

*********

Thu Apr 14 03:47:03 2005




Unresolved kernel trap(cpu 0): 0x300 - Data access
DAR=0x0000000000000014 PC=0x0
00000000020C8F4
Latest crash info for cpu 0:
   Exception state (sv=0x1F736C80)
      PC=0x0020C8F4; MSR=0x00009030; DAR=0x00000014; DSISR=0x40000000;
LR=0x0020
C800; R1=0x0C9CBC20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
         0x00000000 0x0020C330 0x002463E4 0x00094160 0x01000000
Proceeding back via exception chain:
   Exception state (sv=0x1F736C80)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x2E895780)
      PC=0x9002E1CC; MSR=0x0000F030; DAR=0xE5CF3000; DSISR=0x42000000;
LR=0x8D76
5A8C; R1=0xF0D3A390; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.8.0:
Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC
Proceeding back via exception chain:
   Exception state (sv=0x1F736C80)
      PC=0x0020C8F4; MSR=0x00009030; DAR=0x00000014; DSISR=0x40000000;
LR=0x0020
C800; R1=0x0C9CBC20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
         0x00000000 0x0020C330 0x002463E4 0x00094160 0x01000000
   Exception state (sv=0x2E895780)
      PC=0x9002E1CC; MSR=0x0000F030; DAR=0xE5CF3000; DSISR=0x42000000;
LR=0x8D76
5A8C; R1=0xF0D3A390; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 7.8.0:
Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC


*********

If you roll out the NIO changes on a wider basis expect a flurry of
system crash reports from users. As these system crashes do cause lost
work due to a reboot this problem is very serious. It would probably be
a good idea to open a support case with Apple to get that problem fixed.
This is just a head's up so you do not stumble into the problem
unprepared.
-- 
Jens-Uwe Mager	<pgp-mailto:F476EBC2>
_______________________________________________
core-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/core-dev