To slow things down. ATM there is a fault created when the mouse moves
with updates, creates and destroying region handles. The kernel fault
occurs inside SEH which should not happen right?
What we need is a semaphore that is used for the whole handle manager.
This is my point over the years about the stability inside win32k. It
running full bore, spinning out of control. Surprised it still works
after turning everything on in my tree.
On Sun, Jan 3, 2010 at 3:26 AM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
Why the KeEnterCriticalRegion?
jimtabor(a)svn.reactos.org wrote:
- if (pAttr) FreeObjectAttr(pAttr);
+ if (pAttr)
+ {
+ KeEnterCriticalRegion();
+ FreeObjectAttr(pAttr);
+ KeLeaveCriticalRegion();
+ }
break;