make Hemlock not spend 100% CPU on trying to fetch events
Bug #538778 reported by
David Lichteblau
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Hemlock |
New
|
Undecided
|
Unassigned | ||
Bug Description
I had to revert the commit "make Hemlock not spend 100% CPU on trying to fetch events" by Nikodemus:
commit 35078e4b1ee9025
Author: Nikodemus Siivola <email address hidden>
Date: Mon Dec 21 12:00:59 2009 +0200
make Hemlock not spend 100% CPU on trying to fetch events
Now things are responsive and CPU utilization remains low even on
Darwin...
The reason I reverted it was that is caused 100% CPU spending on Linux
in dispatch-
Presumably the MacOS bug is back now.
In any case, we need test cases to catch this before a third commit breaks yet another OS.
Revision history for this message
| Nikodemus Siivola (nikodemus) wrote | #1 |
To post a comment you must log in.
It seems that thanks to intervening iolib changes this is not needed on Darwin either, anymore. At least I could not easily trigger the CPU-spinning here, anymore -- and it used to start happening by just starting Hemlock and letting it sit there.
...since you can observe the spinning, can you cook up a test-case? :)