Opened 4 years ago

Last modified 4 years ago

#5672 new defect

0AD quits unexpectedly and *silently*

Reported by: BigBadaboom Owned by:
Priority: Should Have Milestone: Backlog
Component: Core engine Keywords: silent crash
Cc: Patch:

Description

Linux (Most recent Xubuntu)

Game performs as usual and suddenly simply vanishes. No message. No other software running. No abnormal behavior whatsoever.

This happens now and then, perhaps once every other week on average, sometimes several times in a row. I have not noticed any specific trigger or condition, am unable to reproduce.

The game that was in progess is, of course, lost. Subsequent exection as usual.

I don't know where to look for logs or traces.

Attachments (5)

crashlog.txt (68.0 KB ) - added by BigBadaboom 4 years ago.
mainlog.html (25.1 KB ) - added by BigBadaboom 4 years ago.
system_info.txt (8.6 KB ) - added by BigBadaboom 4 years ago.
userreport_hwdetect.txt (16.8 KB ) - added by BigBadaboom 4 years ago.
commands.txt (224.2 KB ) - added by BigBadaboom 4 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 by elexis, 4 years ago

There are crashdumps and logfiles in a directory, see wiki:GameDataPaths

Perhaps its an out of memory issue (too large map?) or a problem with a driver or old hardware / platform.

If there are no useful logfiles from the time of the crash: On Xubuntu, one can run the program in gdb gdb ./binaries/system/pyrogenesns, run. Then if it crashes one can type info stack to obtain a stacktrace. That would reveal more about the origin of the error.

by BigBadaboom, 4 years ago

Attachment: crashlog.txt added

by BigBadaboom, 4 years ago

Attachment: mainlog.html added

by BigBadaboom, 4 years ago

Attachment: system_info.txt added

by BigBadaboom, 4 years ago

Attachment: userreport_hwdetect.txt added

by BigBadaboom, 4 years ago

Attachment: commands.txt added

comment:2 by BigBadaboom, 4 years ago

Found, and attached, the log files and the replay file.

(interestinglog.html is empty)

comment:3 by elexis, 4 years ago

Do you know if the crashlog.txt is from a day the game crashed the way you reported it?

Either way, the crashlog.txt refers to an issue with OggVorbis codec, which might relate to some soundcard or sounddriver issue. Perhaps it could be triggered by changing the selected sound output, or the soundsystem somehow becoming busy otherwise?

Function call failed: return value was -100030 (Try again later) Location: ogg.cpp:289 (GetNextChunk)

which is

const Status AGAIN = -100030;

That comes from > source/soundmanager/data/ogg.cpp

static Status LibErrorFromVorbis(int err)
{
	switch(err)
	{
	case 0:
		return INFO::OK;
	case OV_HOLE:
		return ERR::AGAIN;

OV_HOLE

https://xiph.org/vorbis/doc/libvorbis/return.html

Vorbisfile encoutered missing or corrupt data in the bitstream. Recovery is normally automatic and this return code is for informational purposes only.

Perhaps it means that one of the ogg soundfiles is corrupt, perhaps the public.zip is broken, in that case a reinstallation might help. Or perhaps you use a mod that has a broken sound file?

One could also delete the cache or mods folder contents (see that wiki:GameDataPaths) in case there were any broken ogg leftovers.

And it sounds like this warning should be ignored instead of triggering a debug_breakpoint.

0AD quits unexpectedly and *silently*

In case the reported reoccurring crash is due to the vorbis error, the ticket title is even more accurate I guess.

Last edited 4 years ago by elexis (previous) (diff)
Note: See TracTickets for help on using tickets.