Chris B

As MEB said, thanks for the detailed bug report. It is always so helpful when we have nice easy steps to follow
If this bug is impeding your workflow, you can install the beta alongside the retail version from here:
 

Well I can now create one at that size from New Doc, however resizing a small JPEG to the dimensions mentioned gives me a consistent crash. There's something worth investigating here! 

Sorry I'm late to the party... I can't even create a 65,000 px x 65,000 px document without the app crashing 🙃
We shouldn't crash but to be honest, I'm not surprised such an enormous document is causing issues. I know 65,535 px is the max size for a JPEG but I can't imagine many people work to that. 
Some apps will even enforce their own max size. If it's any consolation, Photoshop on my Mac crashed once but on the second attempt it did create a blank JPEG at max size after 7 minutes 👀
Edit 1 - If we were to try and sort this, I'm not sure if we'd either impose a max limit or actually work on improving stability. Worth asking though! 
Edit 2 - I've just tried this on Affinity Photo on my Mac and is created the document in second or two... Probably something for Windows to improve then. 

Well I can now create one at that size from New Doc, however resizing a small JPEG to the dimensions mentioned gives me a consistent crash. There's something worth investigating here! 

Chris,
I did say in the opening post that getting to that size was the result of an error on my part. I certainly can't think of any circumstances where I would normally want to export a JPG of that size.
I see the issue firstly as whether Affinity Photo's JPG export process should be using the amount of memory it is, and then secondly whether a future version could provide a more graceful termination, even if that means applying some limits (maybe based on available memory).
 

I'm in conversation with Wacom.  They seem to think this is a driver issue.  It happens not only with Affinity Photo and Deisgner, but also when I use Clip Studio Paint.

Short preview of P playing, opening AP. 
IMG_1999.MP4

Chris B,
I followed the steps as listed.  It seems that this is the issue.  If I move my pen off the tablet, it seems I can no longer get access with the mouse.  Very strange.

@Chris B thank you for the help - and thank you, @Sean P - I can finally get the photo of my dog to print! XD

I just scared my dog half to death after cheering so loud 😂
So it was staring at us right in the face for a few days. I could kick myself that I didn't notice that was missing. Luckily a colleague @Sean P spotted it after posting in the development chat we had going. I'm really pleased! 

Try to take a bigger brush-size and don’t’ try to edit all way over in once. Try the size to 3 lines you want to delete and take smaller portions.

Hi Affinity team.
I found a crash. Attached the project to reproduce.
Do the steps:
Ctrl click on top layer group to set pixel layer selection of the layer boundings press Q to switch to edit pixel selection Try to move the mask by dragging inside transform box. Here it is. Thank you.
Win10 x64 Affinity Photo 1.8.3.641
 
affPh_1.8.3_641.sviter_crashReport.afphoto

Sorry folks the problem seems to have corrected itself. I reloaded the 1.8 update but had to do it about three times.

I just scared my dog half to death after cheering so loud 😂
So it was staring at us right in the face for a few days. I could kick myself that I didn't notice that was missing. Luckily a colleague @Sean P spotted it after posting in the development chat we had going. I'm really pleased! 

I just scared my dog half to death after cheering so loud 😂
So it was staring at us right in the face for a few days. I could kick myself that I didn't notice that was missing. Luckily a colleague @Sean P spotted it after posting in the development chat we had going. I'm really pleased! 

Good news! I added the sRGB IEC61966-2.1 profile, set it as the default, and everything appears to work correctly!

Hi @Fritz_H, the issue is not related to a 10-bit panel, wide gamut display, anything like that. I simply think it's your colour preferences and how your workspace colour settings are configured.
I appreciate you want to work in ROMM RGB for more intense colours, but because you have changed the default colour profile (rather than changing it on a per-image basis whenever you develop a RAW file), you must take into consideration how this affects all imagery you bring into Affinity Photo.
Normally, with panorama stitching, the colour profile will be inferred from the images you provide during the stitching process. For example, if you are stitching JPEGs tagged with Adobe RGB, the final panorama document will be in Adobe RGB. This is true, even if your default RGB Colour Profile in Preferences>Colour is different.
However, there are circumstances when your RGB Colour Profile choice will be used: if the images do not contain any colour profile tagging (you will typically receive a message in the top right explaining your image has been assigned a colour space), or if you have explicitly enabled Convert opened files to working space in Preferences>Colour.
The only way I could reproduce your issue with panorama stitching is by going to Preferences>Colour and enabling the Convert opened files to working space option—could you check your own preferences? If that option is enabled, disable it, then see if your colours are correct. Note that it is disabled by default, so at some point I suspect you may have manually enabled it?
Hopefully that will solve your issue. However, do be aware that I'm unsure as to whether your Xiaomi smartphone JPEGs are intended to be in sRGB or a wider colour space—similar to iPhones and how their images are tagged with Display P3. If you open a single JPEG image, what does the colour profile entry read in the top left?

@Chris B I would add that loading Additional Dictionaries slows the start substantially.

Hi
Here comes the focus merge file. I had the same problem with HDR merge file. Same JPG or raw file print ok.
Focus_merge2.afphoto

I'll query it for you
Update - @IPv6 - this has been confirmed as a bug—thanks!

I'll query it for you
Update - @IPv6 - this has been confirmed as a bug—thanks!

Shift-click is a shortcut for manual drawing. So everything that is work "by hand" - should work via shortcut too.
And this is really problematic to draw straight line by hand when start and finish are several scrolls away on high zoom levels. Zoom in/out every time is not that handy //
Also, this auto-rotating brushes are really useful for some tasks precisely because of autorotation... the whole idea of directional rotation - to let AP rotate brush tip automatically, without manual intervention.
Minor problem, for sure, but still. This is proper use of brush, such functionality is expected (imho, of course...  )

There is a bug with brush rotation when brush is used with shift-clicks (straight lines). For example pick any engraving brush and try to draw straight line with it.
It should be the same as drawing the very same line manually
Also, it is sad that shift-clicks does not interpolate brush size changes /// Would be helful for AP users without tablets

I just tested this on my iPad Pro, 10.5 (iPadIOS 13.4.1) and Pandora plays, without interruption, while opening and editing in Affinity Photo.

Beta versions run along side the retail. Do not uninstall your retail. When installing it should see that you have a retail version installed, and not ask for a serial number.