Besides the background layer with a 'B/W image' I created a layer to add some colour. When I use the eraser in that layer, a white haze appears.
I've never experienced such a thing in over 15 years of Photoshop use.
Normal, coverage 100%
In the image below clearly to be seen the eraser stroke from left to right. The white haze best to be seen at the darker part.
I don't have a computer right now with CC to check this, but there have been some issues white fringing around patterns - mainly in CS6. there have been a lot of changes with using GPU, so maybe this could be a result of that. Do you get the same thing then you apply a layer mask to your colored layer and mask out the color that way? that is actually a better way to work, as you can go back and re-edit if you want. The eraser tool is a bit too distructive.
I had a problem like these wet edges on a brush. Toggling the color calibration profiles in a certain way would make this go away temporarily. In addition had very light dots under 7% going to invisible. Tried running the hardware color calibration multiple times, but could not get this to go away, until I create a new user account.
Before you try a new user acocunt see if you have any brush settings on, turn them all off.
First, as you can see, never posted on this form before. It looked like I replied to one specific person... Anyway.
I found a solution myself. The correction was made in CMYK mode. Changing the mode to RGB made the haze disappear.
Switching between colour modes back and forth isn't my favorite handling because of the color management.
So if you have more ideas please let me know.
I'm not at my computer that has CC loaded, but it dosen't happen with CS6, so if that's the case, it looks like a bug. I agree, switching back and forth between color spaces isn't a good idea. There have bee a lot of changes with GPU and how it works with PS, so this might be a side affect. As I mentioned above, white lines sort of like the ones you're getting were happening with the pattern fill, and it was corrected fairly easily, Hopefully the same can be true for this. Hopefully someone of the staff will respond, but you can submit a bug at: