Page 2 of 2
Re: 1.77 crash
Posted: Fri Jan 25, 2013 12:29 pm
by Eric Walch
Mad Dan Eccles wrote: I've had one random crash in the middle of a furball, ....
I'll upload a log if it happens again.
The crash-log might still be stored on your system. Go to spotlight and search for "Console", than open the program.
Than, on the left, unfold the category '~/library/logs' . Than look in 'Crashreporter'. All crash logs are stored here by program.
You might need to show the index bar by clicking the icon on the top left of the console window.
(And the stations spinning to fast is not Mac specific as it is also reported on windows systems)
Re: 1.77 crash
Posted: Fri Jan 25, 2013 12:52 pm
by Mad Dan Eccles
Thanks Eric, I'll have a look tonight.
Re: 1.77 crash
Posted: Fri Jan 25, 2013 1:18 pm
by aegidian
Look if the latest Mac version on the download page does not work with the latest version of OSX (especially if it crashes at startup) then there should be at least a warning there to download 1.76.1 instead.
Unfortunately, 1.77 is being widely promoted as the latest version, not the latest 'stable' version.
Please don't deploy something that doesn't work. Especially not on my machine. It makes me peevish!
Re: 1.77 crash
Posted: Fri Jan 25, 2013 1:47 pm
by Mad Dan Eccles
Oh, come on: you *know* even-numbered OS X versions are a bit shonky
Re: 1.77 crash
Posted: Fri Jan 25, 2013 7:15 pm
by Mad Dan Eccles
@Eric, my crash log is
here.
Re: 1.77 crash
Posted: Fri Jan 25, 2013 8:30 pm
by Eric Walch
Mad Dan Eccles wrote:I've had one random crash in the middle of a furball, .... @Eric, my crash log is
here.
Thanks, but in that log in no good clue for the crash area. The last entry was from the player entering witchspace. (got cold feet?
)
Re: 1.77 crash
Posted: Fri Jan 25, 2013 8:35 pm
by Mad Dan Eccles
Bollocks. I'm trying to remember exactly when the crash happened, but failing. It might have been as I went into witchspace, and as I usually do my anti-piracy *after* that, it might explain why I wasn't too upset.
If it happens again I'll be a good little tester and make an immediate note.
Re: 1.77 crash
Posted: Sat Jan 26, 2013 10:16 am
by Disembodied
aegidian wrote:Look if the latest Mac version on the download page does not work with the latest version of OSX (especially if it crashes at startup) then there should be at least a warning there to download 1.76.1 instead.
Just to complicate matters, I can report that 1.77 runs beautifully and with no problems for me under 10.8.2 ...
Re: 1.77 crash
Posted: Sat Jan 26, 2013 10:43 am
by Eric Walch
pescenaufrago wrote:I installed the "Latest edition" from this
page.
Please download
this nightly build version. That version does log a bit more internal errors than the release version, and might log something useful into the 'latest log'.
As fas as I see from the crash log, it happens during the pre-loading of sounds and the last changes there were made 4 months ago. Just a pity that none of the trunk users experienced any problem in that time.
Re: 1.77 crash - SOLVED with nightly vs
Posted: Sun Jan 27, 2013 8:16 pm
by pescenaufrago
It works!
I installed oolite-trunk-1.77.1.5626-dev.
Re: 1.77 crash - SOLVED with nightly vs
Posted: Sun Jan 27, 2013 9:55 pm
by aegidian
pescenaufrago wrote:It works!
I installed oolite-trunk-1.77.1.5626-dev.
Yep, that works for me too.
Thanks devs.
Thevs.
Re: 1.77 crash - solved with nightly version
Posted: Sun Mar 24, 2013 3:29 pm
by JensAyton
Since this seems to have been wallpapered over rather than fixed, I’ve posted a testing build
here. This is 1.77 in deployment mode with extra logging of sound preloading, and the hack that puts the last log message in the crash report enabled. It’s also build with a newer compiler, so it might magically “just work”, who knows? In any case, testing by those afflicted would be welcome.
Re: 1.77 crash - solved with nightly version
Posted: Wed Mar 27, 2013 6:01 pm
by pescenaufrago
Hello. I downloaded the build posted by jensAyton and copied on the oldest build. So, with all my oxps.
Except for debug.oxp (not compatible), now everything seems to work! (or crash reports are disabled... anyway...).
Thank You!