winedevice taking up 100% after wine cmd
damjan.jov at gmail.com
Fri Nov 4 02:55:02 CDT 2011
On Thu, Nov 3, 2011 at 10:05 PM, Hin-Tak Leung <hintak_leung at yahoo.co.uk>wrote:
> I just had a rather odd incident earlier today when I just launched "wine
> cmd", and saw that my process monitor max-out to 100% - and it continued,
> until I finished what I intended to do and exited cmd, minutes later. I
> wasn't doing anything else and no typing anything in the cmd console
> either, so that was curious. It was winedevice taking up 100%.
> I tried wine cmd later but couldn't get that odd behavior any more. But is
> there any reason why winedevice should go into a spin?
> This is fedora 15 x86_64 running 32-bit wine I built myself.
The winedevice process just loads a (Windows) device driver and runs it.
What driver is being loaded?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wine-devel