[Bug 22580] RegisterWaitForSingleObject() with tmo=0 causes 100% CPU load

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=22580





--- Comment #62 from joakim.tjernlund at transmode.se  2010-05-18 13:51:33 ---
(In reply to comment #61)
> (In reply to comment #60)
> > > So far there is exactly 0 (zero) apps affected by this problem. Once again,
> > 
> > You don't know that. You are just guessing.
> 
> Unless proven otherwise this a matter of the fact. Please stop speculating.

You are speculating too.

> 
> > > crypt32.dll is a system library (and not an application), and it looks like
> > > win9x version of the DLL uses undocumented quirk of
> > > RegisterWaitForSingleObject()
> > > implementation which doesn't exist on newer Windows versions.
> > 
> > Come on, why do you keep repeating this false claim?
> 
> That's the fact. Please read again all the comments in this report.

It is false that it is an undocumented quirk which I made clear
in my next sentence.
> 
> > It is documented and verified for Windows < Vista.
> 
> No one, except win9x version of crypt32.dll uses RegisterWaitForSingleObject()
> that way. Please read once again in the comments how much MSDN could be
> trusted regarding API behaviour, all the Wine history is about that.

Possibly no one but win9x uses RegisterWaitForSingleObject() in this way.

> 
> > You think XP is dead? Think again.
> 
> You went too far with your speculations. We are talking about specific API
> behaviour a win9x version of a single DLL depends upon.

What I meant is that any app that was written for and built on XP could
also use this "feature".

> 
> > > And once again, there is no any justification or need to use win9x version
> > > of crypt32.dll under Wine, built-in version works just fine. Try to use it
> > > for instance under Vista, then in the case of a bug report it Microsoft,
> > > let us know how it goes.
> > 
> > This I can agree with but once again, we have left this particular
> > dll behind us. It is just one way of triggering this particular bug.
> 
> You forgot (once again) to list the other ones. If you don't know them
> please stop speculating.

I didn't forget but the statement still holds, any app using the same
"feature" will not work in Wine. I don't know if there are any
but it is not impossible.

> 
> > > > Consider that you don't even want to check your 100% CPU bugs
> > > > wrt. to this problem.
> > > 
> > > Feel free to do that in your own free time, Wine is an open source project
> > > developed by volunteers. Be our guest.
> > 
> > I just a causal Wine user from time to time. It is even more unlikely I will
> > do that than a Wine developer that cares does it.
> 
> Please read the comment #16 once again.
> 
> > It is a bug in Wine, plain and simple.
> 
> So much for a report resolved as INVALID.

I didn't agree to that, but I accept it.
We just don't agree whether Wine should try to address this before
some approved app has been proven to need this to be on the safe side
or wait until someone actually hits this, which may never happen.

I don't have anything more to add, hopefully this will be
the last time this issue is discussed, time will tell.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.