Color fill bug and crash

[Ryuuga]

Windows 10
Affinity Photo version 2.0.0

Can you reproduce it?
Have not tried, but I will attempt to retrace my steps to the best of my ability here.

Does it happen for a new document? If not can you upload a document that shows the problem?
Happened with a relatively new document that I started yesterday. Cannot provide sample doc.

If you cannot provide a sample document then please give an accurate description of the problem

   Is hardware acceleration (in Preferences > Performance) ON or OFF ? (and have you tried the other setting?)

OpenCL ON produces the image you see below. OpenCL OFF straight crashes Affinity Photo.

   What happened for you (and what you expected to happen)

Made some freehand lasso selections and then attempted to fill them with color. Result: color filling in random spaces and even has some weird looking display glitch. (Photo attached below) Expected: color to fill within the selections.

   Provide a recipe for creating the problem (step-by-step what you did).

- opened a new doc in Publisher,
- added a master page with photo frame
- added bunch of pages  with said master page.
- filled the pages with Place image.
- Switched over to Affinity Photo for editing
- DUPLICATED AND RASTERIZED IMAGES
- DENOISED SOME 10% and added some black and white leveling (I'm working with blackand  white comics)
- Now I make my selections 
- once done, I tried to fill a few pages with color. Works okay so far.
- Save doc and closed program.
- Following day, I opened the same document, Gets an error about unlinked files(?)
- Decides to ignore it and continue filling color for the remaining pages
- BUG OCCURS

Now it is worth mentioning that I have done this exact workflow on a previous separate document with no issues whatsoever. The issues above in UNDERLINE AND ITALICS are the only NEW steps I did for this document. Other than that all is the same.

   Screenshots (very handy) or a screen capture/video.
Included below. I can't show the actual image itself, but this was done on an empty Pixel Layer within the document. 

   Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers.
Not that I know of

   Did this same thing used to work and if so have you changed anything recently? (software or hardware)
Did not change any hardware of software.

Things I've done so far to try and fix the issue:
- making a new layer(Bug Persists)
- deleting old layers one by one to try and isolate the problem layer (Bug still persist)
- Restart the Affinity Photo program (Bug still persists)
- Restart Computer (Bug still persists)
- Turn OFF OpenCL (Affinity Photo Crashes instantly)

Hypothesis, Saved document is corrupted somehow. Might have to redo this entire piece again.

[Komatös]

Hi @Ryuuga

Maybe installing the latest version 4.8.1 of MS NET Framework will help.

Download: https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net481-web-installer

[Ryuuga]

Thank you for your reply. I have just installed 4.8.1 MSNET from the link you provided. Restarted the PC. 

The Issue is still there after installation and restart.

[Chris B]

Hey Ryuuga,

I have tried to follow the recipe but the file I created was fine. I know you said you cannot show the image but I'm not sure if you meant publicly or at all. We have a private Dropbox account that goes directly to the developers if you wish them to have a look - https://www.dropbox.com/request/QOTyWKpK3LQGA8VDw9hg

[Ryuuga]

Hey Chris, thanks for the quick reply and help. 

I fiddled around with it a little more and manage to find a workaround. Turns out my ICC color profile was set to Gray/16 greyscale D50. When I changed that to Gray/8, the color fills works exactly as it should, filling out the selected areas. After that I tried saving, restarting program, reopening the document and it is still working fine with  Gray/8 setting.  

I'll be honest, I'm not entirely sure what the differences or 8 vs 16 is yet at the moment, but I guess I'll be working with gray/8 for now. Hopefully that might give you some clue on reproducing the issue though.