Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mac Update to Big Sur causes crash when moving do files

    Hello everyone,

    I just updated my macbook pro to Big Sur. I am using Stata SE 15.1.

    I am using multiple do files so I would like to open them side by side on one window. When I open two do files, and try to move one of them to the side of the screen so that I have two do files on two windows, I experience a crash in Stata.

    I attach the beginning of the crash report below:

    Is there anybody else who experiences this? And could you find a solution to this?

    Thank you for your time,
    Emre

    HTML Code:
    Process:               StataSE [4505]
    Path:                  /Applications/Stata/StataSE.app/Contents/MacOS/StataSE
    Identifier:            com.stata.stata15
    Version:               15.1.640 (15.1.640)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           StataSE [4505]
    User ID:               501
    
    Date/Time:             2020-12-05 23:55:08.932 +0100
    OS Version:            macOS 11.0.1 (20B50)
    Report Version:        12
    Anonymous UUID:        3086ACC7-3E41-F9EF-697B-6779E9CEFB53
    
    
    Time Awake Since Boot: 24000 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:
    *** Terminating app due to uncaught exception 'NSImageCacheException', reason: 'Cannot lock focus on image <NSImage 0x600001032d00 Size={0, 0} RepProvider=(null)>, because it is size zero.'
    terminating with uncaught exception of type NSException
    abort() called







  • #2
    I am also experiencing this same problem with Stata version 15.1.643 on macOS 11.6. I just upgraded with Stata version and macOS; previously, this was never a problem. Sorry to say I haven't found a solution, though.

    Comment

    Working...
    X