Crash with savegame to reproduce

Bug #1817477 reported by xzu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Confirmed
Undecided
Benedikt Straub

Bug Description

100% producible bug with build-18 under ubuntu 16.04.

Recipe:

1- load attached save game
2- do nothing, just wait about 10s
3- and then then game freez and crash.

I've also send bug report by apport (automatic bug report for ubuntu package).

I have other saved game, if that can help. Some before this one that make the crash, and some other that don't.

Revision history for this message
xzu (xzurukneg) wrote :
xzu (xzurukneg)
information type: Private Security → Public
Revision history for this message
kaputtnik (franku) wrote :

Sorry xzu, this bug report was overlooked.

Build 18 is quite old, currently build 19 is the official release of widelands. I guess no one will look into this issue, since the code basis has changed a lot since build 18 and the underlying bug may has already been fixed.

Changed in widelands:
status: New → Invalid
Revision history for this message
xzu (xzurukneg) wrote :

The Crash occurs exactly the same with build 19. Please test it.

Changed in widelands:
status: Invalid → New
Revision history for this message
kaputtnik (franku) wrote :

I do not have build 19 anymore, sorry, it does not compile on my system.

The current development build, which i use, is incompatible with your savegame :-(

In some weeks a new official release will be released.

You may has to wait until someone using build 19 test your savegame.

Revision history for this message
Benedikt Straub (nordfriese) wrote :

Can reproduce. Will look into it…

Changed in widelands:
assignee: nobody → Benedikt Straub (nordfriese)
status: New → Confirmed
Revision history for this message
Benedikt Straub (nordfriese) wrote :

gdb output:

Thread 1 "widelands" received signal SIGSEGV, Segmentation fault.
0x0000555555a747d3 in Widelands::Economy::find_best_supply(Widelands::Game&, Widelands::Request const&, int&) ()
(gdb) bt
#0 0x0000555555a747d3 in Widelands::Economy::find_best_supply(Widelands::Game&, Widelands::Request const&, int&) ()
#1 0x0000555555a75697 in Widelands::Economy::process_requests(Widelands::Game&, Widelands::RSPairStruct&) ()
#2 0x0000555555a758ba in Widelands::Economy::balance_requestsupply(Widelands::Game&) ()
#3 0x0000555555a792a9 in Widelands::Economy::balance(unsigned int) ()
#4 0x00005555558cbf11 in Widelands::CmdQueue::run_queue(int, unsigned int&) ()
#5 0x000055555580f6cf in Widelands::Game::think() ()
#6 0x000055555598f9a8 in InteractiveBase::think() ()
#7 0x000055555599920a in InteractivePlayer::think() ()
#8 0x0000555555932025 in UI::Panel::do_run() ()
#9 0x000055555581342b in Widelands::Game::run(UI::ProgressWindow*, Widelands::Game::StartGameType, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#10 0x0000555555814253 in Widelands::Game::run_load_game(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#11 0x00005555557741ee in WLApplication::mainmenu_singleplayer() ()
#12 0x00005555557746d0 in WLApplication::mainmenu() ()
#13 0x0000555555774e57 in WLApplication::run() ()
#14 0x000055555575da83 in main ()

tags: added: crash economy
Revision history for this message
Benedikt Straub (nordfriese) wrote :

The problem is that a ware (snack) that is stored in the port at 83/16 believes it is not in a building but still being carried by a worker, and this worker doesn´t know where he currently is. I´ll now try to find out how that could have gotten messed up…

Revision history for this message
Benedikt Straub (nordfriese) wrote :

This is already fixed in trunk, see bug 1639444. The ware is being carried while it´s on a ship, causing a segfault.

You can continue playing without the crash if you destroy all ships close to the said port before the snack (it´s near the barrier just southwest of the port when the savegame starts) arrives in the port.

tags: added: seafaring
Revision history for this message
kaputtnik (franku) wrote :

Thanks Benedikt :-)

Revision history for this message
xzu (xzurukneg) wrote :

Fixed, ok good news. Thanks!

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

Other bug subscribers

Remote bug watches

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