Photos app crashes when selecting an image to view or edit

Hi thanks for the feedback

Drive is formatted to APFS format... Images are generally straight from either icloud (iphone, ipad etc.) or imports from my DSLR so JPEG normally. (don't import the RAW files)

Folder file path is HD\Photos (iPhoto)\Photolibary2

Ignore ownership is selected yes.. code below.. although i have sent the report several times now

Whats really strange is if i plug in my MBP 2017 it works perfectly... Only since i have moved to the Macmini with Blackmagic EGPU this has started happening.. oh it hasn't changed from running Catalina beta to installing the public release either

Process: Photos [975]

Path: /System/Applications/Photos.app/Contents/MacOS/Photos

Identifier: com.apple.Photos

Version: 5.0 (121.17.170)

Build Info: Photos_Apps-121017170000000~1

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Photos [975]

User ID: 501

Date/Time: 2019-12-11 20:57:28.968 +0000

OS Version: Mac OS X 10.15.2 (19C57)

Report Version: 12

Bridge OS Version: 4.2 (17P2551)

Anonymous UUID: 44E5F706-A132-C3C5-7334-FBA97477AEB0

Time Awake Since Boot: 470 seconds

System Integrity Protection: enabled

Crashed Thread: 19 Dispatch queue: NUJobQueue.Interactive_Render.run

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

ID Vend/Dev

9222 67df1002

Seconds Ago ID Type

460.0 9222 Attach

Application Specific Information:

dyld3 mode

Assertion failure in -[NURenderer renderImage:rect:toDestination:atPoint:error:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/Photos/Photos-121.17.170/workspaces/neutrino/Core/Render/NURenderer.m:170

Invalid parameter not satisfying: point.x + rect.size.width <= (NSInteger)destination.width

abort() called

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

0 libsystem_kernel.dylib 0x00007fff6d49725a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff6d4975d0 mach_msg + 60

2 com.apple.CoreFoundation 0x00007fff35e8ad0b __CFRunLoopServiceMachPort + 322

3 com.apple.CoreFoundation 0x00007fff35e898e7 __CFRunLoopRun + 1695

4 com.apple.CoreFoundation 0x00007fff35e88bd3 CFRunLoopRunSpecific + 499

5 com.apple.HIToolbox 0x00007fff349df65d RunCurrentEventLoopInMode + 292

6 com.apple.HIToolbox 0x00007fff349df39d ReceiveNextEventCommon + 600

7 com.apple.HIToolbox 0x00007fff349df127 _BlockUntilNextEventMatchingListInModeWithFilter + 64

8 com.apple.AppKit 0x00007fff33050eb4 _DPSNextEvent + 990

9 com.apple.AppKit 0x00007fff3304f690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352

10 com.apple.AppKit 0x00007fff330413ae -[NSApplication run] + 658

11 com.apple.AppKit 0x00007fff33013775 NSApplicationMain + 777

12 libdyld.dylib 0x00007fff6d3567fd start + 1

Yes its becoming highly frustrating

I have just gone out this week and purchase a bigger MCP, so will be getting rid of the mini, but was planning to use the Black Magic as a doc to take some of the load of the MCP whilst providing the charge / additional ports etc.

Apple... is there going to be a fix anytime soon? or should i be planning to return the EGPU on the basis of mis-advertising that its "fully compatible" with apple programs??

Sure if Lightroom can figure it out... theres no real excuse...

After much messing around, i have since binned the Mac Mini, and also my 13" 2017 MCP and replaced with a new 15" MCP

Still using the black magic, and all seems to be working as it should now...

Just another mystery... although i will soon be getting rid of the black magic probably, as the 15" pro has enough GPU power now for most of my editing.. so its basically an expensive thunderbolt 3 hub now

Thanks all for your comments, as it was good to hear i wasn't alone