1. Simulation Curriculum Corp.
  2. Community
  3. Starry Night 8 | User Support
New post
0

[OpenGL]* Why Does Catalina Security Update (19H1519) Crash Starry Night 8? (Answer: Apple Security Update 2021-2008 Catalina Fixes The Issue!)

Hi, SN Pro Plus 8 now crashes on startup after Apple Security Update 2021-007 10.15.7 (Catalina) is applied on my Macbook Pro. As an aside so does Stellarium. Both applications ran fine until the update. Now both give similar crash dumps indicating a graphics problem. I have a MBP early 2013 with 3Ghz i7, 8 Gb RAM and Intel 4000 graphics. I have included part of the crash dump.

Process: Starry Night Pro Plus [696]
Path: /Applications/Starry Night Pro Plus 8.app/Contents/MacOS/Starry Night Pro Plus
Identifier: com.simulationcurriculum.starrynight.proplus.8.osx
Version: 8.1.1 (2078)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Starry Night Pro Plus [696]
User ID: 501

Date/Time: 2021-11-07 23:51:12.130 +0000
OS Version: Mac OS X 10.15.7 (19H1519)
Report Version: 12
Anonymous UUID: 7BB8B297-9CF1-40EF-88B6-BE524EDAE79E

Time Awake Since Boot: 930 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Application Specific Signatures:
Graphics kernel error: 0xfffffffb

Cheers
Richard

Date Votes

