Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.97a is out! (02/02/24); New blog post: Simulator Enhancements (03/13/24)

Pages: 1 [2]

Author Topic: Crashing in battle  (Read 5210 times)

robepriority

  • Captain
  • ****
  • Posts: 409
  • robepriority#2626
    • View Profile
Re: Crashing in battle
« Reply #15 on: September 23, 2020, 01:15:08 PM »

Tested with sound box unchecked on startup and useGLFinish set to true.

Doing a station defense against the pirate fleet armada:

Zoomed out, the game will hang, with a spike to 100% GPU and CPU usage. Closing out SS will also spike.



Tested the same battle, but zoomed in:

Game does not hang, even running the same battle with sound box checked.

robepriority

  • Captain
  • ****
  • Posts: 409
  • robepriority#2626
    • View Profile
Re: Crashing in battle
« Reply #16 on: September 23, 2020, 01:42:57 PM »

Does an actual crash always have a popup error message in addition to what's in starsector.log, or is it possible to crash with only errors in log?

I haven't seen a window pop up yet.

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 23987
    • View Profile
Re: Crashing in battle
« Reply #17 on: September 23, 2020, 03:24:25 PM »

Zoomed out, the game will hang, with a spike to 100% GPU and CPU usage. Closing out SS will also spike.

Tested the same battle, but zoomed in:

Game does not hang, even running the same battle with sound box checked.

Hmm. So this really goes sound like a graphics card/driver issue; I'm not sure what else I can suggest, unfortunately.

Does an actual crash always have a popup error message in addition to what's in starsector.log, or is it possible to crash with only errors in log?

A crash should either 1) produce a hs_err_pidXXXX.log file, or 2) (more normally) a popup and a more detailed error in the log.
Logged

robepriority

  • Captain
  • ****
  • Posts: 409
  • robepriority#2626
    • View Profile
Re: Crashing in battle
« Reply #18 on: September 23, 2020, 11:30:03 PM »

I looked at java's dump file during one of the hangs - the most notable being


Spoiler
Code
  27  Id: 410c.2308 Suspend: 1 Teb: 00000000`003f0000 Unfrozen
 # Child-SP          RetAddr               Call Site
00 00000000`17f3f998 00007ff8`f8147675     win32u!NtUserGetMessage+0x14
01 00000000`17f3f9a0 00000000`17de0d29     USER32!GetMessageA+0x45
02 00000000`17f3fa00 00007ff8`f7477bd4     OpenAL64!alcCloseDevice+0xd6c9
03 00000000`17f3faa0 00007ff8`f882ce51     KERNEL32!BaseThreadInitThunk+0x14
04 00000000`17f3fad0 00000000`00000000     ntdll!RtlUserThreadStart+0x21

  28  Id: 410c.500 Suspend: 1 Teb: 00000000`003f2000 Unfrozen
 # Child-SP          RetAddr               Call Site
