Preview won't display large jpgs

[monokakata]

I updated to 10.10.3 this morning. After the update, I find that Preview will not display jpgs in 7360x4912 size (D810) if those jpgs were exported from LR 5.7, using the same LR settings I've been using for many months.

The image flashes briefly (maybe a second) and is then replaced by background, which seems to scroll up. If I ask for a thumbnail I get one. But I can't do anything with it.

If I use Preview on a 7260x4912 NEF -- no problem.

If I take the 7360x4912 jpg into Photoshop and do nothing but write it back out again, Preview will open it. The same is true for a NEF that I bring into PS.

I took a Sony RX100 jpg into LR, sized it to 7360x4912 for export, and Preview failed. At 7220 it fails. At 7018 it doesn't. At 7019 it does.

It seems to be a LR--Preview collision of some kind, but what could that be?

I'm baffled.

 

[yugioh5d]

I have the exact same problem. My preview won't view image of size 7680 × 4320. It only happened on my iMAC 5K though. I can view just fine on the Macbook Retina.

What piss me off even more is that, Apple support asked me recover OSX, Internet Recovery, Clean install, then PRAM reset.......after they satisfied, they have sent a note to the developer about the issue......I have wasted like 5 hours just for this.....

 

[monokakata]

Mine is a retina iMac also. I haven't upgraded my retina MBP, but maybe I'll try it now that I'm using Xee3 instead of Preview, for looking at jpgs.

Sorry that you're having the same problem, but especially sorry that Apple had to you do all that stuff.

 

[yugioh5d]

Mine is a retina iMac also. I haven't upgraded my retina MBP, but maybe I'll try it now that I'm using Xee3 instead of Preview, for looking at jpgs.

Sorry that you're having the same problem, but especially sorry that Apple had to you do all that stuff.

I too feel pity of myself.....the support team should first check with the developers first before let me do all these cause you know Preview can open normal images just fine. All the 'fixes' that I did basically are meaningless, but now it is clear that it is a software bug. I suggest we should all send a note to developer to let them fix this.