ITADN

Static lifetime of CTextureLoader causes textures to be released when ID3D11Device is already freed. (Maybe.)

#138Openbrittyazel 创建于 2025-11-10
Bug
B
brittyazelcommented
**Describe the bug** I have been noticing a large number of Gw2-64.exe related error events showing up in the Windows Event Viewer, and I noticed a pattern that _each and every_ event timestamp corresponds to the game closing. Testing this theory, I have now confirmed that 100% of the time that GW2 exits, I get a copy of this same error in the Windows Event Viewer. After removing Nexus from my game folder the errors completely stop, which leads me to believe Nexus is in some way triggering this error inadvertently. Googling would suggest that the error itself (0xc0000005) has something to do with illegal memory access violations. Likewise, this error is causing multiple gigabytes of error logs to build up weekly on my system that I need to keep running Disk Cleanup to remove. In order to diagnose this error further, I tried disabling all of my Nexus addons to see if the issue was with Nexus itself or one of the 3rd party addons, and I found that the issue was present even with all nexus addons disabled. I then clean reinstalled a fresh copy of Nexus without any addons or settings, and the error continued to show 100% of time the game is exiting. This leads me to believe that Nexus itself is the cause of these errors, not any specific addon. Lastly, to confirm that the issue is with Nexus and not my specific hardware or operating system, I carried out all of the above steps on my wife's computer, and experienced identical behavior. 100% of the time when Nexus is installed, Gw2-64.exe throws an error on exit. Both her system and mine both are showing the same exact error messages, with the exact same pattern, and with the exact same error logs building up and needing to be cleaned. This is the text of every error log that is reported: ``` Faulting application name: Gw2-64.exe, version: 1.0.0.1, time stamp: 0x690cff18 Faulting module name: Gw2-64.exe, version: 1.0.0.1, time stamp: 0x690cff18 Exception code: 0xc0000005 Fault offset: 0x000000000099bec8 Faulting process id: 0x3B4C Faulting application start time: 0x1DC51CCCD951C07 Faulting application path: C:\Program Files\Guild Wars 2\Gw2-64.exe Faulting module path: C:\Program Files\Guild Wars 2\Gw2-64.exe Report Id: 8ffd7eef-06b4-4b04-a06a-b37b7085b26c Faulting package full name: Faulting package-relative application ID: ``` **To Reproduce** Steps to reproduce the behavior: 1. Have Nexus installed in your GW2 folder. 2. Launch the game. 3. Exit the game. 4. See the error log within the "Administrative Events" section of the Windows Event Viewer. **Expected behavior** Nexus should not be triggering these error logs upon GW2 exiting. The game itself does not cause such error logs to occur, and it would be nice if Nexus did not either. **Screenshots** <img width="1290" height="823" alt="Image" src="https://github.com/user-attachments/assets/0ba59722-2446-4ba6-97d8-dde787ddd8a6" /> **Additional context** My system is running Windows 11 25H2, with a Ryzen 7 5800X3D CPU, and a Radeon RX 7900XT GPU. My wife's computer is also running Windows 11 25H2, but she has a Ryzen 7 5700X3D CPU, and a Radeon RX 5700XT GPU.
20 条评论