Behavior across the board (IE, FF, Chrome) is not what it should be.
The while(true){} loop is a total show stopper for chrome (the v8 lock
problem), would be worth seeing what affect releasing the v8 lock
within that loop has. This would put it on equal footing to IE and FF,
and would allow us to compare behavior with background threads running
at a lower priority (chrome) with bg threads running at normal
priority (ie,ff).On Thu, Feb 12, 2009 at 6:52 PM, Michael Nordman <[email protected]> wrote: > please see related http://b/issue?id=1587253 > > > On Thu, Feb 12, 2009 at 6:42 PM, <[email protected]> wrote: >> >> >> Comment #1 on issue 826 by erik.arvidsson: Worker threads hangs Chrome >> http://code.google.com/p/gears/issues/detail?id=826 >> >> Updated the test to inline gears_init.js >> >> Attachments: >> chrome-threads.html 4.8 KB >> >> -- >> 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 >> >
