Replace Color crashes Aseprite
https://github.com/user-attachments/assets/cbf284f4-9018-42d0-b297-9b675e44bb9f
From my observations it is because of these two (or one of the) parameters:
I am attaching my settings just in case:
[theme]
selected = default-dark
[general]
screen_scale = 1
ui_scale = 2
[experimental]
multiple_windows = true
use_native_file_dialog = false
[color]
manage = true
working_rgb_space = Custom Profile
files_with_profile = 3
missing_profile = 3
window_profile = 1
I was able to reproduce this just one time, probably related to #4991
@dacap same error occurs if you simply turn off color management, tested on Aseprite v1.3.14.4-dev.
@ElderlyGlek I saw that sharing crash data is unchecked, would you mind to enable it?
@ElderlyGlek I saw that sharing crash data is unchecked, would you mind to enable it?
@dacap I am currently using the dev build. Would it be okay if I sent you the file Aseprite-crash-1.3.15.2-dev.dmp?
@ElderlyGlek we'd require three files, aseprite.exe, aseprite.pdb (it's quite large file), and the .dmp. If please you could upload them in a shared folder and send me the link privately to [email protected] it'd be great.
@dacap the problem is that I deleted Aseprite.pdb… If you want, I can either rebuild Aseprite or download the release version (I have a license) and report this bug. If you really need it, I can do both.
If you can give a try to the official version, reproduce the crash with it, and share the crash data, that will be the best. Would you mind to send me your aseprite.ini file at [email protected]?
@dacap I literally wrote my Aseprite.ini in text form at the very beginning, just copy and paste the text. If I don't forget, I'll report the bug after work.
@ElderlyGlek the aseprite.ini will contain an uuid to match your issue with the crash report, but in the best case, try to reproduce the crash several times, and after sharing the crash data we'll receive all these crash reports.
@dacap I sent you an email and also reproduced this bug four times in a row (twice with Color Management enabled and twice with it disabled).
Thanks @ElderlyGlek, I've just received your mail and was able to check your crashes. It looks like it's the same issue as #4991, I'll try to fix it for the next release, probably send you an alpha version to test the fix if you wish.
@dacap no problem, I don't mind testing the fix in the alpha version.
This bug was fixed in v1.3.15.4 (#4991) with #5436