boost::too_many_args: during battle

Bug #1351620 reported by GunChleoc
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Fix Released
Critical
Unassigned

Bug Description

To reproduce, start a single player game with Golden Peninsula and build a barrier and a FOrtress to get north, then attack the AI.

revno: 7162

Log:

Vision check successful for player 2
took 30ms
 Reading Player Message Data ... took 1ms
 Reading Objective Data ... took 1ms
 Reading Scripting Data ... took 4ms
 WL_Map_Loader::load_map_complete() took 172ms
Game: Read_Complete took: 176ms
Game: Reading Player Economies Info ... took 2ms
Game: Reading Command Queue Data ... took 32ms
Game: Parsing messages ... took 0ms
Game: Reading Interactive Player Data ... took 2ms
Game_Loader::load() took 728ms
Done reloading the game from replay
Replay writer has started
[sync] Reset
ComputerPlayer(2): initializing (2)
Forcing flag at (43, 59)
Message: adding (wh) (warehouse) 1
Forcing flag at (42, 21)
Message: adding (wh) (warehouse) 2
Cmd_EnemyFlagAction::execute player(1): flag->owner(2) number=11
Fata exception: boost::too_many_args: format-string referred to less arguments than were passed
Game: Writing Preload Data ... took 192ms
Game: Writing Game Class Data ... took 0ms
Game: Writing Player Info ... took 9ms
Game: Writing Map Data!
Writing Elemental Data ... took 12ms
 Writing Player Names And Tribe Data ... took 0ms
 Writing Port Spaces Data ... took 0ms
 Writing Heights Data ... took 1ms
 Writing Terrain Data ... took 14ms
 Writing Player Start Position Data ... took 0ms
 Writing Player Message Data ... took 2ms
 Writing Resources Data ... took 5ms
 Writing Map Extra Data ... took 43ms
 Writing Map Version ... took 0ms
 Writing Allowed Worker Types Data ... took 0ms
 Writing Flag Data ... took 2ms
 Writing Road Data ... took 0ms
 Writing Building Data ... took 1ms
 Writing Map Objects ... took 34ms
 Writing Flagdata Data ... took 1ms
 Writing Roaddata Data ... took 1ms
 Writing Buildingdata Data ... took 51ms
 Writing Node Ownership Data ... took 2ms
 Writing Exploration Data ... took 3ms
 Writing Players Unseen Data ... took 18ms
 Writing Scripting Data ... took 45ms
 Writing Objective Data ... took 4ms
 Map_Saver::save() took 239ms
Game: Writing Map Data took 251ms
Game: Writing Player Economies Info ... took 0ms
Game: Writing Command Queue Data ... took 1041ms
Game: Writing Interactive Player Data ... took 0ms
Game_Saver::save() took 1493ms
SaveHandler::save_game() took 1570ms
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::io::too_many_args> >'
  what(): boost::too_many_args: format-string referred to less arguments than were passed
Aborted (core dumped)

Tags: crash

Related branches

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

I got the same crash here by following your steps to reproduce. Interesting note; I first launched one attack which failed without seeing any problems. Though on the second attack wave it crashed. It might have been triggered by winning the battle/conquering the enemy building.

I've attached a stacktrace.

Changed in widelands:
importance: Undecided → Critical
milestone: none → build19-rc1
status: New → Confirmed
Revision history for this message
Hans Joachim Desserud (hjd) wrote :
tags: added: boost crash
GunChleoc (gunchleoc)
Changed in widelands:
assignee: nobody → GunChleoc (gunchleoc)
status: Confirmed → In Progress
GunChleoc (gunchleoc)
Changed in widelands:
status: In Progress → Fix Committed
GunChleoc (gunchleoc)
Changed in widelands:
assignee: GunChleoc (gunchleoc) → nobody
GunChleoc (gunchleoc)
tags: removed: boost
GunChleoc (gunchleoc)
Changed in widelands:
status: Fix Committed → Fix Released
Revision history for this message
GunChleoc (gunchleoc) wrote :

Fixed in build19-rc1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.