Comment 3 for bug 1638394

Revision history for this message
SirVer (sirver) wrote : Re: [Bug 1638394] Re: Crash on rendering roads

Very likely this was introduced with the zoom branch. Of course not sure.

> Am 01.11.2016 um 22:37 schrieb GunChleoc <email address hidden>:
>
> Fix LGTM. Candidate for Build 19?
>
> ** Changed in: widelands
> Milestone: None => build19-rc2
>
> ** Tags added: crash
>
> --
> You received this bug notification because you are subscribed to
> widelands.
> https://bugs.launchpad.net/bugs/1638394
>
> Title:
> Crash on rendering roads
>
> Status in widelands:
> New
>
> Bug description:
> I am not completely sure what causes it, but my theory is:
> - Discover/See an area but do not conquer it.
> - Lose sight of the area.
> - Let the AI conquer and build on the land without observing it. Building is important here, we need some roads.
> - At some later time, rediscover the ares. Roads leading into the non-visible areas crash the game. (Most likely these roads must lead into darkness above or left of the visible area).
>
> Happened in r8163. The problem seems to be that the road is told to be
> rendered by a neighboring tile but the start of the road is not
> visible yet. Since it is not visible, the player(!=game) does not know
> the owner of the land, leading to a failed assert(owner!=null).
>
> A backtrace and a branch with a fix are attached. I can also offer
> savegames if required.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/widelands/+bug/1638394/+subscriptions