26 comments

  • Avatar
    Keiron Smith Official comment

    DevOps reference: https://starrynight.unfuddle.com/a#/projects/7957/tickets/by_number/10392

  • 0
    Avatar
    Keiron Smith

    Richard, 

    Please delete and reinstall SN8.

    Catalina has been out for a long time.  This issue is limited to something specific to your computer.

    I have SN8 running on 2013 Macbook Pro + Catalina 10.15.7 and all is good.

    Thanks!

  • 0
    Avatar
    Richard Holland

    Hi Keiron

    Also see issue: https://support.simulationcurriculum.com/hc/en-us/community/posts/4411984533143-SN8-will-not-launch-on-Mac

    Also the phrase 'something specific to my computer' - well its a MBP (early 2013) is there something specific with it then or have I got a special one? I thought all Macs had the same hardware spec (maybe just slight differences in CPU spec and RAM size).

    I had SN8 running on my MBP + Catalina 10.17.7 like you and everything was honky dory but have you installed 2021-007 10.15.7 security update (19H1519)? I would be interested if you have.

    Best regards

    Richard

     

     

     

  • 0
    Avatar
    Richard Holland

    I meant 10.15.7 not 10.17.7

     

  • 0
    Avatar
    Keiron Smith

    Apologies, I'll update my Macbook Pro shortly and get back to you.

  • 0
    Avatar
    Richard Holland

    Thanks Keiron

    I thought I was going mad when you said it worked for your 2013 MBP!

    Interesting it happens with Stellarium as well (not that that helps)

    Richard

  • 0
    Avatar
    Keiron Smith

    Still works for me after the update!

  • 0
    Avatar
    Richard Holland

    Hi Keiron

    I think I know why yours is working from the info on your screenshot.  Unlike me you have a 15" (mine is the 13") dual graphics model. I think the problem stems from mine only having the Intel HD 4000 chip. As my crash dump suggests a graphics driver incompatibility, is there a way you can disable the NVidia GT650M  from being used (probably not) and see if it still works?  You also have 16Gb RAM  compared to my 8 but I would not think that is a problem.

    Best regards

    Richard

  • 0
    Avatar
    Keiron Smith

    Richard,

    Here is my crash dump.

    Process:               Starry Night Pro Plus [6579]
    Path:                  /Applications/Starry Night Pro Plus 8.app/Contents/MacOS/Starry Night Pro Plus
    Identifier:            com.simulationcurriculum.starrynight.proplus.8.osx
    Version:               8.1.1 (2078)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Starry Night Pro Plus [6579]
    User ID:               501
     
    Date/Time:             2021-11-09 12:32:29.808 -0500
    OS Version:            Mac OS X 10.15.7 (19H1519)
    Report Version:        12
    Anonymous UUID:        7D1307F4-0CBD-31B2-9B4E-D43463912CA4
     
    Sleep/Wake UUID:       7D483115-E4DC-4C21-8D12-8F453EAE6DF4
     
    Time Awake Since Boot: 44000 seconds
    Time Since Wake:       4600 seconds
     
    System Integrity Protection: enabled
     
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
     
    Exception Type:        EXC_CRASH (SIGABRT)
    Exception Codes:       0x0000000000000000, 0x0000000000000000
    Exception Note:        EXC_CORPSE_NOTIFY
     
    Application Specific Information:
    abort() called
     
    Application Specific Signatures:
    Graphics kernel error: 0xfffffffb
     
     
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x00007fff67f3a33a __pthread_kill + 10
    1   libsystem_pthread.dylib       0x00007fff67ffae60 pthread_kill + 430
    2   libsystem_c.dylib             0x00007fff67ec1808 abort + 120
    3   libGPUSupportMercury.dylib     0x00007fff4f12c0a5 gpusGenerateCrashLog.cold.1 + 95
    4   libGPUSupportMercury.dylib     0x00007fff4f12318f gpusGenerateCrashLog + 89
    5   com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff239d9dd0 gpusKillClientExt + 9
    6   libGPUSupportMercury.dylib     0x00007fff4f12455b gpusSubmitDataBuffers + 164
    7   com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff235afc78 IntelCommandBuffer::getNew(GLDContextRec*) + 48
    8   com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff235afaa6 intelSubmitCommands + 187
    9   com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff235a73f0 Gen7Context::CheckOOM(USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, unsigned long long, bool&) + 1644
    10  com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff235ad4fd Gen7Context::CheckOOM(unsigned long long, bool&) + 97
    11  com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff235aa3e8 Gen7Context::ProgramPipeline() + 96
    12  com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff2366d28e glrIntelBeginPrimitiveBuffer + 166
    13  GLEngine                       0x00007fff388d0d20 gleBeginPrimitiveTCLFunc + 72
    14  com.simulationcurriculum.starrynight.proplus.8.osx 0x0000000102dc39a8 TPanoramaChunk::PlotInSceneRecursive(TScene*, FRect const&, float, TOGLDrawer*, unsigned int, TOGLTexture*, CoordinateSystemEnum, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TCartesian const&, double, TCartesian const*, unsigned char, int) + 1560
    15  com.simulationcurriculum.starrynight.proplus.8.osx 0x0000000102dc38de TPanoramaChunk::PlotInSceneRecursive(TScene*, FRect const&, float, TOGLDrawer*, unsigned int, TOGLTexture*, CoordinateSystemEnum, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TCartesian const&, double, TCartesian const*, unsigned char, int) + 1358
    16  com.simulationcurriculum.starrynight.proplus.8.osx 0x0000000102dc392b TPanoramaChunk::PlotInSceneRecursive(TScene*, FRect const&, float, TOGLDrawer*, unsigned int, TOGLTexture*, CoordinateSystemEnum, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TCartesian const&, double, TCartesian const*, unsigned char, int) + 1435
    17  com.simulationcurriculum.starrynight.proplus.8.osx 0x0000000102dc392b TPanoramaChunk::PlotInSceneRecursive(TScene*, FRect const&, float, TOGLDrawer*, unsigned int, TOGLTexture*, CoordinateSystemEnum, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TTexturePoint const&, TCartesian const&, double, TCartesian const*, unsigned char, int) + 1435
  • 0
    Avatar
    Keiron Smith

    There is a long thread here about the issue: https://discussions.apple.com/thread/253309962

  • 0
    Avatar
    Richard Holland

    Hi Keiron

    Thank you for the above link which just confirmed my thoughts on it. The MAMP thing is just a red herring as this comment sums it up nicely:

    "The problem is your GPU (Intel HD4000). Security Update 2021-007 Catalina broke the Intel Graphics driver." 

    Confirms why yours works with the NVidia chipset. I think Apple should really do more testing before rolling out a disaster like this which (from reading the link comments) is affecting quite a lot of commercial applications. Additionally its not up to the software company to produce a fix for this its really up to Apple and companies such as Simulation and indeed others that are affected really need to lobby Apple about this one. Its worrying someone mentioned that Catalina probably will not get any more security 'updates' but hopefully an urgent device update can be done to address the issue.

    Best regards

    Richard

    ps Oh and in the meantime its another disk utility session to put a clean install of Catalina on again but without the update just so I can run SN8 :-(

     

  • 0
    Avatar
    Richard Holland

    This from Apple support:

    • Okay in that case I will make sure to report this to our techs I am putting this information on my notes. Best way to report to our techs and being able to find resolutions for this kind of issues.
       
      So maybe this will be escalated to their devs (fingers crossed).
       
      Richard
  • 0
    Avatar
    Keiron Smith

    Very unfortunate.  Thank you Richard for helping me focus with the troubleshooting.

    Hopefully, Apple will quickly release another Catalina update.

    Alternatively, is it possible to upgrade to Big Sur?  That might solve the issue too.

    Likely, this is an issue with broken support for OpenGL.

  • 0
    Avatar
    Richard Holland

    Hi Keiron,

    I think we can close this issue now as we wait for Apple to  produce a fix :-). In the meantime users may wish to revert to a fresh install of Catalina and then go up to security update 006 which does not break anything.

    Some may say you should not connect to the net without the latest updates but is a risk I will have to take. Early 2013 MBP 13" machines can only go up to Catalina. It's a rather annoying stealth method of forcing users to upgrade perfectly capable units (analogous to earlier iPhone models being quickly deprecated). One does wonder why Apple categorises 2013 machines 'obsolete' but there again anything over 4-5 years in the computer industry is getting on a bit. Even Microsoft are using this business model with Windows 11 requiring hardware that is averaging a maximum of 3-4 years old.

    I am waiting to see if Apple will produce an M2 class MBP 15 inch but even if they do I will now seriously look at things like 'is the storage and RAM upgradable or integrated to the logic board' as I am thinking of the 'future proofing' aspect of things now.

    Best regards

    Richard

  • 0
    Avatar
    Keiron Smith

    Richard, 

    Regarding Apple, I have seen that they are fighting hard against the Right-to-Repair movement.  Latest iPhones break even when same parts are switched between same iPhone models - essentially, a local tech can not fix the iPhone anymore.  Now, only Apple tech can fix your iPhone.  Likely, Macbooks, if not already, will soon follow suit.

    In line with this, I think now all internal (storage, RAM, CPU) upgrades must also be purchased upfront.  You can't get anything added in after the initial purchase.

    I'm sure the smartest local tech repair shops will find ways around it all.  But, Apple is trying very hard to draw the line given how much can be made from "official" $upport each year.

     

     

  • 0
    Avatar
    Francisco Reyes

    I am talking with the apple support but they say it is the developer who has to fix it

  • 0
    Avatar
    Raymond de Groat

    Francisco,

    It would be great if 3rd party developers were able to resolve this issue, but to my understanding it is the graphic drivers in the security update itself which needs fixing and only Apple can do that. Or am I mistaken? Also it's not just one developer, but dozens. Even Apple's own software which relies on WebGL and OpenGL are among the affected. Here's a YouTube video I made of Safari accessing a WebGL page.

    https://youtu.be/jPo5yisLs1Y 

    But if I'm wrong great. I'd be happy. But even still, if it's the developer who has to fix it, then Apple has some work to do fixing this issue with their own applications. Either way, I am eager for Apple's fix.

    Raymond

     

  • 1
    Avatar
    Keiron Smith

    Our developer Stephen Cook is looking into the issue, and if we can fix this of course we will.  But, as has been discussed above this is not just an issue for SN8.  Many, many apps are affected.

    Also, as has been discussed above, the easiest solution (workaround) at this time would be to use Time Machine to revert to the Catalina build prior to the security update.  This is a prefect example of why Time Machine is an incredible MacOS back-up feature.

    We will post here when we have more information, and if we can fix this with another build, you will find out first here too.

    Thanks!

  • 0
    Avatar
    Raymond de Groat

    Keiron,

    Yes, please keep us posted. I'd like to add that it's not like the affected Macs are all 10 years old. I purchased my MacBook Pro with Intel HD new from Best Buy on November 25, 2016. The manufacture date was the week of September 19, 2016. Apple introduced the 2021-007 security update on the 23rd of September 2021. That means the machine hadn't even been in existence for 5 years before it stopped working normally. I'm not happy about this.

    Raymond

  • 0
    Avatar
    Keiron Smith

    Just want to remind everyone that updating to Big Sur or Monterey is another solution for this problem.

    Is Catalina the last OS supported on your MacBook?

  • 0
    Avatar
    Keiron Smith

    If anyone in this thread would like to try a new build of SN8 we have a beta ready.

    https://beta.starrynight.com/reqreg.php

    Once your beta account is approved please download and install the latest Pro Plus build:

    (8.1.2.2229 - November/29/2021 14:57 EST) (Size: 2.80GB)

    Thanks!

  • 0
    Avatar
    Raymond de Groat

    Keiron,

    Yes. Officially Catalina is the end of the line for my MacBook Pro (13-inch, Mid2012), Model A1278 with (Intel HD Graphics 4000 1536 MB).

    Officially anyway. Unofficially there is a patch for installing Big Sur "Patched Sur" and even Monterey on older Macs, but I don't have great expectations considering Catalina, which Apple claims is compatible with my MacBook Pro, is already facing serious issues.

  • 0
    Avatar
    Jandmg999

    Hi All,  Starry Night 8 was not working for me.  It would download and install but would not run.  I'd get a message that it had shut down unexpectedly.   Tonight Apple did a new security update and Starry Night 8 downloaded, installed and seems to be working.   Running a MacBook Pro Late 2012, MacOS Catalina 10.15.7, 13 inch with Intel HD Graphics 4000 , Intel i5, 16 GB RAM - hope this helps.

  • 0
    Avatar
    Jandmg999

    Sorry amendment - the MacBook Pro is a mid 2012.

  • 0
    Avatar
    Raymond de Groat

    Thanks for the timely info Jandmg999 I can also confirm that after installing Apple Security Update 2021-2008 Catalina, Starry Night is working again, as it was before the 2021-007 update. Not surprisingly, other applications which depend on OpenGL are also working again. Thanks to Keiron Smith and everyone at Simulation Curriculum for their support!

    https://support.apple.com/en-us/HT212981

  • 0
    Avatar
    Keiron Smith

    This is excellent news!  Yay!

    Thanks everyone for your patience waiting for a fix!

     

Please sign in to leave a comment.