Eric-ThierryM
Bit poster
I any of you are running MS Windows as Guest OS on a Mac running Mountain Lion, are you getting those constant messages in the Mac Console:
10/8/12 3:15:25.617 PM com.apple.launchd.peruser.501[194]: (com.apple.pbs[333]) Exited: Killed: 9
10/8/12 3:15:25.000 PM kernel[0]: memorystatus_thread: idle exiting pid 333 [pbs]
The above is just one of about 6 processes that keeps being killed and re-open constantly when I run Parallels. I get about 1,000 iterations per hour. I can also see in the Activity Monitor utility the processes crashing then being re-open in no time (probably by the Mac OS), just to be killed again. About 6 to 8 processes are affected.
This does not affect the operation of Windows nor the Mac - it probably just slows down the Mac and is certainly not normal behavior. I tested with various Parallels images (XP and Windows 7) and the behavior is the same. I had not seen this when I was running Lion - only happened after I upgraded to Mountain Lion with the latest version of Parallels.
I raised a ticket with Parallels support team and am awaiting an answer. It would be good to find out whether this is happening with other similar deployments.
Would you mind checking your Mac Console and reporting to this thread?
Thanks a bunch!
Eric
10/8/12 3:15:25.617 PM com.apple.launchd.peruser.501[194]: (com.apple.pbs[333]) Exited: Killed: 9
10/8/12 3:15:25.000 PM kernel[0]: memorystatus_thread: idle exiting pid 333 [pbs]
The above is just one of about 6 processes that keeps being killed and re-open constantly when I run Parallels. I get about 1,000 iterations per hour. I can also see in the Activity Monitor utility the processes crashing then being re-open in no time (probably by the Mac OS), just to be killed again. About 6 to 8 processes are affected.
This does not affect the operation of Windows nor the Mac - it probably just slows down the Mac and is certainly not normal behavior. I tested with various Parallels images (XP and Windows 7) and the behavior is the same. I had not seen this when I was running Lion - only happened after I upgraded to Mountain Lion with the latest version of Parallels.
I raised a ticket with Parallels support team and am awaiting an answer. It would be good to find out whether this is happening with other similar deployments.
Would you mind checking your Mac Console and reporting to this thread?
Thanks a bunch!
Eric