Reproducible crash on OS X, support file linked.

[deleff]

Description

===========

 

Game will consistently crash upon entering a new area.

 

The transistion screen with tips will show, then the cursor

will switch to the Mac OS X "beachball" and then the game

will exit, dropping to the desktop and producing the OS X

Problem Reporter with the crash data.

 

The autosave will occur during the transition, and the game

load the save game in the new area upon restarting.

 

Steps to Reproduce

==================

 

Leave the current area and enter any new area.

 

Link to support data

====================

 

https://dl.dropboxusercontent.com/u/7529996/deleff-PoE_crash_data.zip

 

 

[bartlebooth]

I had this problem the other night, fixed by turning off Steam sync. Right click the game in Steam and select properties, then uncheck the sync option.

[deleff]

Thanks for the response, bartlebooth.  I unchecked the "Enable Steam Cloud synchronization for Pillars of Eternity" and am still experiencing the same behavior.

[celliott]

Hello, all.  I apologize for the inconvenience.  After looking at your files it appears as if the problem is stemming from the fact that you are playing on a MacBook Pro.  In the power options please disable automatic GPU switching and that should solve your problem.  If it does not please update this thread accordingly.  Thanks for your support and patience during this issue.

[deleff]

Hello, all.  I apologize for the inconvenience.  After looking at your files it appears as if the problem is stemming from the fact that you are playing on a MacBook Pro.  In the power options please disable automatic GPU switching and that should solve your problem.  If it does not please update this thread accordingly.  Thanks for your support and patience during this issue.

 

Thanks for the response, celliot.  I'm running OS X 10.10.4 if that factors into this.  On the OS, what was the power options I think are now known as "Energy Saver" settings.  Regardless, I see no option to modify GPU related activity under that section or the Display properties.  Also note that this MacBook Pro has the Intel Iris chipset, and does not have the capability of switching between the integrated and a dedicated GPU.

 

I looked in the game options as well, in case you meant an setting there.  I did not find this as a game setting, either.  (I did not expect to, but thought to check just to be certain.)

[deleff]

I will add that I have not always had this difficulty.  It's only recently that this crashing behavior began to manifest.

[celliott]

Hello, again.  Thank you for the additional information, I'm sorry that didn't work out.  Try verifying the integrity of the cache in Steam and update this thread again afterwards. That has also helped some players.  Also make sure that you have the most updated version.  I will keep digging for other options for you in the mean time.  Thanks again for your support and patience during this inconvenience.

[deleff]

I'm verified the integrity and am still experiencing the same issue.  I'm running 1.0.6.0617.  

 

The most relevant parts of the crash log to my eye are:

 

Crashed Thread:        4  UnityGfxDeviceWorker

 

Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

 

Application Specific Information:

abort() called

 

Application Specific Signatures:

Graphics hardware encountered an error and was reset: 0x00000003

 

And then the specifics of that thread:

 

Thread 4 Crashed:: UnityGfxDeviceWorker

0   libsystem_kernel.dylib         0x00007fff8d209286 __pthread_kill + 10

1   libsystem_c.dylib             0x00007fff95370b53 abort + 129

2   libmono.0.dylib               0x00000001016dc44a mono_handle_native_sigsegv + 732

3   libmono.0.dylib               0x0000000101723e3b sigabrt_signal_handler + 100

4   libsystem_platform.dylib       0x00007fff953f1f1a _sigtramp + 26

5   libsystem_kernel.dylib         0x00007fff8d209286 __pthread_kill + 10

6   libsystem_c.dylib             0x00007fff95370b53 abort + 129

7   libGPUSupportMercury.dylib     0x00007fff9298eb81 gpusGenerateCrashLog + 173

8   com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340044249f gpusKillClient + 9

9   libGPUSupportMercury.dylib     0x00007fff92990068 gpusSubmitDataBuffers + 500

10  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400003c98 IntelCommandBuffer::getNew(GLDContextRec*) + 48

11  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340010939d intelSubmitCommands + 191

12  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340005dd23 Gen7Context::CheckOOM(USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, unsigned long long, bool&) + 1665

13  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400105973 Gen7Context::CheckOOM(unsigned long long, bool&) + 103

14  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400100843 Gen7Context::ProgramPipeline() + 91

15  com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340044dbe8 glrIntelRenderVertexArray + 328

16  GLEngine                       0x00007fff8df17f46 glDrawElements_ACC_Exec + 526

17  unity.Obsidian Entertainment.Pillars of Eternity 0x000000010072eb14 ARBVBO::DrawInternal(ChannelAssigns const&, void const*, unsigned int, GfxPrimitiveType, unsigned int) + 436

18  unity.Obsidian Entertainment.Pillars of Eternity 0x000000010074e4e5 GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&) + 12421

19  unity.Obsidian Entertainment.Pillars of Eternity 0x000000010074b33c GfxDeviceWorker::RunGfxDeviceWorker(void*) + 76

20  unity.Obsidian Entertainment.Pillars of Eternity 0x000000010047620a Thread::RunThreadWrapper(void*) + 58

21  libsystem_pthread.dylib       0x00007fff94df4268 _pthread_body + 131

22  libsystem_pthread.dylib       0x00007fff94df41e5 _pthread_start + 176

23  libsystem_pthread.dylib       0x00007fff94df241d thread_start + 13 

[celliott]

Hello again.  Thank you for the update.  I have added your additional information to our internal database so the programming team can get to the bottom of this.  Thank you for your patience and support during this issue.

[deleff]

Hello again.  Thank you for the update.  I have added your additional information to our internal database so the programming team can get to the bottom of this.  Thank you for your patience and support during this issue.

 

I'm curious if any news, cuase, or suggestions to address this problem are as yet identified.  Thanks.

[celliott]

Hello again.  Unfortunately I have no new news.  The bug is assigned to one of our senior programmers and is being looked at.  That's as far as my information goes.  There haven't been any updates or workarounds that I have discovered since entering your additional information.  I apologize!  Thanks for your support.

[mikemariano]

I have been playing Pillars of Eternity for months like this on my 2013 MacBook Pro.  I walk to a new area, the program crashes, I restart it and continue from the autosave into the next area.  Sometimes I got lucky and PoE stayed open from one area to the next—if I made it through one transition without crashing the following transitions in the same session would usually work—but most playing sessions consisted upon crash after crash. 

 

None of the suggested workarounds made any difference: typing msaa 0 into the console, trying to search for a GPU option on the system that doesn't exist, syncing and unsyncing Steam saves.

 

But I kept playing.  Until tonight.  I am at what I assume is close to the end of the game and I am expected to jump from one area into another with a text transition in between.  But the game does not autosave in the new area; it saves right where I was.

 

So I jump into the pit, the game crashes, I jump again, it crashes again, and unlike all my previous crashes I don't get into the next area.

 

I'm sad; this seems to be the end of Pillars of Eternity for me!

[Quantics]

I have been playing Pillars of Eternity for months like this on my 2013 MacBook Pro.  I walk to a new area, the program crashes, I restart it and continue from the autosave into the next area.  Sometimes I got lucky and PoE stayed open from one area to the next—if I made it through one transition without crashing the following transitions in the same session would usually work—but most playing sessions consisted upon crash after crash. 

 

None of the suggested workarounds made any difference: typing msaa 0 into the console, trying to search for a GPU option on the system that doesn't exist, syncing and unsyncing Steam saves.

 

But I kept playing.  Until tonight.  I am at what I assume is close to the end of the game and I am expected to jump from one area into another with a text transition in between.  But the game does not autosave in the new area; it saves right where I was.

 

So I jump into the pit, the game crashes, I jump again, it crashes again, and unlike all my previous crashes I don't get into the next area.

 

I'm sad; this seems to be the end of Pillars of Eternity for me!

 

 

 

First I want to say that I've been playing PoE on my 2014 MBP since release without any problems. So I don't know if those options will fix anything...

 

1) The GPU option is found in Preferences > Energy > (Disable) Automatic Graphics switching 

 

2) Try that nice little app called gfxCardStatus (free)

 

https://gfx.io

 

You will be able to choose which of the integrated graphics card or dedicated GPU to use (note that you will have to click to use twice for some reason). This will ensure OS X is not switching GPUs while you're playing.

 

It's worked for me in other games.

Edited August 12, 2015 by Quantics

[mikemariano]

 

2) Try that nice little app called gfxCardStatus (free)

https://gfx.io

 

You will be able to choose which of the integrated graphics card or dedicated GPU to use (note that you will have to click to use twice for some reason). This will ensure OS X is not switching GPUs while you're playing.

 

It's worked for me in other games.

 

 

Thanks, Quantics!  I'll check it out.

 

But before I downloaded it, while checking some of the PoE graphical options I decided to give the pit one more shot.  I jumped in and the game successfully transfered to the new area.  I powered through and completed the game.  I'm glad I got to see the end!

[deleff]

Hello again.  Unfortunately I have no new news.  The bug is assigned to one of our senior programmers and is being looked at.  That's as far as my information goes.  There haven't been any updates or workarounds that I have discovered since entering your additional information.  I apologize!  Thanks for your support.

 

Hi, original poster here.   Is there any update on this from the programmers?  I'm still getting the same behavior, after the update to PoE version 2.

[celliott]

Hello, deleff.  Can you please upload new files?  This will help me dig in to the problem better as a lot of stuff has changed in the game.  You might also try uninstalling and completely reinstalling the game to clear out any bad data that might have happened.  Verifying the game files might work as well.  Please update this thread after you have done these things and we'll go from there.  Thank you for the support!