[ros-bugs] [Bug 3259] 3d text screensaver causes memory read error
ReactOS.Bugzilla at www.reactos.org
ReactOS.Bugzilla at www.reactos.org
Thu Jun 5 23:10:00 CEST 2008
http://www.reactos.org/bugzilla/show_bug.cgi?id=3259
--- Comment #2 from aicommander <aicommander at gmail.com> 2008-06-05 23:09:59 CET ---
I now get new errors after I run the screensaver a couple of times.
r33860
(subsystems/win32/win32k/ntuser/cursoricon.c:158) Removing pointer!
(subsystems/win32/win32k/objects/gdiobj.c:576) Attempted to free foreign
handle: 0x4040547 Owner: 0x174 from Caller: 0x1d0
(subsystems/win32/win32k/objects/gdiobj.c:578) Type = 0x40404, KernelData =
0x8D27E8F8, ProcessId = 0x00000174
(subsystems/win32/win32k/objects/gdiobj.c:763) Tried to lock object
(0x0E010238) of wrong owner! ProcessId = 000001D0, HandleProcessId = 00000174
(subsystems/win32/win32k/objects/gdiobj.c:763) Tried to lock object
(0x0E010238) of wrong owner! ProcessId = 000001D0, HandleProcessId = 00000174
Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page
Fault)
Memory at 0x0000002C could not be read: Page not present.
kdb:> bt
[7hEip:
<win32k.sys:8ab65 (subsystems/win32/win32k/objects/dc.c:1372
(@IntGdiCopyFromSaveState at 12))>
Frames:
<win32k.sys:78d72 (subsystems/win32/win32k/ntuser/windc.c:239
(@DceReleaseDC at 8))>
<win32k.sys:78e0d (subsystems/win32/win32k/ntuser/windc.c:844
(@UserReleaseDC at 12))>
<win32k.sys:75831 (subsystems/win32/win32k/ntuser/simplecall.c:387
(NtUserCallOneParam at 8))>
<NTOSKRNL.EXE:96f6a (ntoskrnl/ke/i386/trap.s:244 (KiFastCallEntry))>
<ntdll.dll:5dea>
<3dtext.scr:158e>
<3dtext.scr:1b73>
<user32.dll:38f13>
<user32.dll:3901b>
<ntdll.dll:5d31>
<user32.dll:24560>
<user32.dll:25406>
<3dtext.scr:1d0b>
<3dtext.scr:1498>
<3dtext.scr:1b73>
<user32.dll:38f13>
<user32.dll:39261>
<user32.dll:3953c>
<3dtext.scr:1ada>
<3dtext.scr:1c6a>
<3dtext.scr:1902>--- Press q to abort, any other key to continue ---
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Ros-bugs
mailing list