Opened 4 years ago

Last modified 18 months ago

#1977 new bug

Playing sounds freezes game

Reported by: vext01 Owned by:
Milestone: Future Keywords: openBSD



Angband seems to work great on OpenBSD (once working around ncurses detection -- reported as separate ticket). However, when sound is enabled, the game freezes, presumably at the point it needs to play a sound -- usually I am killing a thief in the town as a test.

Here is a trace of the frozen thread (SIGINT is me pressing ctrl+c):

Thread 1 received signal SIGINT, Interrupt.
0x000006d6ec539d4a in _thread_sys___thrsleep () at <stdin>:2
2       <stdin>: No such file or directory.
(gdb) bt
#0  0x000006d6ec539d4a in _thread_sys___thrsleep () at <stdin>:2
#1  0x000006d75741925c in _rthread_mutex_lock (mutexp=0x6d7a4314910, trywait=0, abstime=0x0) at /usr/src/lib/librthread/rthread_sync.c:151
#2  0x000006d719f03fde in SDL_mutexP () from /usr/local/lib/
#3  0x000006d6f739f80a in Mix_FadeInMusicPos () from /usr/local/lib/
#4  0x000006d4c5514c8c in game_event_dispatch (type=EVENT_SOUND, data=0x7f7ffffbb910) at game-event.c:43
#5  0x000006d4c5514f24 in event_signal_message (type=3313682592, t=<optimized out>, s=0x0) at game-event.c:180
#6  0x000006d4c5533928 in msgt (type=2, fmt=<optimized out>) at message.c:443
#7  0x000006d4c5565499 in py_attack_real (fear=<optimized out>, x=<optimized out>, y=<optimized out>) at player-attack.c:398
#8  py_attack (y=7, x=33) at player-attack.c:442
#9  0x000006d4c55086f6 in move_player (dir=<optimized out>, disarm=true) at cmd-cave.c:1061
#10 0x000006d4c5508d4d in do_cmd_walk (cmd=<optimized out>) at cmd-cave.c:1247
#11 0x000006d4c5509582 in process_command (ctx=CMD_GAME, cmd=0x6d4c5831520 <cmd_queue+2112>) at cmd-core.c:224
#12 0x000006d4c5509640 in cmdq_pop (c=1466044800) at cmd-core.c:252
#13 0x000006d4c55156ec in process_player () at game-world.c:632
#14 0x000006d4c55164c3 in run_game_loop () at game-world.c:729
#15 0x000006d4c5587175 in play_game (new_game=false) at ui-game.c:429
#16 0x000006d4c55b5df0 in main (argc=1, argv=0x7f7ffffbca38) at main.c:556

Sorry I have not had time to look deeper.

OpenBSD-current/amd64 on angband-4.0.5.


Change History (2)

comment:1 Changed 3 years ago by nckmccnnll

  • Keywords openBSD added
  • Milestone changed from Triage to Future

Marking all OpenBSD bugs as such and setting them to Future

comment:2 Changed 18 months ago by vext01


This is still an issue with angband-4.1.3.

Note: See TracTickets for help on using tickets.