Details
-
Bug
-
Resolution: Unresolved
-
Major
-
0.4.8-dev-153-g3e1a541 https://git.reactos.org/?p=reactos.git;a=commit;h=3e1a54151fdb2f513d5e1d4a374c2c973132493a
Description
Testing 0.4.14-dev-178-g90c5cac
Test done with a MSVC Build, MSVC_19.0.24213.1.
Test done in Win10 1803/VMware Workstation 12.
Test done using Vmware's SVGA driver from VMware Tools v12.0.1
This problem occurs after PR merge (contains 2 commits!)
https://github.com/reactos/reactos/pull/87
The problem is:
Access violation - code c0000005 (!!! second chance !!!)
nt!IoBuildDeviceIoControlRequest+2d [x:\src\master\reactos\ntoskrnl\io\iomgr\irp.c @ 896]
8046ce6d 0fb64830 movzx ecx,byte ptr [eax+30h]
The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
- This problem occurs when UnrealTournament game application initializes its OpenGL rendering engine, and the engine tries to go Full Screen Mode
- If we are in debug mode and use the 'g' command to continue, ReactOS doesn't crash/BSoD after this error, but desktop freezes with only mouse cursor being alive
- With no way to invoke a reboot with the mouse or keyboard, a forced reboot is required to recover the system
Reverting ONLY
https://git.reactos.org/?p=reactos.git;a=commitdiff;h=3e1a54151fdb2f513d5e1d4a374c2c973132493a
from the culprit PR makes the game usable again with the VM 3D OpenGL acceleration enabled, while it ACTUALLY FIXES one of the asserts specified in CORE-7727, related to the PR.
DON'T REVERT THE WHOLE PR!
DebugLogs describing the situation before and after the reversion are included, along one picture of the game working after the reversion