[Bug] Crash in desktop RC2 from basic use

[astrosticks]

I am running the flatpak on Fedora 43. Full output below.

Simplest way to reproduce:

• Create a blank document
• Create a basic shape (like a circle)
• Wiggle the shape around with the mouse for several seconds until the program crashes

Doing any basic set of operations will crash the app eventually, too.

$ RUST_BACKTRACE=full flatpak run art.graphite.Graphite 

Available WGPU adapters:
[0] Vulkan IntegratedGpu (Name: Intel(R) HD Graphics 520 (SKL GT2), Driver: Intel open-source Mesa driver, Device: 6422)
[1] Vulkan Cpu (Name: llvmpipe (LLVM 21.1.7, 256 bits), Driver: llvmpipe, Device: 0)
[2] Gl IntegratedGpu (Name: Mesa Intel(R) HD Graphics 520 (SKL GT2), Driver: , Device: 0)

Using WGPU adapter: AdapterInfo { name: "Intel(R) HD Graphics 520 (SKL GT2)", vendor: 32902, device: 6422, device_type: IntegratedGpu, driver: "Intel open-source Mesa driver", driver_info: "Mesa 25.2.6 (git-3f12436d80)", backend: Vulkan }
[2:23:0107/115425.578365:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:23:0107/115425.737497:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:23:0107/115425.737571:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:23:0107/115425.890951:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:23:0107/115425.891033:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:17:0107/115425.904719:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.DBus.Properties.GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice: unknown error type: 
[2:25:0107/115430.250296:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT
2026-01-07T19:54:41.532608Z ERROR wgpu::backend::wgpu_core: Handling wgpu errors as fatal by default

thread '<unnamed>' (17) panicked at /nix/store/wmczzm8nwr237hi52rlpa46i8wwh9clv-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/wgpu-27.0.1/src/backend/wgpu_core.rs:1588:26:
wgpu error: Out of Memory

stack backtrace:
   0:     0x562a86e6f41b - <unknown>
   1:     0x562a8556166f - <unknown>
   2:     0x562a86e8a08d - <unknown>
   3:     0x562a86e6b6b3 - <unknown>
   4:     0x562a86e84632 - <unknown>
   5:     0x562a86e84512 - <unknown>
   6:     0x562a86e847e1 - <unknown>
   7:     0x562a86e6c45a - <unknown>
   8:     0x562a86e6b7c9 - <unknown>
   9:     0x562a86e8070d - <unknown>
  10:     0x562a852780e0 - <unknown>
  11:     0x562a872230c4 - <unknown>
  12:     0x562a8530489b - <unknown>
  13:     0x562a8530379a - <unknown>
  14:     0x562a8722b148 - <unknown>
  15:     0x562a854ee6fa - <unknown>
  16:     0x562a854e9cf0 - <unknown>
  17:     0x562a854eb873 - <unknown>
  18:     0x562a857b58d9 - <unknown>
  19:     0x562a85853afe - <unknown>
  20:     0x562a857bf57e - <unknown>
  21:     0x7f68534e0519 - <unknown>
fatal runtime error: failed to initiate panic, error 5, aborting```

[aiamuzz]

I am running the flatpak on Fedora 43. Full output below.

@astrosticks ... for the life of me, i can't seem to find where to download this flatpak release of 'GraphiteEditor' !

Can somebody share a link to the flatpak or appimage version of this software ?

[Keavon]

@aiamuzz the RC series of builds are available through our Discord, specifically the #announcements channel. This is to facilitate a close feedback cycle between us and testers reporting feedback in the #desktop-app channel before the upcoming 1.0 release, where of course public builds will be readily available. If you're interested in testing the RC builds as an early adopter and reporting what works and what doesn't on your machine, you can find the Discord invite link on the project website.

[timon-schelling]

https://discord.com/channels/731730685944922173/874548734304874526/1470513986075099288

[DigitallyGray]

@timon-schelling Unsure if this has been fixed or not, but I thought I would say that hiding both the properties and layer panels stop it from crashing, though I get fairly big lag spikes. These lag spikes usually happen roughly the same amount of time a crash would take. I will also say now that it no longer crashes I have noticed it will steadily increase its use of ram, the lag spikes usually coincide with a fairly big jump in ram, once jumping from 76% of ram to 83% of ram, when all I was doing is constantly resizing a rectangle.

For reference I only had one document open, and it was this.

I started with about ~50% ram, and it rose to around 90% were I stopped as previously it had a lag spike where the out of memory system killed it after my system completely froze for a solid 3 minutes.

Here is a recording (I forgot to include my mouse):

Screencast.From.2026-03-08.22-02-19.mp4

Tested on

• Arch Linux
• Gnome Desktop Environment, Version 49.4
• CPU: 13th Gen Intel® Core™ i5-1334U × 12
• Intel® Iris® Xe Graphics (RPL-U)
• Driver: Mesa 26.0.1-arch1.1 (I think this is the right driver to attach)
• RAM: 16.0 GiB
• RC3

(If this has been fixed for the upcoming RC4 then disregard, but if not I hope this information can be helpful.)

[DigitallyGray]

Did some testing on RC4. It still crashes, but no longer has a massive memory leak.
If the layer and/or either property panels are enabled it will crash.

The UI will also still disappear before crashing, but only if you create a new document. If it crashes and I reopen it, then do my tests it just crashes immediately without the UI disappearing. The UI also briefly reappears moments before crashing/exactly when it crashes. There is also a brief amount of time when the UI is gone where it is still usable. This time this has been consistent.

Edit: Hiding both panels doesn't fully stop the crash, but slows down how long it takes to crash considerably. Both times it has happened the UI disappeared before the crash, but was still partially usable for it stopped responding.

Beyond that my spec haven't changed aside from using RC4.

[JonathanSteininger]

Are you sure its a memory leak and not a vram leak?
I dont know if they are related. But I am also getting the wgpu error: Out of Memory error. and having the same appearance bugs right before the crash.

I can re-create the issue by resizing the application. Which rapidly fills up the system vram. And since my machine has unified memory, it will then appear as using normal memory.

• taken with nvtop

[JonathanSteininger]

I tested on latest git commit 21d2994