Started by Screemer, April 19, 2011, 03:37:54 AM
Quote from: petrossa on April 24, 2011, 01:42:51 PMI'll try and not get you too distracted. I was talking about timer resolution and threads that use a waitfor can get thrown off course. Let it slide, no matter. Btw today 4 reboots, 3 crashes
Quote from: petrossa on April 23, 2011, 02:45:01 PMI've noticed changes to the preemptive taskmanager's algorythm. (i think, i have no access to it's code obviously)It shows most in the timer. Before an apps timer was given equal slices, but since some time (can't really say which build of win7) it seems like the timeslices are more staggered for standard apps under heavy load. Such as S3 wakeup.
Quote from: jeremy.collake on April 24, 2011, 03:36:07 PMI am releasing a new beta in a few minutes that makes an experimental change to the inter-process communication. The governor's 'sender thread' now waits 5 seconds before it transfers anything. I *believe* there is a theoretical condition where if events are sent too early during the initialization of the GUI then they can cause a subsequent crash. I am inserting other safety catches as well, but they are not in here yet. I'm mostly curious if this affects the crash.In addition, I'm evaluating the constructors of the couple global objects.Soon every component of the startup will have been checked ;o.I need to do some proper debugging of this too. As I said, I gotta spend more time coding, less talking, lol . Besides, I talk too much already ;p