Load of saved skirmish fails with couldn't find a BASE_OBJ with ID #984
Comments
bill@... uploaded file Save that causes a crash on restore, and the resulting dump file. |
Buginator edited the issue description |
Buginator commented Please don't compress the crash dump file, it makes it much more difficult for us to see what the problem is. |
bill@... uploaded file uncompressed dump (as requested) |
Buginator commented Thanks. If you can recreate this, then please go into detail on how this happens. This is a long standing bug that we can't nail down, and pops up randomly. This isn't the same crash you had in #532. |
Buginator changed milestone from |
Buginator commented Milestone 2.2.5 deleted |
Buginator changed status from |
Buginator commented The milestone change was from the deletion of 2.2.5. If you know of a way we can replicate this issue on our newest build (2.3.x) then please let us know. I haven't seen this issue in a long time, and it may have been fixed. Thanks! |
trac-robot changed status from |
trac-robot commented This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 7 days. |
type_bug
| by bill@...Duplicate of #532, but I couldn't reopen it. I compiled the warzone-2.2.3 release on an ubuntu jaunty x86-64 bit machine (not overclocked, in a well cooled case). Oh the filesystem is nowhere near full, so it shouldn't have been a partial save.
I don't understand what was missing from the first bug report, I'm hoping I have whatever is missing. I have a previous save as well, it's possible I could recreate the corrupted save.
Oh, and the bugreport message should say "regarding" instead of "regardings".
Issue migrated from trac:984 at 2022-04-15 19:51:01 -0700
The text was updated successfully, but these errors were encountered: