Jump to content

Mister Potatohead

  • Content count

  • Joined

  • Last visited

  1. Mister Potatohead

    Near instantaneous crash when opening AD Media Browser

    @Chris B Update2: So if I just click on the photos high level folder in the top part of the Media Browser, almost all my photos show up. Out of 4206 photos, the AD Media Browser was able to load up all but 14, some (but not all) the missing ones were the freshest... and the very last one shown in the Media Browser was a gray thumbnail instead of a normal image and when double-clicked, a dialog box came up saying it can't open up some transcoder cache file -- permission denied (screenshot attached). And when I right-click to show it in Finder, it takes me to some com.apple.iLifeMediaBrowser.ILPhotosTranscodeCache folder (screenshot attached). Strange. More often than not, though, the Media Browser just gets stuck and I have to quit AD and open again to have any hope of it loading up again. Update3: All 4206 photos eventually showed up (after a long time), but the last 6 or 7 were grey thumbnails (just like the single one I'd described above).
  2. Mister Potatohead

    Near instantaneous crash when opening AD Media Browser

    It's the default view that comes up. A folder hierarchy on top and thumbnails on the bottom. Other than the apps that are shipped with the Mac, and Affinity Photo, I have no other photo apps or plugins installed. I waited a long time before taking the plunge and buying the Affinity Designer and Photo apps. I would rather have a root canal without anesthesia before getting Photoshop or Illustrator or anything else on a subscription model. Perhaps Apple licensed the iMedia browser for embedded use? A bit of new info... over the past 20 minutes or so, AD has been crashing near instantly and 100% of the time when I open the Media Browser. What's different now?... a Photos background process was running updating faces/people in my Photo Library. So is it possible this crashing issue is somehow related to my Photo library being in a state of flux while the list of Photos albums/folders (and thumbnails) is being populated in the AD Media Browser window... and that's not being handled gracefully? I think everybody's Photos library on Mac is in some state of flux over time if there are photos with faces that can be identified (and new photos have been taken on a device or a change has been made in an identified face, etc.) and also, if iCloud Photos is enabled, there could be a variety of changes driven locally based on iCloud photo library state. Update: So the background process appears to be done, at least for now. And AD Media Browser could be successfully opened without a crash (or at least no immediate or near-immediate crash). Some of the photo library folders are showing as empty though... like Years and Albums... which isn't correct. So maybe some thread is timing out there (or something is buggy with some Apple API you're using) -- but, anyway, that'd probably be a separate issue.
  3. Mister Potatohead

    Near instantaneous crash when opening AD Media Browser

    @Chris B A fresh crash report is attached. Affinity Designer_2018-05-02-132528.crash
  4. Mister Potatohead

    Near instantaneous crash when opening AD Media Browser

    Hello there. I have ~4200 items in my photo library. I performed the suggested clear option (with all items checked). This time the crash took about a half-hour to occur, and meanwhile absolutely nothing was being done in the AD app (the Media Browser window just sitting open).
  5. In Affinity Designer for Mac v1.6.1 on MBP TB 2016 15" running MacOS 10.13.4, when I open the Media Browser, the app crashes. The first time I ever opened it, it crashed instantly. It seemed like after every subsequent re-launch, it took longer to crash each time after opening Media Browser. I wonder if it's related to the size of my Photo Library.... Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [0] Application Specific Information: BUG IN CLIENT OF LIBDISPATCH: Use-after-free of dispatch_semaphore_t or dispatch_group_t Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libdispatch.dylib 0x00007fff64bd58b8 _dispatch_sema4_signal + 103 1 libdispatch.dylib 0x00007fff64bcda0f _dispatch_semaphore_signal_slow + 39 [ … ]