Page MenuHome

painting on a psd image crashes blender
Closed, ResolvedPublic

Description

System Information
Operating system and graphics card
Manjaro Linux, ati mobility radeon 4650

Blender Version
Broken 2.70-1464316

Short description of error

Exact steps for others to reproduce the error
0.smart uv project unwrap cube
1.in blender image editor load a psd file (saved in krita)
2.Paint on it (in 3d view or in texture editor)

blender will crash. This happens on both the stable 2.70 release and 2.70-1464316

Event Timeline

Todor Imreorov (blurymind) created this task.
Todor Imreorov (blurymind) raised the priority of this task from to Needs Triage by Developer.

I don't know if it's related, but krita PSD files have a problem - T39652

Also, I can't reproduce the issue here (OSX). And I find strange that a PSD would present a specific bug like this (internally they are all image buffers).

Can you please share a file where this problem shows up?

I don't know if it's related, but krita PSD files have a problem - T39652

Also, I can't reproduce the issue here (OSX). And I find strange that a PSD would present a specific bug like this (internally they are all image buffers).

Can you please share a file where this problem shows up?


This is the problematic krita psd file that causes blender to crash.

opening it in gimp, i get a warning message about an embeded color profile (invalid- utf8 string). It asks me if I want to convert it to rgb working space.

When I convert it in gimp and save it out as another psd, the gimp psd wont load in blender at all.

Weird.

Can you attach the file after you saved it in gimp too?

For the records, if I open it in Photoshop and save it, it works fine.
The full backtrace is here: P60

The file saved in photoshop has colorspace "sRGB". The file saved in Krita has the colorspace "" (blank). Or it's something OIIO doesn't recognize and it spits out as "".

@Sergey Sharybin (sergey) if the file comes with no colorspace, should we assign it to a fallback ("sRGB") ?
Or the problem is in colormanagement that should be able to handle empty colorspaces?

Apart from that @Todor Imreorov (blurymind) you could report this upstream (in krita) - https://bugs.kde.org
It may be a bug in OpenImageIO too, but I'm not sure if the PSD specs reinforce a colorspace.

fixed now, we are falling back to sRGB. It is still a bug in krita, but at least it won't affect us.

Hi, heres the file after being saved in gimp.

Thank you for resolving this bug. I hope krita devs do so as well.

Krita developers are very responsive (you can even find "boud" in #blendercoders IRC, which maintains PSD for krita). But they will also need a bug report in their tracker to take care of that ;)

@Todor Imreorov (blurymind) could you attach one of your gimp files in the upstream report (in the krita tracker)?

It no longer crashes blender in the newer krita, however the file imports with the wrong colors!

try yourself:

If I open the file in PSD and save it, it looks fine in Blender.

do you open and save it in gimp?
Please see this:
https://bugs.kde.org/show_bug.cgi?id=334582

Krita devs confirm this bug. Seems like a krita bug

@Dalai Felinto (dfelinto):
May he say that blender reads it in defiance of color profile included in the psd file?

@Todor Imreorov (blurymind):
It is one of the restrictions if I point out that you are displayed with a different color in blender.
OCIO does not support embed colorspace now.
It should be output by a console screen.