Updates:
Labels: -Pri-0 Pri-1
Comment #5 on issue 4759 by [email protected]:
ConditionVariableTest.LargeFastTaskTest hang with Application Verifier
http://code.google.com/p/chromium/issues/detail?id=4759
I couldn't tell who might have changed this to a P0, or why. It is not
obvious this
is blocking so much development for so many developers.
I'm away on vacation, but my distant memories of the design of this leave
me very
doubtful that there is a deadlock (unless semantics of lock constructs have
been
changed significantly).
For now, I'll change the level to P-1, and I'll look into the issue when
I'm back.
rvargas's comment about worker threads seems orthogonal to the issue at
hand. If
there is a bug in the current implementation, it should be fixed. It is
doubtful
that a complete rewrite to an alternate threading model would be a bug free
as the
current implementation (and there have been arguments about this
architectural
decision in the past). If this architectural change is to be made, it
should be done
based on a clear analysis and reasoning, and not as an approach to work
around a bug.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
