You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Affinity no longer responds when selecting an object in a project that has many objects. #109
I have ensured my environment (operating system, app launcher, etc) is up to date
Operating System and Version
Linux Mint 22.1
Launcher
Lutris (Recommended)
Launcher Installation
Flatpak (Recommended)
Other Install
No response
Wine Version
ElementalWarrior (Recommended)
Affinity Version
Canva 3.0.1.3808
Desktop Environment
Cinnamon
Description
When attempting to select any object in a project that has an abundance of objects, Affinity appears to hard crash the moment I try. I have to force stop the process from within Lutris.
For example, it crashes consistently when opening PlayingCards.svg in this free asset pack and trying to select things.
It occurs regardless if I try to click things directly in the viewport or in the layers panel.
changed the title [-][BUG] Affinity hard crashes when selecting an object in a project that has many objects.[/-][+][BUG] Affinity no longer responds when selecting an object in a project that has many objects.[/+]on Nov 30, 2025
I'm seeing the same issue. But it doesn't even have to be a lot of objects. I have a simple SVG object with 4 layers. Dragging any of the layers around causes an instant freeze with no log output.
This happens when using Lutris with EW or GD.
Operating System: CachyOS Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.3-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2080 Ti
I have the same problem - all runners, vulkan and gl. It's weirdly not all svgs. I have imported a bunch of silhouettes of dancing people in my Affinity 3 project in Layout Studio, but selecting one specific layer causes an immediate freeze.
Last lines in the logs are:
(hundreds of the d2d fixme messages)
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_PushAxisAlignedClip Ignoring antialias_mode 0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3120.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE31C0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3120.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3120.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE30D0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE3080.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE1A50.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE1AA0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE1AA0.
0024:fixme:d2d:d2d_device_context_PushAxisAlignedClip Ignoring antialias_mode 0.
0024:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 0000000040EE1B40.
0218:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0214:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
028c:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0190:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0188:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
03f8:fixme:seh:WerSetFlags (2) stub
03f8:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
0408:fixme:process:SetProcessShutdownParameters (00000380, 00000000): partial stub.
0408:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00006FFFFE3925B7, 28) stub
0408:fixme:ver:GetCurrentPackageId (0000000000C0EB50 0000000000000000): stub
0414:err:environ:init_peb starting L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscorsvw.exe" in experimental wow64 mode
0414:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0414:fixme:seh:WerSetFlags (2) stub
0414:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
0408:fixme:service:QueryServiceConfig2W Level 6 not implemented
0408:fixme:service:QueryServiceConfig2W Level 6 not implemented
0408:fixme:service:QueryServiceConfig2W Level 6 not implemented
0408:fixme:service:QueryServiceConfig2W Level 6 not implemented
0408:fixme:service:QueryServiceConfig2W Level 6 not implemented
I've started experiencing this as well. I've noticed that the application isn't actually completely dead - if I use KDE's taskbar to "Terminate Affinity", then Affinity will actually un-hang and ask me if I want to save files before closing. If I hit Cancel on that box, Affinity is actually usable again (although it seems to then get stuck in a state where I can't select anything until I close and reopen the file).
quentinmit's observation that the app isn't fully dead (reviving briefly when you try to force-close it) is a useful clue, that pattern usually means a UI-thread deadlock rather than a crash. If anyone can grab a WINEDEBUG=+seh,+relay log spanning the moment of the freeze (not after, during), that would help. Given how common object-heavy documents are, this is one of the higher-priority unresolved bugs, we just don't have a lead on the actual deadlock yet.
Activity
[-][BUG] Affinity hard crashes when selecting an object in a project that has many objects.[/-][+][BUG] Affinity no longer responds when selecting an object in a project that has many objects.[/+]eatcodeplay commentedon Jan 8, 2026
I'm seeing the same issue. But it doesn't even have to be a lot of objects. I have a simple SVG object with 4 layers. Dragging any of the layers around causes an instant freeze with no log output.
This happens when using Lutris with EW or GD.
Creanimo commentedon Feb 10, 2026
I have the same problem - all runners, vulkan and gl. It's weirdly not all svgs. I have imported a bunch of silhouettes of dancing people in my Affinity 3 project in Layout Studio, but selecting one specific layer causes an immediate freeze.
Last lines in the logs are:
(hundreds of the d2d fixme messages)
Faust90 commentedon Feb 14, 2026
Seems very similar to this issue #76
quentinmit commentedon Mar 8, 2026
I've started experiencing this as well. I've noticed that the application isn't actually completely dead - if I use KDE's taskbar to "Terminate Affinity", then Affinity will actually un-hang and ask me if I want to save files before closing. If I hit Cancel on that box, Affinity is actually usable again (although it seems to then get stuck in a state where I can't select anything until I close and reopen the file).
Gamedirection commentedon Aug 22, 2026
This is tracked as a known, unresolved issue: https://github.com/seapear/AffinityOnLinux/wiki/Install-Guide-Lutris#-affinity-freezes-when-selecting-an-object-in-a-large-or-svg-heavy-document (see also #76, which looks like the same underlying freeze). No fix yet.
quentinmit's observation that the app isn't fully dead (reviving briefly when you try to force-close it) is a useful clue, that pattern usually means a UI-thread deadlock rather than a crash. If anyone can grab a
WINEDEBUG=+seh,+relaylog spanning the moment of the freeze (not after, during), that would help. Given how common object-heavy documents are, this is one of the higher-priority unresolved bugs, we just don't have a lead on the actual deadlock yet.