d2dx icon indicating copy to clipboard operation
d2dx copied to clipboard

Occasional crashes in 0.99.516 and 512c

Open Birdsong243 opened this issue 3 years ago • 18 comments

First, thank you for your great work on this project. It has been perfectly stable for me until now.

I am using Windows 10, game version 1.14d, and Plugy 14.02. I have had some intermittent crashes since the switch to SGD2FreeRes.

When using version 512c (without MOP, all other options default), the game would sometimes crash after I alt-tabbed out and tried to alt-tab back in.

Also, when using version 516 tonight (with MOP, all other options default), the game crashed once when I was paging through my Plugy extended stash.

These are crashes to desktop -- the game closes and displays the default Blizzard error dialog: "The application encountered an unexpected error."

If I can provide any other information that would be helpful, just let me know.

Birdsong243 avatar May 17 '21 04:05 Birdsong243

Hmm sorry to hear that. I have done most testing on 1.13d so far, I will switch to 1.14d and see if I can catch this crash. I think you gave all the info I need, thanks.

bolrog avatar May 17 '21 06:05 bolrog

I'm also experiencing at least the alt tab crashing. I haven't had time to test newer versions yet but I can say with certainty that 0.99.510 never crashes for me when switching focus to or from the game, but 0.99.511 does. It's pretty frequent too. It also seems to always happen if I leave the game minimized for more than a minute or two. Once I tab back to the game it will immediately crash. I can leave 0.99.510 minimized for hours and it won't crash. The error I get is always the same unhandled exception.

The crash

I'm using PlugY 14.02, Windows 10 19041.985, and 1.13d.

fapmilk avatar May 18 '21 01:05 fapmilk

Thanks for the info, this is really valuable in pinning down the problem!

bolrog avatar May 18 '21 04:05 bolrog

Any particular settings you've changed in PlugY.ini? Any D2DX settings changed from defaults?

bolrog avatar May 18 '21 05:05 bolrog

My PlugY settings are default except for the following:

[WORLD EVENT] ActiveWorldEvent=0 TimeBeforeAutoSellMin=1 TimeBeforeAutoSellMax=1

So I normally have the World Event disabled (but set to spawn the Diablo clone quickly if I enable it). My crashes occurred with the World Event disabled.

My D2DX settings are default except for nologo=true. (The logo overlaps the PlugY version number :) )

I haven't been able to replicate these crashes so far. I've been testing with the most recent versions of D2DX. These intermittent problems are hard to pin down!

Birdsong243 avatar May 18 '21 18:05 Birdsong243

Ok! I'll be testing with those settings, keeping the game in the background for a while. Are you usually tabbed out for 4-5 mins?

Are you usually in town when it happens? And is the stash usually open?

Edit: so far no crashes... both 1.13d and 1.14d. :(

bolrog avatar May 18 '21 18:05 bolrog

I think I was in town with the stash closed when I had the first alt-tab crash. I'd say I was tabbed out for about 5 minutes. I still can't duplicate the alt-tab crash today.

I'll do some testing tomorrow to see if I can duplicate the in-game crash. That happened in town with the stash open after I had done a few dozen Travincal runs.

Birdsong243 avatar May 18 '21 23:05 Birdsong243

I had a little time test some and the latest version, 0.99.518b, seems totally stable. I can't get it to crash, which is great!

I also tried 0.99.511 again and I can still reproduce a crash within seconds of entering the game. I just have to open my shared stash and then alt tab once or twice and it crashes. Not sure if that helps to fix anything. My changed PlugY settings are below.

Param=-3dfx -direct -txt ActivePrintPlugYVersion=0 OpenSharedStashOnLoading=1

Also forgot to mention last time that I also use a font replacement to fix the number 5. I can't imagine that would be an issue though. And like I said the latest version seems completely stable.

fapmilk avatar May 19 '21 03:05 fapmilk

This sounds hopeful, maybe I resolved the issue unknowingly in the recent changes. I'll keep the issue open until you've had time to test it some more.

bolrog avatar May 19 '21 06:05 bolrog

I just had another in-game crash. This was with version 517. Here is what I was doing at the time:

  • Started the game and swapped back and forth between several characters about 6 or 7 times, moving gear around with shared stash.
  • Had Firefox open and alt-tabbed back and forth a few times while swapping gear around.
  • Was standing in Kurast Docks with the extended (not shared) stash open when the game crashed to desktop. I think it may have happened at the moment that I moused over a piece of gear.

I'll try version 519 when I have some more time to play.

Birdsong243 avatar May 19 '21 21:05 Birdsong243

Sorry to keep bringing the bad news. I had another crash with 519. Started the game in Harrogath, killed Pindle and a few things in Halls of Anguish, and took TP back to town. The game crashed when I clicked to take the Frigid Highlands waypoint.

Birdsong243 avatar May 20 '21 16:05 Birdsong243

Thanks, I appreciate all details!

I think I managed to reproduce this now.

Edit: The bug seems to be in sgd2freeres, and I've filed an issue in Mirs repository. Hopefully it can be fixed soon.

See https://github.com/mir-diablo-ii-tools/SlashGaming-Diablo-II-Free-Resolution/issues/40 for my description.

bolrog avatar May 20 '21 19:05 bolrog

Another twist: it turns out it happens in PlugY without sgd2freeres as well. At least Mir was able to reproduce it there. Hm.

bolrog avatar May 30 '21 10:05 bolrog

Hmm, that's surprising. I have spent a lot of time playing using D2DX in the past two months. I did not have any crashes until the resolution mod changed from D2HD to sgd2freeres. After the change, my crashes started almost immediately.

I just noticed the BlizzardError folder with crash logs and .dmp files. I don't know if any of the info there would be helpful.

Birdsong243 avatar May 30 '21 14:05 Birdsong243

They might be! If you can find a log in there from one of the occurrences, it may help.

Edit: It's possible that the repro case I sent to Mir was of a different bug that just happened to affect PlugY without sgd2freeres. But I'll keep looking for the problem.

bolrog avatar May 30 '21 16:05 bolrog

Hmm, that's surprising. I have spent a lot of time playing using D2DX in the past two months. I did not have any crashes until the resolution mod changed from D2HD to sgd2freeres. After the change, my crashes started almost immediately.

This has been my experience as well. I never crashed in any version, or any mod, until the swap from D2HD to SGD2FreeRes.

I should note that, just like two weeks ago when I last posted, D2DX still seems completely stable for me. Still zero crashes since the last time I posted.

fapmilk avatar May 31 '21 00:05 fapmilk

Maybe there was a different crash that happened in earlier versions, now fixed. And maybe there's a crash that happens with PlugY (with or without sgd2freeres).

bolrog avatar Jun 01 '21 19:06 bolrog

I'll keep testing with the latest versions. If I run into another crash, I'll post the logs and additional details.

Birdsong243 avatar Jun 02 '21 14:06 Birdsong243