- Steam or GOG
- Steam
- Single Player/Multiplayer
- Single
- Operating System
- Windows 10
- Terraria Version
- 1.4.4.9
- Controls Used
- Keyboard/Mouse
I usually put my computer to sleep when I head to work, and I turn it back on when I get home. Sometimes, if Terraria is running while this happens, the game crashes with the following error:
This error occurs only during wakeup (or perhaps the process of the computer going to sleep?), and it doesn't happen every time. Judging by the crash log, something is causing the render target of the game to be disposed during sleep or wake up, which means the game has nothing to draw to and it can't proceed. I'm not sure how best to record the circumstances for the crash, given that it happens on sleep/wake, but if you have any ideas I'd be willing to look into it more. I'm fairly well acquainted with d3d11, so although I don't have any experience with Xna directly I should be able to figure out what's going on in the background if I can catch it in the act.
EDIT: Even if we can't catch the cause, I think it shouldn't be too hard to just reinstantiate the render target when trying to access one that's been disposed of. That might help out if anything else somehow causes the rendertarget to be disposed of too.
This error occurs only during wakeup (or perhaps the process of the computer going to sleep?), and it doesn't happen every time. Judging by the crash log, something is causing the render target of the game to be disposed during sleep or wake up, which means the game has nothing to draw to and it can't proceed. I'm not sure how best to record the circumstances for the crash, given that it happens on sleep/wake, but if you have any ideas I'd be willing to look into it more. I'm fairly well acquainted with d3d11, so although I don't have any experience with Xna directly I should be able to figure out what's going on in the background if I can catch it in the act.
EDIT: Even if we can't catch the cause, I think it shouldn't be too hard to just reinstantiate the render target when trying to access one that's been disposed of. That might help out if anything else somehow causes the rendertarget to be disposed of too.
Last edited:
