Neo export crash

Answered

Comments

9 comments

  • Avatar
    Elena Blum

    Hi Derek,

    Where are the images and catalog saved? 

    You may need to ensure that the app has full disc access and access to files and folders. Make sure that you have all the read-and-write permissions for the folder where you store images and catalog.

    Try changing the export directory to an alternative one. 

     

    0
    Comment actions Permalink
  • Avatar
    Member

    Hi Derek,

    I know this problem from earlier Luminar versions. It has nothing to do with access rights on folders. When software crashes, there is a bug in the code. A cleanly programmed software would simply stop the process and give an error message, but without crashing the program.

    As a workaround, I suggest that you export your images in smaller groups. Depending on the catalog size, this can be very annoying and tedious, but probably the only way to do it.
    Just see after how many images NEO crashes. Then export one or two images less in a group. That should work then.

    0
    Comment actions Permalink
  • Avatar
    Derek Handforth

    I've tried what you suggest. The original export stopped at 335, I then deleted that photo and tried again this time it it went to 420. I then divided the library into 3 and exported each third separately which worked.

    A bit of a poor work around. Are Skylum aware of this fault?

    Derek

    0
    Comment actions Permalink
  • Avatar
    Elena Blum

    Hi Derek,

    I definitely understand how it can be frustrating to have it not work the way you think it should,  so hopefully we can get this sorted out for you.  Please contact us  https://skylum.com/support and we'll be happy to help.

    0
    Comment actions Permalink
  • Avatar
    Member

    Hi Derek,

    I'm glad to hear that the tip I gave you worked out. Skylum should be aware of this problem. Not only me, but other users have reported this and some other issues to Skylum.
    I think the programmers and as well the support team in the forum are doing their best. And if you take a closer look at the development history of Luminar, you can see that Luminar is evolving. Even the big software companies have taken years to learn to respond to the wishes of their customers.

    0
    Comment actions Permalink
  • Avatar
    Member

    I installed Ventura 13.0 on my Mac desktop. Luminar will no longer open. I get an Apple error message. Is the latest 1.5.3 compatible with Apples lates OS???

     

    0
    Comment actions Permalink
  • Avatar
    Member

    this is part of the error message which is like Greek to this old hillbilly:   

    System Integrity Protection: enabled
     
    Crashed Thread:        18  Dispatch queue: com.skylum.DBCoreWrapper.block-dispatcher.<MPDBCatalog: 0x6000029df880>
     
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
    Exception Codes:       0x0000000000000001, 0x0000000000000000
     
    Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
    Terminating Process:   exc handler [2550]
     
    VM Region Info: 0 is not in any region.  Bytes before following region: 4514365440
          REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
          UNUSED SPACE AT START
    --->  
          __TEXT                      10d13c000-10d2a0000    [ 1424K] r-x/r-x SM=COW  ...OS/Luminar AI
     
    Thread 0::  Dispatch queue: com.apple.main-thread
    0   MPLum5Framework                     0x10ed532a1 +[MPLumFrameworkIPService setHistoryPath:] + 0
    1   Luminar AI                           0x10d1636f6 __62+[MPScenarioFactory onCatalogDidChangeScenarioWithCompletion:]_block_invoke + 111
    2   Foundation                        0x7ff819548d47 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
    3   Foundation                        0x7ff819548c3f -[NSBlockOperation main] + 98
    4   Foundation                        0x7ff819548bda __NSOPERATION_IS_INVOKING_MAIN__ + 17
    5   Foundation                        0x7ff819547ed1 -[NSOperation start] + 782
    6   CoreFoundation                    0x7ff81870f81c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
    7   CoreFoundation                    0x7ff81870f752 __CFRunLoopDoBlocks + 406
    8   CoreFoundation                    0x7ff81870eab2 __CFRunLoopRun + 2184
    9   CoreFoundation                    0x7ff81870dbb0 CFRunLoopRunSpecific + 560
    10  HIToolbox                        0x7ff821fefbd6 RunCurrentEventLoopInMode + 292
    11  HIToolbox                        0x7ff821fef9e6 ReceiveNextEventCommon + 679
    12  HIToolbox                        0x7ff821fef723 _BlockUntilNextEventMatchingListInModeWithFilter + 70
    13  AppKit                            0x7ff81b830b37 _DPSNextEvent + 909
    14  AppKit                            0x7ff81b82f9b8 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
    15  AppKit                            0x7ff81b821ff3 -[NSApplication run] + 586
    16  AppKit                            0x7ff81b7f6058 NSApplicationMain + 817
    17  Luminar AI                           0x10d13fa54 main + 217
    18  dyld                              0x7ff818304310 start + 2432
     
    Thread 1:
    0   libsystem_pthread.dylib          0x7ff818630c58 start_wqthread + 0
     
    Thread 2:
    0   libsystem_kernel.dylib            0x7ff8185f661e semaphore_wait_trap + 10
    1   libtbb.dylib                         0x10e44beb4 tbb::internal::rml::private_worker::thread_routine(void*) + 436
    2   libsystem_pthread.dylib          0x7ff818635259 _pthread_start + 125
    3   libsystem_pthread.dylib          0x7ff818630c7b thread_start + 15

     

    0
    Comment actions Permalink
  • Avatar
    Elena O'Brien

    Are you using Luminar Neo?
    If so, please note that it is fully compatible with macOS Ventura.

    In case you experience any issues with it, please reach out to us at http://skylum.com/support and we'll get that sorted out for you ASAP.

    0
    Comment actions Permalink
  • Avatar
    Derek Handforth

    Yes Neo latest version. 

    This suggestion from a member is the only thing that works.

    "I know this problem from earlier Luminar versions. It has nothing to do with access rights on folders. When software crashes, there is a bug in the code. A cleanly programmed software would simply stop the process and give an error message, but without crashing the program.

    As a workaround, I suggest that you export your images in smaller groups. Depending on the catalog size, this can be very annoying and tedious, but probably the only way to do it.
    Just see after how many images NEO crashes. Then export one or two images less in a group. That should work then."

    0
    Comment actions Permalink

Please sign in to leave a comment.