non-troppo
Member
Using the wonderful Process Explorer[1] for logging GDI resource of ParallelsToolsCenter.exe (3188) running in bootcamp XP Pro SP2, it is clear that Parallels Tools is suffering from a resource leak. After several hours of use, GDI usage is >7000 (seems to partially depend on the applications used).
Although there is a 10000 GDI limit in XP, this causes the technical computing suite Matlab 7.3 to start failing to produce graphics output. Killing parallelstoolscenter.exe solves the Matlab issues immediately.
As an aside, killing parallelstoolscenter.exe also drops CPU use of parallels by 3-4%, which may make a slight difference if you were running off battery. It seems parallelstoolscenter.exe is constantly accesing the registry, around 250kb/s I/O Other as logged using Process Explorer...
[1] http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx
Although there is a 10000 GDI limit in XP, this causes the technical computing suite Matlab 7.3 to start failing to produce graphics output. Killing parallelstoolscenter.exe solves the Matlab issues immediately.
As an aside, killing parallelstoolscenter.exe also drops CPU use of parallels by 3-4%, which may make a slight difference if you were running off battery. It seems parallelstoolscenter.exe is constantly accesing the registry, around 250kb/s I/O Other as logged using Process Explorer...
[1] http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx