Bug 515105 - crash when exporting: Error std::bad_alloc sending event 3 to object file
Summary: crash when exporting: Error std::bad_alloc sending event 3 to object file
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: * Unknown (other bugs)
Version First Reported In: 5.2.13
Platform: NixOS Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-26 12:54 UTC by Tobias Bora
Modified: 2026-01-27 10:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Bora 2026-01-26 12:54:18 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY

When exporting any document, Krita crashes.


STEPS TO REPRODUCE
1. Create a new 2000x2000 blank empty image
2. Click "File / Export"
3. Wait a few seconds: it crashes.



OBSERVED RESULT

Crash

EXPECTED RESULT

No crash

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: NixOS 25.11
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.12.32 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 165H
Memory: 32 Gio of RAM (30.8 Gio usable)
Graphics Processor 1: Intel® Graphics
Graphics Processor 2: NVIDIA RTX 2000 Ada Generation Laptop GPU

ADDITIONAL INFORMATION

See also https://github.com/NixOS/nixpkgs/issues/483990 in case it is a nix-specific bug
Comment 1 Dmitry Kazakov 2026-01-26 13:37:12 UTC
Hi, Tobias!

Could you provide a backtrace? It seems like the problem is NixOS-specific.
Comment 2 Tobias Bora 2026-01-26 18:40:38 UTC
Thanks for the quick answer. I got this backtrace https://github.com/NixOS/nixpkgs/issues/483990#issuecomment-3801118153, is it enough?
Comment 3 Tobias Bora 2026-01-26 21:37:01 UTC
Problem solved: as noted in the above thread, this is due to a file `~/.config/QtProject.conf` that grows crazily in size with garbage content (accentuated letter that is duplicated during 500Mb). Removing the file fixes the issue. Now I don't know if this is something you can/want to fix, e.g. by detecting if this file is too large and clearing it if so…
Comment 4 Bug Janitor Service 2026-01-27 03:48:51 UTC
🐛🧹 Thanks for your comment!

Automatically switching the status to REPORTED so the team can perform further triage.

In the future you may also do this yourself when providing needed information.
Comment 5 Dmitry Kazakov 2026-01-27 10:27:17 UTC
Thank you for the info! :)