https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
--- Comment #5 from Paul Floyd <pjfl...@wanadoo.fr> ---
(In reply to Tavian Barnes from comment #4)
> I guess? I'm surprised that valgrind will totally starve a thread by
> default.
>
> This may be a dupe of https://bugs.kde.org/show_bug.cgi?id=343357 anyway.
It can happen. The default Valgrind scheduler is well, no scheduling. There's
just a global lock (using FIFO reads and writes). When the running thread
releases the lock it's pot luck as to which thread gets to take it. And I
suspect that there are cases where the running thread is hot in the cache and
so it keeps taking the lock.
--
You are receiving this mail because:
You are watching all bug changes.
