Comment 66 for bug 792896

On August 12, 2011 01:48:57 am Daniel wrote:
> Just wanted to add that setting the CPU affinity worked around the problem
> for me. Hope that helps some people out.

Thank you! Yes this helps a lot. It confirms that the issue is one of
threading, probably expiring cache. And there are ways for the program itself
to request affinity.

I suspect that somebody at Apple though about this and affinity is ON by
default - would explain why Apple is so unaffected. I did not research links
to substantiate my hypothesis. Windows systems tend to have more threads
running around (antivirus!) which would explain why the cache expires/corrupts
more often.

On Linux we can use something like
* http://www.ibm.com/developerworks/linux/library/l-affinity/index.html
* http://www.linuxjournal.com/article/6799

And on Windows something like
* http://msdn.microsoft.com/en-us/library/ms686223%28v=vs.85%29.aspx

For the short term:
* Linux http://www.linuxcommand.org/man_pages/taskset1.html
* Windows http://www.addictivetips.com/windows-tips/how-to-set-processor-
affinity-to-an-application-in-windows/

Performance trade-off:
* https://lanvu.wordpress.com/tag/setprocessaffinitymask/

Now it is a matter of time to implement and test...