|
Written by Hash
|
|
Friday, 01 February 2008 06:40 |
|
The OS X bug which was the subject of my last post turned out not to have anything to do with Parallels after all, but with Airport. In certain ad-hoc networks, joining the network makes kernel_task eat up real memory very fast, till the machine becomes unusable. On Panther, it would also cause mouse and keyboard freezes, but on Leopard this hasn't been happening. Turning off airport stops the memory leak, and even releases a chunk of real memory, but doesn't release all of it. I've found that if I create the ad-hoc network through the MacBook, and then have the Zaurus join it, I don't trip up this bug, but if the Zaurus is already connected to the network, and I have the MacBook join it (or create it - in case it isn't detected) that sends kernel_task gobbling memory. It's irritating, but as long as I'm careful about the order in which I have the machines join the network, I can avoid it. It does feel great to have Parallels back in action.
|