00 00000000`1827f558 00000000`17dde531     OpenAL64!alcCloseDevice+0xb384
01 00000000`1827f560 00000000`17dd593a     OpenAL64!alcCloseDevice+0xaed1
02 00000000`1827f670 00000000`17de02cd     OpenAL64!alcCloseDevice+0x22da
03 00000000`1827f710 00000000`17ddad15     OpenAL64!alcCloseDevice+0xcc6d
04 00000000`1827f750 00007ff8`f7477bd4     OpenAL64!alcCloseDevice+0x76b5
05 00000000`1827f780 00007ff8`f882ce51     KERNEL32!BaseThreadInitThunk+0x14
06 00000000`1827f7b0 00000000`00000000     ntdll!RtlUserThreadStart+0x21

  29  Id: 410c.3ea0 Suspend: 1 Teb: 00000000`003f6000 Unfrozen
 # Child-SP          RetAddr               Call Site
00 00000000`0f37efe8 00007ff8`f87c7619     ntdll!NtWaitForAlertByThreadId+0x14
01 00000000`0f37eff0 00007ff8`f87c74d2     ntdll!RtlpWaitOnAddressWithTimeout+0x81
02 00000000`0f37f020 00007ff8`f87c72fd     ntdll!RtlpWaitOnAddress+0xae
03 00000000`0f37f090 00007ff8`f87db576     ntdll!RtlpWaitOnCriticalSection+0xfd
04 00000000`0f37f170 00007ff8`f87db3c0     ntdll!RtlpEnterCriticalSectionContended+0x1a6
05 00000000`0f37f1d0 00000000`17dcb6ba     ntdll!RtlEnterCriticalSection+0x40
06 00000000`0f37f200 00000000`17dcba1a     OpenAL64!alGetListeneriv+0x632
*** WARNING: Unable to verify checksum for C:\Program Files (x86)\Fractal Softworks\Starsector\starsector-core\native\windows\lwjgl64.dll
07 00000000`0f37f250 00000001`80004ed5     OpenAL64!alGetSourcei+0x7a
08 00000000`0f37f280 00000000`02eda7ea     lwjgl64!Java_org_lwjgl_openal_AL10_nalDeleteSources2+0xd5
[close]

I can also send the rest of the dump.

IntelĀ® IrisĀ® Plus Graphics graphics card, if that matters.

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 23987
    • View Profile
Re: Crashing in battle
« Reply #19 on: September 24, 2020, 09:01:38 AM »

Is this from running with sound on or no? It looks like there are two separate issues going on in your case, so it's hard to draw any conclusions without knowing the specifics of what you were doing with a particular test/crash.

Unfortunately, though, regardless of that, I'm not sure what else you can do. Zooming out causing the problem seems like a pretty solid indicator that the card/drivers just aren't going to be able to handle it, for whatever reason - whether issues in the driver or hardware limitations on the card. The OpenAL related issue, while an issue, I don't think has any bearing on this one.

Edit: a couple of other things to try, actually - from the other/similar thread, just to make sure you see them:
http://fractalsoftworks.com/forum/index.php?topic=19157.msg298646#msg298646
« Last Edit: September 24, 2020, 09:09:02 AM by Alex »
Logged

robepriority

  • Captain
  • ****
  • Posts: 409
  • robepriority#2626
    • View Profile
Re: Crashing in battle
« Reply #20 on: September 27, 2020, 11:24:19 AM »

I've used Intellij to try and debug one of the hangs. (sound disabled, fullscreen, station battle)

The only suspicious thread I found was a certain thread with the traverse() method. It still runs during the hang, the other threads that are running are inconspicuous (either waiting or system thread). Is it possible that something in the traverse() method is causing a livelock?


This is the stack trace:

Code
"Thread-4@1465" prio=5 tid=0x14 nid=NA runnable
  java.lang.Thread.State: RUNNABLE
  at com.fs.starfarer.combat.CombatState.traverse(Unknown Source:-1)
  at com.fs.state.AppDriver.begin(Unknown Source:-1)
  at com.fs.starfarer.combat.CombatMain.main(Unknown Source:-1)
  at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source:-1)
  at java.lang.Thread.run(Unknown Source:-1)

If there is a way for me to isolate the problem better, please share some tips with me.

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 23987
    • View Profile
Re: Crashing in battle
« Reply #21 on: September 27, 2020, 11:45:13 AM »

Hmm - not unless it's happening in the graphics or sound driver, no.
Logged

robepriority

  • Captain
  • ****
  • Posts: 409
  • robepriority#2626
    • View Profile
Re: Crashing in battle
« Reply #22 on: September 27, 2020, 11:57:09 AM »

Ah well - I guess I should just use another device.

It has similar specs(128 MB VRAM, 8 GB RAM) but less disk space.

It runs the battle that I've used for hang testing slowly (15-30 FPS in comparison to the hang device's 50-60), but it doesn't hang.

Sorry for the trouble, hopefully something pops up about drivers later on.

In the meantime, I'm going to be doing all the capital battles I missed out on ;)

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 23987
    • View Profile
Re: Crashing in battle
« Reply #23 on: September 27, 2020, 12:30:09 PM »

Glad you have at least a somewhat viable alternative! And, also sorry about the trouble - and thank you for your understanding :)
Logged
Pages: 1 [2]