Crash after switching focus
issueid=3988 11-17-2015 03:33 AM
Senior Member
Number of reported issues by hapro: 15
Crash after switching focus

This may or may not be the same crash described here (http://steamcommunity.com/app/333300...1136921002552/).

I started a new character and without moving or pressing any buttons, I started doing stuff in a browser on my second monitor. After a few seconds (it wasn't instantly when I switched to the browser), the ADOM screen faded and I realized it crashed when I tried to go back to it.

I was running the Steam version on Windows with the graphics settings set to ASCII and windowed mode.
Issue Details
Issue Number 3988
Project ADOM (Ancient Domains Of Mystery)
Category All Steam Versions
Status Fixed
Priority 1 - Highest
Affected Version ADOM r61 (v2.0.0)
Fixed Version ADOM r63 (v2.0.2)
Milestone Potential work pipeline
Users able to reproduce bug 5
Users unable to reproduce bug 0
Assigned Users jt
Tags (none)




11-20-2015 04:07 AM
Junior Member
Quote Originally Posted by jt
We identified the problem, it's fixed for R62. But it still needs some more testing before we release it.
I still get this crash in R62

11-20-2015 06:54 AM
The Creator
Two questions:
1. Are you using Windows 10?
2. Are you using the very latest build of Windows 10 or some earlier beta or prerelease?

#2 seems to be the cause for many such crash observations. It seems that earlier versions of Windows (and not ADOM) were broken in some respect and so far the observed problems managed to disappear whenever I got people to update to the very latest version of Windows 10. I'm keeping my fingers crossed here ;-)

11-20-2015 09:31 AM
Ancient Member
I am on Windows 7 64-bit and I can confirm it still crashes with r62, tested in two different computers (desktop and laptop).

Minimize ADOM with Alt+Tab, wait for a while while fiddling with other programs -> crash.
Leave ADOM in the foreground but just do nothing for a while -> crash.

100% of the time.

11-20-2015 09:33 AM
Ancient Member
By the way, I'm surprised you cannot reproduce, as with r61 it happened in 3 out of 3 Windows computers where I tried, and with r62 it has happened in 2 out of 2 at the moment... are you sure you are setting the ASCII mode and full screen? All the reports seem to be in ASCII and full screen.

11-20-2015 09:59 AM
Ancient Member
Quote Originally Posted by Al-Khwarizmi
I am on Windows 7 64-bit and I can confirm it still crashes with r62

100% of the time.
Not 100% for me but still crashes on win7. On my PC seems like crash is dependant on time spent away. Small switches to other windows work, while longer ones crash.

And I play windowed AScii [just checked settings]. so it is not just fullscreen thing

11-20-2015 10:06 AM
Ancient Member
Quote Originally Posted by Soirana
Not 100% for me but still crashes on win7. On my PC seems like crash is dependant on time spent away. Small switches to other windows work, while longer ones crash.
Yes, definitely. I mean 100% if you wait long enough (I didn't time it, but I guess around one and a half minute, as vdeogmer said in a previous post in the thread).

11-20-2015 12:00 PM
jt jt is offline
Administrator
I could reproduce the effect in my Windows 10 VM. Just set ADOM to ASCII mode and wait. It crashes after a short period. The tile mode works fine.

The fix in R62 doesn't seem to work on Windows 10.

11-20-2015 02:30 PM
Junior Member
I am using Windows 7 64-bit PC and Windows 8.1 laptop, both fully updated, both with high end Nvidia cards with the newest drivers. I have tried each renderer and still crashes every time. (Windowed ASCII mode).

Here is a report using the software renderer.

Problem Event Name: APPCRASH
Application Name: adom.exe
Application Version: 0.0.0.0
Application Timestamp: 564df0f1
Fault Module Name: noteye.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 564d82d0
Exception Code: c00000fd
Exception Offset: 00040c56
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 7571
Additional Information 2: 7571c1ae1223a9a1302e598203cdcafb
Additional Information 3: 88d3
Additional Information 4: 88d3e758a4704ba29644f779110b9d8d

11-20-2015 02:34 PM
Junior Member
and here is a report of using OpenGL. Different Fault Module Name.

Problem Event Name: APPCRASH
Application Name: adom.exe
Application Version: 0.0.0.0
Application Timestamp: 564df0f1
Fault Module Name: nvoglv32.DLL
Fault Module Version: 10.18.13.5891
Fault Module Timestamp: 563b6404
Exception Code: c00000fd
Exception Offset: 0008a8e5
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: c103
Additional Information 2: c10368083b108f836b176891945595a5
Additional Information 3: c365
Additional Information 4: c3655b10c13b89663ec0af13fbfd8a54

11-20-2015 02:43 PM
Junior Member
and this is with the SDL2 renderer

Problem Event Name: APPCRASH
Application Name: adom.exe
Application Version: 0.0.0.0
Application Timestamp: 564df0f1
Fault Module Name: nvd3dum.dll
Fault Module Version: 10.18.13.5891
Fault Module Timestamp: 563b6327
Exception Code: c00000fd
Exception Offset: 00625ce9
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 3518
Additional Information 2: 3518474852f77bf4f0791e31cf1feadf
Additional Information 3: 7a92
Additional Information 4: 7a9254722153abfeb4db435e3e98d0ab

11-20-2015 02:53 PM
Junior Member
Also, if i sit on the "choose renderer" screen, it doesn't crash. only while in the game world.

11-20-2015 04:33 PM
Junior Member
Quote Originally Posted by adom-admin
Two questions:
1. Are you using Windows 10?
2. Are you using the very latest build of Windows 10 or some earlier beta or prerelease?

#2 seems to be the cause for many such crash observations. It seems that earlier versions of Windows (and not ADOM) were broken in some respect and so far the observed problems managed to disappear whenever I got people to update to the very latest version of Windows 10. I'm keeping my fingers crossed here ;-)
Yeah I'm running the latest build of Windows 10, my updates are all installed and up to date.

11-20-2015 05:22 PM
Junior Member
Further testing on Win7 confirms Mizrach's feedback that the game is much less likely to crash on the title screen or unusual screens than in the game world.
I also tabbed out and found my desktop resolution was being played with at random.
Windows 10 and 7 aren't too far apart, but ideally ADOM should be CTD-free on both. They're the two most popular editions at present.

11-20-2015 07:09 PM
Junior Member
Crashing happens to me as well in R62 running on the latest Windows 10. It never happens during active playing, but when I switch away to simply walk away from the keyboard for several minutes, it eventually crashes, no exceptions.

11-20-2015 08:00 PM
jt jt is offline
Administrator
This was still happening in ASCII mode (with R62 on Windows XP, 7, 8.1 and 10) if the game was idling in the background. Fixed for R63.

11-20-2015 08:24 PM
Ancient Member
Is it also fixed when you spend a while doing nothing but the game is in the foreground? Because here, it also crashes.

11-20-2015 08:26 PM
jt jt is offline
Administrator
Yes, foreground/background doesn't really matter. There was a stack overflow when it was idling "too long". The Steam update for R63 will be available really soon.

11-20-2015 09:21 PM
Ancient Member
Awesome news! :)

11-20-2015 09:23 PM
jt jt is offline
Administrator
The update is available now (you might need to restart Steam to see it).

11-20-2015 10:06 PM
Junior Member
awesome! i believe this is fixed now. i've had the game minimized for a good 10 minutes with no crash atm. will let it go a bit longer to make sure. thanks!

+ Reply