High CPU usage of IDriver.exe
Hello,
I am testing my installations (created in InstallShield X) in VMWare. During the installation process, I need to run a special tool working with registry. The problem is, that when this tool is executed, IDriver.exe process suddenly starts "doing something" using 100% CPU so my tool is almost suspended. I always have to set low priority to the IDriver.exe and after that everything goes OK. I can not reproduce this behavior on a real machine.
Is there any solution? Does anybody know what the IDriver is doing?
Installed system is Windows XP Professional.
I am testing my installations (created in InstallShield X) in VMWare. During the installation process, I need to run a special tool working with registry. The problem is, that when this tool is executed, IDriver.exe process suddenly starts "doing something" using 100% CPU so my tool is almost suspended. I always have to set low priority to the IDriver.exe and after that everything goes OK. I can not reproduce this behavior on a real machine.
Is there any solution? Does anybody know what the IDriver is doing?
Installed system is Windows XP Professional.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello Jonvee,
thank you for the advice. Process Explorer shows the main CPU usage on thread belonging to IDriver.exe module.
There is no malware. Unfortunately :)
thank you for the advice. Process Explorer shows the main CPU usage on thread belonging to IDriver.exe module.
There is no malware. Unfortunately :)
ASKER
Well, using the process explorer, I found out the IDriver is executing my tool. If I set high priority to the tool, it works. But still... Why the IDriver needs so much on VMware?
If you're using VMWare, did you install VMWare Tools?
Also, howmuch RAM Is there in your PC and howmuch did you assign to the VMWare Virtual Machine?
Which OS are you running on VMWare?
Olrik
Also, howmuch RAM Is there in your PC and howmuch did you assign to the VMWare Virtual Machine?
Which OS are you running on VMWare?
Olrik
ASKER
computer has 2460MB available memory (1GB RAM), VMware machine has 2258MB (768MB RAM). I am using VMWare player. Both PC and the VMware machine has installed WinXP SP2.
Did you install VMWare tools?
Remember that VMWare is -another- OS within your OS and if you assign too much RAM to the VMWare machine it will start swapping and that'll make the system really slow. Is IDriver.exe a program that requires a bit of CPU Power or is it something that requires nothing at all?
I don't find it weird you can't reproduce this error on a normal machine because a normal machine would have about double the memory a VMWare machine has (If you're using the same machine that VMWare is running on.)
Remember that VMWare is -another- OS within your OS and if you assign too much RAM to the VMWare machine it will start swapping and that'll make the system really slow. Is IDriver.exe a program that requires a bit of CPU Power or is it something that requires nothing at all?
I don't find it weird you can't reproduce this error on a normal machine because a normal machine would have about double the memory a VMWare machine has (If you're using the same machine that VMWare is running on.)
Did you install VMWare tools?
Remember that VMWare is -another- OS within your OS and if you assign too much RAM to the VMWare machine it will start swapping and that'll make the system really slow. Is IDriver.exe a program that requires a bit of CPU Power or is it something that requires nothing at all?
I don't find it weird you can't reproduce this error on a normal machine because a normal machine would have about double the memory a VMWare machine has (If you're using the same machine that VMWare is running on.)
Olrik
Remember that VMWare is -another- OS within your OS and if you assign too much RAM to the VMWare machine it will start swapping and that'll make the system really slow. Is IDriver.exe a program that requires a bit of CPU Power or is it something that requires nothing at all?
I don't find it weird you can't reproduce this error on a normal machine because a normal machine would have about double the memory a VMWare machine has (If you're using the same machine that VMWare is running on.)
Olrik
ASKER
No, I did not install VMware tools, just the player. The IDriver is executing another executables within the installation, so I guess it should just wait for them to exit. Since the executable has lower or equal priority, the IDriver is taking more CPU(95% - 100%).
ASKER
I tried this on a VMware machine with 1500MB RAM and the problem persists, so I do not think it is about lack of memory.
Ok, Well i just noticed your VMWare Machine has more GB Assigned then your own XP Machine's OS will start getting slow and slow down VMWare aswell.
VMWare tools is basicly installing drivers for your VMWare machine. If you experience a slow mouse movement or programs booting slowly etc. try installing VMWare tools.
Also on the second reply.
VMWare might have 1500 MB RAM, but howmuch did the hosting PC have in total?
Olrik
VMWare tools is basicly installing drivers for your VMWare machine. If you experience a slow mouse movement or programs booting slowly etc. try installing VMWare tools.
Also on the second reply.
VMWare might have 1500 MB RAM, but howmuch did the hosting PC have in total?
Olrik
correcting the first sentence there:
<< Well i just noticed your VMWare Machine has more GB Assigned then your own XP Machine's OS will start getting slow and slow down VMWare aswell. >>
Well i just noticed your VMWare machine has more RAM Assigned to it then your hosting XP Machine will have left. It will start getting slow and slow down the VMWare machine aswell.
<< Well i just noticed your VMWare Machine has more GB Assigned then your own XP Machine's OS will start getting slow and slow down VMWare aswell. >>
Well i just noticed your VMWare machine has more RAM Assigned to it then your hosting XP Machine will have left. It will start getting slow and slow down the VMWare machine aswell.
ASKER
the second try was on a PC with Windows XP Professional, 64bit, with 6MB RAM. If it was a problem with memory, all software would be slow in the VMware. But it is just during the installation, when the InstallShield's IDriver is doing something instead of just waiting for my tool to exit. I do not experience any problems you mentioned (slow mouse movement etc.)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, it seems to be.
I've worked quite a bit with VMWare and i've always experienced some slowness in the VMWare machines i've set up. I hope that the flaw won't be in the way of your work :)
I hope i've helped enough.
Olrik
I hope i've helped enough.
Olrik
ASKER
Well, VMWare machines are slower, but this behavior is really strange. Even for a flaw in VMWare. I think it might be some little bug in InstallShield and another little on in VMWare and when these two get together... :)
I am just worried that if it can happen in VMWare, maybe it can happen on a customer's machine. That would be reall trouble.
There is a little workaround I am going to use until this is solved. My tool can set its process priority to High, so the IDriver has no chance.
I am just worried that if it can happen in VMWare, maybe it can happen on a customer's machine. That would be reall trouble.
There is a little workaround I am going to use until this is solved. My tool can set its process priority to High, so the IDriver has no chance.
I get your concern :)
I'd say use a machine with average Specifications and run a few CPU requiring programs then try to run your tool. If it doesn't require 100% like it does on VMWare you'll be sure it won't do it on client's pcs.
Olrik
I'd say use a machine with average Specifications and run a few CPU requiring programs then try to run your tool. If it doesn't require 100% like it does on VMWare you'll be sure it won't do it on client's pcs.
Olrik
ASKER
ProcessExplorer helped to realize what the IDriver.exe is doing. However, it seems to be a bug in VMWare. Thanks for help.
ASKER
yes, I will try this. Thank you for help
Been periodically following your progress, & pleased that you're aware of a temporary workaround :)
Good luck with the test suggested by Artellos. Thanks.
Good luck with the test suggested by Artellos. Thanks.
http://www.file.net/process/idriver.exe.html