Crashes when opening .CR3 (ver 4.8.1)

[shayislam]

Describe the bug

I can import fine, but when I try to open any .CR3 files and edit, the app crashes. This only happens on one of my laptops (Ryzen 5, integrated graphics). Doesn't happen on my gaming PC/Laptop (dedicated graphics). Works for .TIFF and .jpg.

Steps to reproduce

Click on any .CR3 file App will crash

Expected behavior

Darktable should open the file normally and allow me to edit.

Logfile | Screenshot | Screencast

https://github.com/user-attachments/assets/9dc723ff-badd-4fed-933b-de7eb128f8bc

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.8.1

What OS are you using?

Windows

What is the version of your OS?

Windows 11

Describe your system?

AMD Ryzen 5 5500U with Radeon Graphics, 2.10 GHz, RAM 8.00 GB (7.35 GB usable)

Are you using OpenCL GPU in darktable?

I dont know

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

[gi-man]

Go to AMD and download the latest drivers for your card directly from them.

[MStraeten]

in general there aren’t known issues with cr3 in general, so please provide more infos, see

https://www.darktable.org/about/faq/#faq-windows-bugs https://www.darktable.org/about/faq/#faq-windows-logs

[shayislam]

Hi Martin,

Thanks for sending those links over. I've replicated the problem and recorded it on 2 files.

(see file numbered 1) It prints the following line when I open a CR3 file and the software crashes. 396.7300 [libraw_open] extensions whitelist: `cr3' Magick: caught exception 0xC0000005 "Access violation"...

The file numbered 2 shows me opening a couple of JPEGs before opening another CR3 file after which the software crashed again.

I dont quite understand how to open darktable using command prompt to follow the steps to disable opencl but i'll keep reading and try to figure it out. Let me know if the log files mean anything or if there's something else you'd like me to attempt.

Regards, Shay

On Sat, 12 Oct 2024 at 08:22, Martin Straeten @.***> wrote:

in general there aren’t known issues with cr3 in general, so please provide more infos, see

https://www.darktable.org/about/faq/#faq-windows-bugs https://www.darktable.org/about/faq/#faq-windows-logs

— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/17642#issuecomment-2408437565, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7J2JIJ5A4FEQ4FGSW4WY3DZ3DE43AVCNFSM6AAAAABPZWR7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGQZTONJWGU . You are receiving this because you authored the thread.Message ID: @.***>

======================================== version: darktable 4.8.1 start: 2024:10:11 22:15:16

end: 2024:10:11 22:15:16

Magick: caught exception 0xC0000005 "Access violation"...Magick: caught exception 0xC0000005 "Access violation"...Magick: caught exception 0xC0000005 "Access violation"...======================================== version: darktable 4.8.1 start: 2024:10:14 18:57:31

396.7300 [libraw_open] extensions whitelist: `cr3' Magick: caught exception 0xC0000005 "Access violation"...Magick: caught exception 0xC0000005 "Access violation"... (darktable.exe:16036): Pango-WARNING **: 19:27:51.193: couldn't load font "monospace Semi-Condensed Not-Rotated 9", falling back to "Sans Semi-Condensed Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.193: couldn't load font "Sans Semi-Condensed Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.194: couldn't load font "monospace Condensed Not-Rotated 9", falling back to "Sans Condensed Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.194: couldn't load font "Sans Condensed Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.195: couldn't load font "monospace Extra-Condensed Not-Rotated 9", falling back to "Sans Extra-Condensed Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.195: couldn't load font "Sans Extra-Condensed Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.195: couldn't load font "monospace Ultra-Condensed Not-Rotated 9", falling back to "Sans Ultra-Condensed Not-Rotated 9", expect ugly output.

(darktable.exe:16036): Pango-WARNING **: 19:27:51.196: couldn't load font "Sans Ultra-Condensed Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output. Magick: caught exception 0xC0000005 "Access violation"...

version: darktable 4.8.1 start: 2024:10:11 22:15:16

end: 2024:10:11 22:15:16

Magick: caught exception 0xC0000005 "Access violation"...Magick: caught exception 0xC0000005 "Access violation"...Magick: caught exception 0xC0000005 "Access violation"...======================================== version: darktable 4.8.1 start: 2024:10:14 18:57:31

396.7300 [libraw_open] extensions whitelist: `cr3' Magick: caught exception 0xC0000005 "Access violation"...

[victoryforce]

I dont quite understand how to open darktable using command prompt to follow the steps to disable opencl but i'll keep reading and try to figure it out.

Did you manage to figure it out?

[shayislam]

Hi Victor,

Thanks for checking in and yes I've figured it out.

these are the lines that i use and its fixed it. Still not sure why i have this problem but i just run this every time i need to open the program and it works perfectly.

cd C:\Program Files\darktable\bin start darktable.exe --disable-opencl

Regards, Shay

On Fri, 22 Nov 2024 at 16:38, Victor Forsiuk @.***> wrote:

I dont quite understand how to open darktable using command prompt to follow the steps to disable opencl but i'll keep reading and try to figure it out.

Did you manage to figure it out?

— Reply to this email directly, view it on GitHub https://github.com/darktable-org/darktable/issues/17642#issuecomment-2494179584, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7J2JIKWB347FBOK5TKDS4L2B5MYFAVCNFSM6AAAAABPZWR7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGE3TSNJYGQ . You are receiving this because you authored the thread.Message ID: @.***>

[victoryforce]

these are the lines that i use and its fixed it. Still not sure why i have this problem but i just run this every time i need to open the program and it works perfectly. cd C:\Program Files\darktable\bin start darktable.exe --disable-opencl

So the issue is with your OpenCL driver. BTW, you can just disable OpenCL in darktable settings: (gear icon above the image area) --> processing --> OpenCL GPU acceleration --> untick "activate OpenCL support". No need to always start from command line with disabling switch.

It would be great if you could test if this issue is reproducible with current dev build. You can download it from https://github.com/darktable-org/darktable/releases/tag/nightly

You can install this version in parallel with the already installed one. It is best to make copies of the images for testing this version (so you do not make incompatible changes to the xmp files of the images processed by the previous version). It would also be wise to run the new version only with a separate configuration folder. Or copy/rename the standard configuration folder for restoration if you want to return to the release version.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[victoryforce]

It would be great if you could test if this issue is reproducible with current dev build.

@shayislam As I see you have lost interest and are not responding, this forces me to close this issue, as we are stuck here and cannot do anything due to the lack of necessary information.

As always, if the bug reporter later wants to continue communication and provide information, the issue can be reopened, closing only shows the inability to continue analyzing the problem, not unwillingness.