If you are still crashing with resolutions higher than 4096 pixels in any one direction (for example, 5760x1080) after updating to 188.8.131.52, I'm sorry. I've put in as much troubleshooting as possible without being able to reproduce the issue in-house...which is my next step.
Right now, I'm running on a 2560x1440 monitor with a GeForce GTX 760. I'm going to see if I can get another two monitors attached to this guy this week in hopes of breaking the ultra-wide resolution barrier and I'll see if I can reproduce the issue under a debugger then.
It's currently looking like a write-after-free bug with a render target.
If anyone can attach a debugger to their Terraria.exe process patched to 184.108.40.206 with v0.7 before then and can get me any detail, I can work on patching it, but until then, I'm stuck.
Sorry for the delay.
You've been doing an awesome job :) Thanks so much. Hope one day, higher resolutions are supported natively.
where can i find the crash script
If you need any help with this... I'm running a 7680x1440 (plus some bezel correction) rig right now, using triple 27" displays. I'm not sure how the whole debugging thing would work, but if you'd be willing to guide me through that I'd be glad to see what kind of information I could get out of it for you. The game currently crashes out for me when I try to enter fullscreen. It'll work for a little bit, after which it'll throw an error in "clr.dll".
(I can be found on Steam under the username "SUXpanD". My screen name is "XpanD - Minecraft! (irrelevant MC server URL here)")
Some extra details on the crash, in case they may be useful. These are from the Event Viewer, two separate logged messages.
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 5B0938AA (5AFC0000) with exit code 80131506.
Faulting application name: Terraria.exe, version: 220.127.116.11, time stamp: 0x55a6a78d
Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348961e
Exception code: 0xc0000005
Fault offset: 0x000d38aa
Faulting process id: 0x542c
Faulting application start time: 0x01d0bf2d3bcbf443
Faulting application path: D:\Steam\steamapps\common\Terraria\Terraria.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: b0415ee6-2b20-11e5-8274-d43d7e387cde
Faulting package full name:
Faulting package-relative application ID:
Interesting, I just looked into the eventlog, but in my case the faulting module was pointing to raptr - I guess it's somehow taking over for video recording (this is from MSI).
After killing the raptr related processes, I still get the crash, but this time the module is clr.dll as well.
No luck with the debugger - it's just giving a general error about system.executionengine (something like that), but I can't switch to the debugger window, since the fullscreen terraria is blocking control (tried alt+tab, task manager, window key+tab, alt+esc).
Any more recommendation with the debugger? It's VS2012.
If you enable cooperative fullscreen, you should be able to alt-tab over and get more details.
Still no luck getting back to VS, even with cooperative fullscreen turned on.
What does that switch do anyway? Local coop?
Cooperative fullscreen mode is basically a borderless window. It plays nicer with multimonitor setups because it lets the desktop compositor help out.
Post a Comment