New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMP file crashes darktable, segmentation fault #14241
Comments
If you want someone here to analyse that file you'd have to share it. Some files are just broken :-) Or you use exiv2 first to see for something obvious |
This chunk of XMP is broken. |
I didn't touch that code part yet, Any idea why/how that would happen? Or could we do some xmp validation? |
I think the broken XMP is because the OP has not properly cut&paste it here or what I think is that the XML tag have been broken by GitHub rendering. |
I have checked (I have the permission to edit the original post) and putting the XMP inside a code block fixes the XMP. |
But I have been able to load the XMP without issue now. So cannot reproduce the issue on my side with current master. |
Thank you for the quick reply! I sent the image to TurboGit, exiv2 does not show any issues: |
I had a look and it seems that the rotation and perspective module has buggy values. Maybe a crash while editing? I'm not sure how this has happened, but to fix edit your XMP and replace:
To skip the last history (rotation and perspective). From there you can compress the history and you'll be ok. It would be good to avoid the crash on dt side of course. |
Thanks, I don't remember a crash while editing. But I think I copied and pasted a lot of settings between images, maybe that contributed somehow?
Am 19. April 2023 09:12:49 MESZ schrieb Pascal Obry ***@***.***>:
…I had a look and it seems that the rotation and perspective module has buggy values. Maybe a crash while editing?
![image](https://user-images.githubusercontent.com/467069/232994868-9782e248-d536-426c-9dc0-d6fb949cebb4.png)
I'm not sure how this has happened, but to fix edit your XMP and replace:
` darktable:history_end="11"`
by
` darktable:history_end="10"`
To skip the last history (rotation and perspective).
From there you can compress the history and you'll be ok.
It would be good to avoid the crash on dt side of course.
--
Reply to this email directly or view it on GitHub:
#14241 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Describe the bug
I imported a collection of about 400 Fuji X-E4 RAW images (.RAF). I was able to go through all images for a first cull. Then I wanted to edit the remaining images. When I reached about half of the remaining collection darktable crashed each time while generating previews in the lightroom view. On the command line, I get “Speicherzugriffsfehler darktable” (memory access error/segmentation fault).
I tried running darktable with the -d cache and -d all arguments without clear results. Then I tried to rebuild the cache with darktable-generate-cache. It crashed as well, the last line in the -d all output was:
image 7311/7818 (93,51%) (id:7312, file=DSCF8970.RAF)
Removing the RAF file and the
corresponding XMP has fixed my problem. I am able to re-import the RAF
file into a separate collection and use it without issues. But when I
import the RAF file with the XMP file into another separate collection
darktable crashes again.
Darktable should take more care in handling its input data. If data (in
the XMP file?) is broken, darktable should discard the invalid input
data. Anyhow, no kind of input data should lead darktable to a
segmentation fault ("Speicherzugriffsfehler").
Steps to reproduce
Expected behavior
Darktable should handle errors in input data robustly, without crashing. Bad data should be discarded. At no time should bad input data lead to a segmentation fault.
Logfile | Screenshot | Screencast
Commit
No response
Where did you install darktable from?
distro packaging
darktable version
4.2.1
What OS are you using?
Linux
What is the version of your OS?
Debian testing
Describe your system?
Lenovo Thinkpad L13, 16 GB RAM, i7-10510U CPU, CometLake-U GT2 graphics
Are you using OpenCL GPU in darktable?
None
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
The relevant picture is a family picture (egg hunt), so I don't want to put it into the bug tracker, If necessary I can send it to individual developers upon request.
The text was updated successfully, but these errors were encountered: