2019-11-13 14:14 EST


View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002980FSSCPPilot datapublic2014-02-12 00:15
Reporterrodo 
Assigned ToEchelon9 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionunable to reproduce 
PlatformPhenom X4 965 BE, 8GBram + GTX OSWindows 7OS VersionService pack 1
Product Version3.7.1 
Target VersionFixed in Version 
Summary0002980: FSO crash after mission - possibly pilot code related
DescriptionFSO crashes when I play the mission 'Into the Maelstrom' from the FS2 campaign.

Crash happens right after mission is finished, and going into the debriefing.

It does not happen if I go to the techroom and play it from there (using the all missions cheat).

The error only happens with the user 'rodo', sadly I don't have another pilot as advanced as this one on the fs2 campaign to test it against.

IIRC, the user rodo is brand new, created with the 3.7.0 build.

Attaching fs2 log and the pilot files related to this error.
Steps To ReproduceJust play the next mission for the player rodo for the main fs2 campaign, it should crash at the end of the mission.
TagsNo tags attached.
Attached Files

-Relationships
related to 0002987resolvedGoober5000 AddressSanitizer: global-buffer-overflow in message_queue_process() 
+Relationships

-Notes

~0015547

Echelon9 (developer)

Last edited: 2013-12-30 05:01

View 2 revisions

Hi rodo,
I played through a few times using your pilot and was unable to reproduce the crash at the debriefing stage of the current mission. This was after loading it via the ready room, not the tech room as instructed.

I see you are using the mediavps 2014 beta, have you been able to recreate the crash using the mediavps 3.6.12?

~0015587

Goober5000 (administrator)

Rodo, please provide an update or we will be forced to close this bug.

~0015622

rodo (reporter)

Last edited: 2014-02-10 22:44

View 2 revisions

Sorry for the delay, this account is related to an old email address and I just saw the emails.

I'll check this tonight again and report back.

-EDIT:
Ok, I run it again and this time it didn't crash.
Not sure if it's something that changed on the new exe's, or maybe it was something related to the mvps (though I'm fairly sure I tested it both with 3612 and betas) but it's efectively gone now.
You may close, sorry for the inconvenience.

~0015623

niffiwan (developer)

closing per request
+Notes

-Issue History
Date Modified Username Field Change
2013-12-16 16:14 rodo New Issue
2013-12-16 16:14 rodo File Added: pilot+log.7z
2013-12-29 07:59 Echelon9 Relationship added related to 0002987
2013-12-30 05:01 Echelon9 Note Added: 0015547
2013-12-30 05:01 Echelon9 Assigned To => Echelon9
2013-12-30 05:01 Echelon9 Status new => feedback
2013-12-30 05:01 Echelon9 Note Edited: 0015547 View Revisions
2014-02-03 21:35 Goober5000 Note Added: 0015587
2014-02-10 16:44 rodo Note Added: 0015622
2014-02-10 16:44 rodo Status feedback => assigned
2014-02-10 22:44 rodo Note Edited: 0015622 View Revisions
2014-02-12 00:15 niffiwan Note Added: 0015623
2014-02-12 00:15 niffiwan Status assigned => closed
2014-02-12 00:15 niffiwan Resolution open => unable to reproduce
+Issue History