WAIT. I thought PID 199526 is spinning on the same futex, but I noticed that the address (1st argument) to futext in the above excerpt is bumped by 4 each time it is called (!!!). Is this related to the issue of valgrind needing to support more than 1500 threads to run mochitest under it(!?) Bug 1629433 There seems to be a problem of - too many threads being created. - these seem to wait on MANY futexes, - the wait on different futexes seems to be done in a busy loop manner, at least under a bad condition which I observe locally, thus resulting in high CPU load, and way too slow valgrind execution. These seem to all related.
Bug 1636945 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
WAIT. I thought PID 199526 is spinning on the same futex, but I noticed that the address (1st argument) to futex in the above excerpt is bumped by 4 each time it is called (!!!). Is this related to the issue of valgrind needing to support more than 1500 threads to run mochitest under it(!?) Bug 1629433 There seems to be a problem of - too many threads being created for TB mochitest, - these seem to wait on MANY futexes, - the wait on different futexes seems to be done in a busy loop manner, at least under a bad condition which I observe locally, thus resulting in high CPU load, and way too slow valgrind execution. These seem to all related. Something is terribly wrong under the hood of mochitest.