This seems to happen repeatedly, and seems to be time-based.







I've attached crash reports, they all seem to be EXC_CORPSE_NOTIFY crashes, but the stack is always different. I'm confident that my laptop was awake and running the entire time the game was open, and never went to sleep.



Happy to provide any additional diagnostic info. Super bummed, as a couple hours in is just when the game starts to get interesting, and getting kicked out to the desktop without warning is a pretty shocking way to end a turn.

I'm having the exact same issue. I played for an hour and now when I go to launch; it seems like its blowing up the resolution and then quiting.



https://www.dropbox.com/sh/gefzi211cwwefrg/AAB4N118cT7clxJrWTcx1Gx8a?dl=0



I've followed the instructions listed here /#/endless-legend/forum/23-mac-os/thread/6660-mac-os-troubleshooting but I still experience the problem.



please help

We'll also need your diagnostics file, littleodie914. I've passed on the elements given by lpaulger to our dev team.



In the meantime, I suggest (since Endless Legend on OSX is a 32bits version) restarting the game every couple of hours should alleviate a lot of these issues, since your game probably hits its memory ceiling and tries going through the roof... resulting in these crashes.

So the issue I was experiencing was that the game can't start on mac in full screen without crashing. I figured out that If I make sure to click "Cmd+F" as the game starts I can put it back in windowed mode while it starts to make sure it doesn't crash. Then after that I can set it back to full screen and it works great.

Frogsquadron wrote:
We'll also need your diagnostics file, littleodie914. I've passed on the elements given by lpaulger to our dev team.



In the meantime, I suggest (since Endless Legend on OSX is a 32bits version) restarting the game every couple of hours should alleviate a lot of these issues, since your game probably hits its memory ceiling and tries going through the roof... resulting in these crashes.

To clarify, I'm not having any of the issues lpaulger is. I can start the game just fine in windowed or fullscreen mode, and have no crashes/issues aside from the exit-to-desktop around the 3 hour mark.



Thanks Frogsquadron, I've attached two diagnostic files (.HTML) that seem to correlate time-wise to two of the crash reports, though there are no errors mentioned, only (what seem to be) inconsequential warnings. The earlier diagnostic files seem to have been removed/rolled to the trash. I also attached the Player.log from the Library/Logs/Unity directory, but it's hard to tell if any of the contents pertains to a crashed session, as I've played a few games since the last crash.



I hope the "restart every couple hours" is only a temporary workaround - in the middle of a game it's jarring to think, "Okay, now I should probably save, quit, relaunch, load, and pick up where I left off."



Do you guys have any Macs in the lab? In my experience, it really is as reproducible as starting a game and letting it sit for 3 hours.
Endless Legend Diagnostics.zip

Having same issue. Also, game runs very slowly. Starting a new game, the loading process takes several minutes. Much longer than it used to.



Here's the info:



Mac OS v. 10.11.1

Macbook Pro - 64 bit - CPU 2.2 GHz Intel Core i7

Player Log: attached

Diag log: attached
Diagnostics #2014'11'15 @1851'29''.html.zip
Player.log.zip

I think I'm having this problem, as well; or at least one that's similar: crashed, and lost all of my progress, a couple hours into a game. Pretty upset, as it was going well, too.
crash-nov-23.zip

Just ran into this bug again (w/ the Forges of Creation update).



In this instance, I had left the game running for ~6 hours while I walked away from it. Coming back, the game was still up, but when I pressed a single key (to scroll the map) the crash occurred immediately.

Littleodie914: that'll definitely happen if you let the game sit for a while I think, it'll just eat through its alloted memory, run out, crash. I'll forward these on to the dev team, however I'm not sure what can be done considering the hardware usage seems to be the limitation there.

Frogsquadron wrote:
Littleodie914: that'll definitely happen if you let the game sit for a while I think, it'll just eat through its alloted memory, run out, crash. I'll forward these on to the dev team, however I'm not sure what can be done considering the hardware usage seems to be the limitation there.

Thanks for passing the crash and diagnostics along to the dev team.



However, I have to say that's not how memory management works. Applications don't just eat through memory unless they're either leaking it, or unnecessarily allocating more than they need to be. The only kind of application that crashes after it "uses up" its allocated memory, without any user activity, is an unstable/buggy one.



Being a 32-bit application lowers the memory ceiling, but it just means that the application needs to work within that space.

Hi,

same for me,

CTDs after 2-3 hours



iMac27(last) with 8GbRAM

Frogsquadron wrote:
Littleodie914: that'll definitely happen if you let the game sit for a while I think, it'll just eat through its alloted memory, run out, crash. I'll forward these on to the dev team, however I'm not sure what can be done considering the hardware usage seems to be the limitation there.

Not sure, but this sounds like a memory leak of some sort. It shouldn.t eat more memory than it will release eventually ...

any news on if they've fixed the issue? I've been having this issue for some time now

Which issue are you referring to specifically, doombot890?



There are several issues at hand in this thread:

- Memory usage due to Mac only having a 32-bits client

- Crash to desktop on fullscreen

- Issues with Retina models



The 2nd could have been alleviated with the last version of Unity, the first one is unlikely to change unless we get a 64-bits version (which is something we're considering the feasibility of), the last one we're having issues reproducing in-house.

OK. I have a maxed out mid 2015 Macbook Pro (2.8GHz i7, 16GB RAM), running the game on Steam.



I had the same problem as others. (Won't start after 2 hours of play). I was running the game in full screen mode.



Tried the previous fixes to no avail, tried uninstalling and reinstalling 3 times. No good.



Since I figured the problem had to do with screen size (had similar problems with other games before), I plugged my MBP to my external 27" Apple display and it WORKED.



However, I don't want to be strapped to the monitor when I play, so I tried to turn off fullscreen, but everytime I did that, the mouse UI will not click to the appropriate "OK" box to validate the change. So after several attempts, I cmd-F, the mouse still won't point properly but I was a small margin of error to eventually get to the "OK" box to confirm the change. And now I'm running the game in Windowed mode ONLY.



At least it runs now.



For the dev's, you cannot reproduce it because I have a feeling you're not running the game in a Macbook Pro. You're probably running it on an iMac or Mac Pro?



Game still periodically crash every hour or two, but at least the autosave works so I usually only lose a little bit of a turn.

Frogsquadron wrote:
Which issue are you referring to specifically, doombot890?



There are several issues at hand in this thread:

- Memory usage due to Mac only having a 32-bits client

- Crash to desktop on fullscreen

- Issues with Retina models



The 2nd could have been alleviated with the last version of Unity, the first one is unlikely to change unless we get a 64-bits version (which is something we're considering the feasibility of), the last one we're having issues reproducing in-house.