Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Load of saved skirmish fails with couldn't find a BASE_OBJ with ID #984

Closed
wzdev-ci opened this issue Oct 7, 2009 · 11 comments
Closed

Load of saved skirmish fails with couldn't find a BASE_OBJ with ID #984

wzdev-ci opened this issue Oct 7, 2009 · 11 comments

Comments

@wzdev-ci
Copy link
Contributor

wzdev-ci commented Oct 7, 2009

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 was playing a skirmish against 3 computer players, killed off one (or almost completely), and saved.  On restore I get:
~/.warzone2100-2.2/savegame$ /opt/pkg/warzone210-2.2.3/bin/warzone2100 
ALSA lib pcm.c:2205:(snd_pcm_open_noupdate) Unknown PCM alsa
ALSA lib pcm.c:2205:(snd_pcm_open_noupdate) Unknown PCM alsa
AL lib: alsa.c:344: Could not open playback device 'alsa': No such file or directory
error   |09:46:44: [buildFeature] Artifact(174944) already placed at (23+1, 69+1) when trying to place Artifact(160640) at (23+1, 69+1) - removing it
error   |09:46:44: [getBaseObjFromId] getBaseObjFromId() failed for id 174944
error   |09:46:44: [getBaseObjFromId] Assert in Warzone: objmem.c:867 (!"couldn't find a BASE_OBJ with ID"), last script event: '<none>'
Saved dump file to '/tmp/warzone2100.gdmp-3iMg9p'
If you create a bugreport regardings this crash, please include this file.
Segmentation fault

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

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Oct 7, 2009

bill@... uploaded file warzone-bugreport.tgz (273.9 KiB)

Save that causes a crash on restore, and the resulting dump file.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Oct 9, 2009

Buginator edited the issue description

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Oct 9, 2009

Buginator commented


Please don't compress the crash dump file, it makes it much more difficult for us to see what the problem is.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Oct 9, 2009

bill@... uploaded file warzone2100.gdmp-RwM8Nt (16.5 KiB)

uncompressed dump (as requested)

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Oct 9, 2009

Buginator commented


Thanks.
A corrupted Proximity message.

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.

@wzdev-ci
Copy link
Contributor Author

Buginator changed milestone from 2.2.5 to 2.3

@wzdev-ci
Copy link
Contributor Author

Buginator commented


Milestone 2.2.5 deleted

@wzdev-ci
Copy link
Contributor Author

Buginator changed status from new to pending

@wzdev-ci
Copy link
Contributor Author

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!

@wzdev-ci
Copy link
Contributor Author

trac-robot changed status from pending to closed

@wzdev-ci
Copy link
Contributor Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant