"Follow" function in watch window crashes in replays or when playing as a spectator
Bug #1206211 reported by
wl-zocker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Fix Released
|
Medium
|
cghislai |
Bug Description
I guess the title says it all. Tested in r6880, no useful output in stdout.
I do not know if related, but when I follow a worker via that feature in a normal game, the watch window seems to "hang" for short moments. This is not the case in the main window.
Related branches
lp:~widelands-dev/widelands/log_messages
- SirVer: Needs Information
-
Diff: 1271 lines (+343/-161)35 files modifiedsrc/chat.cc (+100/-1)
src/chat.h (+1/-6)
src/debugconsole.cc (+0/-4)
src/gamecontroller.cc (+2/-30)
src/log.h (+0/-1)
src/logic/game.cc (+3/-1)
src/logic/game.h (+4/-1)
src/logic/immovable.cc (+1/-0)
src/logic/notification.h (+1/-2)
src/logic/player.cc (+1/-1)
src/logmessage.h (+41/-0)
src/network/internet_gaming.cc (+0/-9)
src/network/internet_gaming.h (+0/-3)
src/network/netclient.cc (+0/-9)
src/network/netclient.h (+1/-1)
src/network/nethost.cc (+0/-7)
src/save_handler.cc (+8/-11)
src/ui_basic/panel.h (+1/-1)
src/ui_basic/unique_window.cc (+2/-2)
src/ui_basic/window.cc (+15/-6)
src/ui_basic/window.h (+1/-0)
src/wlapplication.cc (+3/-1)
src/wui/chatoverlay.cc (+86/-18)
src/wui/chatoverlay.h (+3/-0)
src/wui/game_main_menu_save_game.cc (+11/-9)
src/wui/game_main_menu_save_game.h (+3/-1)
src/wui/gamechatpanel.cc (+2/-1)
src/wui/interactive_base.cc (+14/-0)
src/wui/interactive_base.h (+12/-0)
src/wui/interactive_gamebase.cc (+3/-4)
src/wui/interactive_gamebase.h (+4/-3)
src/wui/interactive_player.cc (+3/-9)
src/wui/interactive_player.h (+0/-3)
src/wui/interactive_spectator.cc (+9/-11)
src/wui/watchwindow.cc (+8/-5)
Changed in widelands: | |
assignee: | nobody → cghislai (charlyghislain) |
Changed in widelands: | |
status: | Confirmed → In Progress |
Changed in widelands: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Thanks for noticing and reporting this issue.
I am also able to trigger this when playing a multiplayer game as spectator, and the error message does indeed indicate this could be the reason: Player: :player (this=0x0) at /home/user/ widelands/ src/wui/ interactive_ player. h:68 player( m_player_ number) ;
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ac56df in Interactive_
68 return game().
I believe there should be a stderr file in the same place as stdout on Windows, so you might want to check that for more information in the future. :)