News:

Simutrans Wiki Manual
The official on-line manual for Simutrans. Read and contribute.

[develnew 5820b12] Fatal Error: Vector_tpl<T>......

Started by Ves, December 03, 2015, 10:32:20 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Ves

FATAL ERROR: Vector_tpl<T>::[] - class convoi_t::route_info_t: index out of bounds: 36 not in 0..27

When opening my savegame (lastly saved with 5820b12) and fastforward a few minutes, the screen freezes and the above sentence appear. The savegame where originally created from a resent develnew Experiemental version.

Savegame: https://www.dropbox.com/s/hmbwvws5m5iy11a/Crash%20bug%20test%205820b12.sve?dl=0

Rollmaterial

Good to know I'm not the only one to report out of bounds crashes here :D

Ves

oh, crap! Didnt realize that you already reported about that and it had reappeared (read the thread you and Izaac wrote in, just not realizing its the same issue :P ) apologies for that!
James, this probably is the same as http://forum.simutrans.com/index.php?topic=14971.0

Rollmaterial

It's the same problem, but it's not necessarily the same bug, as out of bounds bugs seem to be quite frequent :)

jamespetts

Can you re-test after the latest fixes to see whether this still recurs? I should be most grateful.

Ves

At a quick glance, it appears to be fixed!

edit: no, I got the same error again after some time, but the text is different:

FATAL ERROR: Vector_tpl<T>::[] - class koord3d:  index out of bounds: 147 not in 0..42

jamespetts

I am having trouble reproducing this - can you let me know at what game time that this occurs for you?

Ves

I had been playing for a while since the save game in first post. However, I'm not home this weekend, but will try to reproduce it next week

jamespetts


Ves

With the current release (develnew 83ea140) and the provided save, this occurs at ingame time: 1874, August 3:00:06

https://www.dropbox.com/s/apmvj4gj6obq1kk/Crash%20bug%20test%2083ea140.sve?dl=0

jamespetts

Thank you for the report. I believe that I have fixed this - would you care to re-test?

Ves