Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Assert failure on autogame end #1398

Closed
wzdev-ci opened this issue Jan 11, 2010 · 5 comments
Closed

Assert failure on autogame end #1398

wzdev-ci opened this issue Jan 11, 2010 · 5 comments

Comments

@wzdev-ci
Copy link
Contributor

keyword_autogame resolution_fixed type_bug | by Per


I left an autogame on during the night, and in the morning the following crash greeted me:

info    |02:58:15: [seq_Play] unable to open 'sequences/end.ogg' for playback
error   |02:58:15: [widgSetButtonState] Couldn't find button or clickable widget by ID
error   |02:58:15: [widgSetButtonState] Assert in Warzone: widget.c:1095 (!"Couldn't find widget by ID"), last script event: 'N/A'
warzone2100: widget.c:1095: widgSetButtonState: Assertion `!"Couldn't find widget by ID"' failed.
**'**'
Program received signal SIGABRT, Aborted.
0x00000030fb832f05 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Missing separate debuginfos, use: debuginfo-install alsa-lib-1.0.21-2.fc10.x86_64 expat-2.0.1-8.fc10.x86_64 freetype-2.3.7-3.fc10.x86_64 libpng-1.2.37-1.fc10.x86_64 libvorbis-1.2.0-7.fc10.x86_64 libxcb-1.1.91-8.fc10.x86_64
(gdb) bt
#0  0x00000030fb832f05 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00000030fb834a73 in abort () at abort.c:88
#2  0x00000030fb82bef9 in __assert_fail (assertion=0x6b6de7 "!\"Couldn't find widget by ID\"", file=0x6b6504 "widget.c", line=1095, function=0x6b7100 "widgSetButtonState") at assert.c:78
#3  0x00000000005dacc5 in widgSetButtonState (psScreen=0x1c42120, id=9, state=0) at widget.c:1095
#4  0x00000000004f0c6a in intResetScreen (NoAnim=0) at hci.c:1145
#5  0x00000000005319cd in missionResetInGameState () at mission.c:2695
#6  0x00000000005319fa in _intAddMissionResult (result=0, bPlaySuccess=1) at mission.c:2708
#7  0x0000000000531f27 in intAddMissionResult (result=0, bPlaySuccess=1) at mission.c:2869
#8  0x00000000005ce23c in displayGameOver (bDidit=0) at wrappers.c:424
#9  0x000000000058a040 in scrGameOverMessage () at scriptfuncs.c:3238
#10 0x00000000005ed2c5 in interpRunScript (psContext=0x2922ca0, runType=IRT_EVENT, index=2, offset=0) at interpreter.c:768
#11 0x00000000005e9955 in eventFireTrigger (psTrigger=0x28dc410) at event.c:1123
#12 0x00000000005e9aae in eventProcessTriggers (currTime=60600) at event.c:1163
#13 0x000000000051c658 in gameLoop () at loop.c:191

I could not reproduce it manually.


Issue migrated from trac:1398 at 2022-04-15 20:52:53 -0700

@wzdev-ci
Copy link
Contributor Author

Per commented


I believe that this happens because the game is waiting in end game/score dialog because of a game loss, when the game ends and tries to start the end game/score dialog once more.

@wzdev-ci
Copy link
Contributor Author

Zarel set resolution to fixed

@wzdev-ci
Copy link
Contributor Author

Zarel changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

Zarel commented


Fixed in 2.3 beta 8.

It's the generic intResetScreen crash.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jul 3, 2010

me@... uploaded file warzone2100.gdmp-Onpq5j (18.2 KiB)

dump file

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant