Crash on saving game: unprotected error in call to Lua API (table index is NaN)

Bug #1254116 reported by famolp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
widelands
Fix Released
High
Unassigned

Bug Description

Hello, I'm playing the barbarian campaign, part 3 and now I'm at the point of attacking the red ones.

I can still do so, after this comes the introduction for the next challenge, with some flickering and some strange offset (view is centered in nowhere). However when I try to save after this part, the game crashes... :-(

Thanks!

see:
https://wl.widelands.org/forum/topic/1387/

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

Thanks for taking your time to report this issue.

I was able to reproduce it by loading the first save game, attack the red players, click through the story dialogs and then attempt to save the game. During the attempted save I saw the following output in the terminal:
 Writing Node Ownership Data ... took 12ms
 Writing Exploration Data ... took 17ms
 Writing Players Unseen Data ... took 93ms
 Writing Scripting Data ... PANIC: unprotected error in call to Lua API (table index is NaN)
[Thread 0x7fffe8c48700 (LWP 12240) exited]
[Inferior 1 (process 12235) exited with code 01]
(gdb) bt
No stack.

Changed in widelands:
importance: Undecided → High
status: New → Confirmed
tags: added: lua savegame
summary: - Crash on savegame
+ Crash on saving game: unprotected error in call to Lua API (table index
+ is NaN)
Revision history for this message
SirVer (sirver) wrote :

Setting to incomplete for bug sweeping.

Changed in widelands:
status: Confirmed → Incomplete
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

In the development release we have replaced the way save games are written to/read from disk. This makes it rather hard to load the first game to test whether attempting to save still leads to this problem.

SirVer: what do you think about this? I don't know how whether we can use the original save game to figure out which part of the state caused this problem or whether we should simply close this and see whether it gets re-reported in the future (with games persisted with eris). I'm not sure though, since I seem to remember we have had a couple of bugs like this, so it would be nice to verify if the problem is gone.

Revision history for this message
SirVer (sirver) wrote :

There is no way to verify if the bug is indeed gone in the dev version as saving as changed a lot. There is also no way to load old savegames in any way anymore.

If we have a bug reported against an old revision and need to check the savegame, we also need to go back to the revision (which is not a big deal imho). We can then still investigate the issues. But since this is related to saving I'd call this fixed until it resurfaces (unlikely).

Changed in widelands:
status: Incomplete → Fix Committed
milestone: none → build19-rc1
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

Remote bug watches

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