Skip to main content
Inspiring
September 5, 2016

P: Crash hangs indefinitely mixer brush

  • September 5, 2016
  • 5 replies
  • 338 views

Photoshop 2015.5: in 2 of my machines photoshop appears to hang idefinitely using mixer brush on a 16bit document with the latest version: 

steps:

create new document: file->new ->ok

change mode to 16bit image->mode->16bit/channel

select mixer brush, alt click to sample the background of the new document (or just sample something), then make a stroke in the document.

create another document: file->new->ok

 

photoshop hangs indefinitely.

 

also happens if you have the second document already open and you switch to it with the mixer brush active (instead of the last step of creating a new document)

 

another similar way to crash photoshop:

 

create new document

select mixer brush, sample the background and make a stroke in the document

change mode to 16 bit image

photoshop hangs.

This topic has been closed for replies.

5 replies

Legend
November 2, 2016
Legend
September 6, 2016
Fun. I can repro. We'll look into it.
Inspiring
September 6, 2016
They'll be back tomorrow, so they should see this. I couldn't find anything about it, either. 
apeironnAuthor
Inspiring
September 5, 2016
thanks Cristen, makes sense.
both of my machines are windows based (win 7 and 10, tested same behaviour on both).
Haven't managed to find anything about it, so I'm guessing this is still unreported.
Inspiring
September 5, 2016
I believe it's switching bit depth with the mixer brush active that's doing it. If I create or switch to documents with the same bit depth, no problem. If I create a new document and change the bit depth in the dialog from 16 to 8 bit, with the mixer brush active, then it hangs.

I'll turn in a Sample Process report and Force Quit Apple report. You might do the same. If you're on Windows, then we know it's also cross-platform. I don't know if they already know about it or not. I know some people have mentioned some kind of mixer brush issues, but I don't recall it was this issue.