[X] I have read this document and I accept the conditions
Search previous report
[X] I have searched my issue
Computer's operating system
Linux
What GPU do you have ?
No GPU
Ansel version
Ansel-0.0.0+913~g85f2b8b15-x86_64.AppImage
Type of binary
Pre-built packages provided by the Ansel project (.AppImage, .EXE)
What happened?
I'd noticed a lot of messages in the Terminal window saying "[_dev_add_history_item_ext] invalidating history" so I loaded a raw with no xmp or history in the database, and started trying to see what caused the messages. I started with Raw Settings and changed the white point from 16383 to 16300. Ansel crashed. I will try to upload the backtrace to private cloud.
I repeated this in case just a one-off but the same thing happened. However the second time, the Terminal window quoted the same file for the backtrace as the first crash, but in fact used a different name. This could be very confusing!
Code of Conduct
Search previous report
Computer's operating system
Linux
What GPU do you have ?
No GPU
Ansel version
Ansel-0.0.0+913~g85f2b8b15-x86_64.AppImage
Type of binary
Pre-built packages provided by the Ansel project (.AppImage, .EXE)
What happened?
I'd noticed a lot of messages in the Terminal window saying "[_dev_add_history_item_ext] invalidating history" so I loaded a raw with no xmp or history in the database, and started trying to see what caused the messages. I started with Raw Settings and changed the white point from 16383 to 16300. Ansel crashed. I will try to upload the backtrace to private cloud.
I repeated this in case just a one-off but the same thing happened. However the second time, the Terminal window quoted the same file for the backtrace as the first crash, but in fact used a different name. This could be very confusing!
Does your problem occur with OpenCL enabled ?
I don't know
Does your problem occur with OpenCL disabled ?
I don't know
Previous Ansel version that use to work
don't know
Output of ansel -d all
No response
Backtrace
No response