Thor, the Norseman

@Sean P It looks like it's having trouble with child nodes again, so I suspect it's the same bug, but it's just manifesting itself further down the line.

@Sean P Oh! It crashed again, but this time it did it while attempting to select a node with the Node Tool after using the Pencil Tool for a while... I'm guessing this might be a new bug? Amusingly, one no less annoying than the original bug... Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 liblibpersona.dylib 0x000000011df30d66 Kernel::JailCounted<MasterPageInstanceNode> const Kernel::TreeBaseNDJailCounted<Node, 5, NodeChildListType>::GetFirstChildOfType<MasterPageInstanceNode>(NodeChildListType) const + 262 1 liblibpersona.dylib 0x0000000132208b59 SpreadNode::FindFirstAppliedMaster(int) const + 41 2 liblibpersona.dylib 0x0000000132209818 SpreadNode::GetSnappingGrid() const + 56 3 liblibpersona.dylib 0x0000000132209935 non-virtual thunk to SpreadNode::GetSnappingGrid() const + 21 4 liblibpersona.dylib 0x0000000134960a4f SnappingTool::SnappingData::CreateSnappingResult(Tool const&) + 95 5 liblibpersona.dylib 0x0000000128f29d66 (anonymous namespace)::HandleCurve::SetSnappedStartPoint(HandleTool&, ToolPointSpread const&) + 614 6 liblibpersona.dylib 0x000000011fefca39 HandleTool::UpdateHoverHandle() + 537 7 liblibpersona.dylib 0x000000011feff85a HandleTool::OnMouseMove(ToolPointSpread const&) + 138 8 liblibpersona.dylib 0x000000011e0371b2 Tool::MouseMovedSpreadCoords(ToolPointSpread const&) + 546 9 liblibpersona.dylib 0x000000011e0353d4 Tool::MouseMoved(ToolPointView const&) + 148 10 com.seriflabs.libcocoaui 0x000000010d1db107 -[DocumentView mouseMoved:] + 615 11 com.apple.AppKit 0x00007fff2fa51f28 -[NSTrackingArea mouseMoved:] + 151 12 com.apple.AppKit 0x00007fff2f98ab25 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 4726 13 com.apple.AppKit 0x00007fff2f989667 -[NSWindow(NSEventRouting) sendEvent:] + 478 14 com.seriflabs.libcocoaui 0x000000010d0a4c56 -[PersonaWindow sendEvent:] + 1606 15 com.apple.AppKit 0x00007fff2f829994 -[NSApplication(NSEvent) sendEvent:] + 3220 16 com.seriflabs.libcocoaui 0x000000010d0d9834 -[Application sendEvent:] + 756 17 com.apple.AppKit 0x00007fff2f8175c0 -[NSApplication run] + 755 18 com.apple.AppKit 0x00007fff2f806ac8 NSApplicationMain + 777 19 com.seriflabs.affinitydesigner.beta 0x000000010baf5464 0x10baf3000 + 9316 Full crash log attached below. Affinity Designer Beta_2020-07-26-202250_thor-hackintosh.crash

@Sean P I was using the latest build of Designer (v1.8.3). I see that the latest beta (v1.8.4.5) contains a speculative fix for the bug and will try it now, and let you know if it still crashes.

@Sean P Also, after one of the crashes, a recovery file was opened, and it contained random paths that I hadn't added to the document, suggesting that the heap was corrupted shortly before the crash.

@Sean P ↑↑↑

I am also facing crash issues with the Pencil Tool. Oddly, it has so far only been a problem with a single document, which is just a single JPEG image layer and many pencil strokes. I have had three crashes in a short time so far, usually right in the middle of drawing. They all crash in the dispatch queue, with the same stack trace, so I'm only going to attach one crash log: Affinity Designer_2020-07-26-101045_thor-hackintosh.crash This seems to be the guilty thread, at least in my case: Thread 6 Crashed:: Dispatch queue: com.apple.root.default-qos 0 liblibpersona.dylib 0x000000012f8fe8d1 StructureCommandHelper::~StructureCommandHelper() + 145 1 liblibpersona.dylib 0x000000012f8ea05e AddChildNodesCommand::~AddChildNodesCommand() + 1086 2 liblibpersona.dylib 0x000000012f8eaf5f virtual thunk to AddChildNodesCommand::~AddChildNodesCommand() + 31 3 liblibpersona.dylib 0x000000011e26e5c7 CompoundCommand::~CompoundCommand() + 119 4 liblibpersona.dylib 0x000000011e26df23 virtual thunk to PreviewCommand::~PreviewCommand() + 35 5 liblibpersona.dylib 0x0000000130b6abf6 DocumentController::ProcessCommandQueue() + 5958 6 liblibkernel.dylib 0x00000001114e413c invocation function for block in Kernel::Dispatch::DispatchAndForget(void (*)(void*), void*, Kernel::Dispatch::DispatchPriority) + 92 7 libdispatch.dylib 0x00007fff5e1685f8 _dispatch_call_block_and_release + 12 8 libdispatch.dylib 0x00007fff5e16963d _dispatch_client_callout + 8 9 libdispatch.dylib 0x00007fff5e16ba53 _dispatch_queue_override_invoke + 763 10 libdispatch.dylib 0x00007fff5e1773bc _dispatch_root_queue_drain + 324 11 libdispatch.dylib 0x00007fff5e177b46 _dispatch_worker_thread2 + 90 12 libsystem_pthread.dylib 0x00007fff5e3a96b3 _pthread_wqthread + 583 13 libsystem_pthread.dylib 0x00007fff5e3a93fd start_wqthread + 13 It looks to be an invalid access when adding a child node to a path. My guess is that you're trying to dereference an invalid pointer when accessing a member on an object. Why this doesn't always occur is more of a mystery. For me, it only began happening with one specific document that I created by opening a JPEG file. I could attach the document, which, while amusing, is probably not appropriate for this forum. 😆

Could we get some options to adjust zoom behaviour? Option to always (initially and/or consistently) display documents at the nearest rational zoom level (e.g. 1:3, 1:2, 1:1, 2:1, 3:1, ...) Option to always initially display documents at 1:1 (with option for "Small images only" and "All images") Option to always use nearest-neighbour scaling for rational zoom levels greater than 1 I would also prefer it if the zoom level could be made to never change unless the user requests it.

Will do. PS: Very impressed at: 1. Getting a reply. 2. So quickly. 3. From an actual programmer. 4. I hope you're finding the time to actually code!

I purchased Affinity Photo pretty recently as an Adobe Photoshop refugee. I'm hoping to have some minor annoyances fixed: Crop tool: It needs to use a hairline for the cropping rectangle so you can crop to exact pixels, and it needs to snap to object boundaries, so you can quickly crop the canvas to fit what you have on there. Zoom: The zoom keeps changing back to fitting the window all the time. This is irritating when you want the zoom to keep to whole steps (25%, 50%, 100%, 200%, ...) These might not be super important if all you do all day is edit photos, but it is pretty important for pixel design work, and I did a significant amount of that in Photoshop.