-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rotate segfaults in /home/darktable/rpmbuild/BUILD/darktable-3.4.1/src/develop/tiling.c:1143 #8510
Comments
it appears that there is an improper value of -1 in the structure "oroi_good.height" this appears to cause the loop to spin until there no 16char chunks anymore :( tiling.c:1142 Now, upon startup, that picture causes a "Working" to be displayed on the picture, and a segfault on the "terminal" window running gdb/darktable. |
This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue. |
@johnny-bit from my understanding this was a rotate error in rcd, is fixed so close the issue :-) |
yes sir! |
any referense # |
@jenshannoschwalm - which PR # could have fixed this? |
#8856 should have fixed it. |
Thanks! |
Well, it still core dumps? Thats from |
how does one un-do an improper close? Clicking on "CLOSED" does nothing |
version can be checked with Can you attach an xmp that causes an issue and if necessary - image file? i tried to replicate via rotation (CW/CCW) and never got tilling problems. I tried with different demosaicers... |
I also would be very interested in thos files. Also; are you using lua scripts by any chance? Also, you mentioned source rpms in your initial descriptions, now have cloned the git here to compile? Also Fedora - i am also using it, still fedora 33 here. What sys are you using, F34? Already on gcc 11? |
@UsefGeorge - can you produce the files? We're very interested in getting to the bottom of the issue. |
@UsefGeorge - Please send sample files and requested information. Currently we lack information to start investigating... |
There have been at least 3 pr's fixing rotate issues ... |
@jenshannoschwalm - yes, there were. And I couldn't reproduce this.. AND it's tiling related. buuuut... Looking tat the code in question it might be possible to overshot calculation for wd & ht since it has size_t problem I was hunting in memory alocations. Eg if for some reason i think there's a possibility for int overshot so "sanitization" of that calcoulation COULD be /* the output dimensions of the good part of this specific tile */
size_t wd = (tx + 1) * tile_wd > roi_out->width ? (size_t)roi_out->width - tx * tile_wd : tile_wd;
size_t ht = (ty + 1) * tile_ht > roi_out->height ? (size_t)roi_out->height - ty * tile_ht : tile_ht; what do you think? |
don't know. can't imagine int overflows here, checks for <= 0 might be necessary to find where something goes wrong. The --enforce-tiling option might help here :-) |
This issue did not get any activity in the past 30 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue. |
@jenshannoschwalm - can you take a look at #9701 if it's ok? if it's ok then it'll close this issue. if not then i guess we'll be closing this issue untill we get sample files to reproduce the issue. |
For me that looks good, although I don't know how to test as I also didn't have a reproducer here. Btw I had been testing this after the tiling debug option a lot . |
Built darktable from rpm sourced designed for Fedora
[Mail@omen-gatworks ~]$ uname -a
Linux omen-gatworks 5.8.15-201.fc32.x86_64 #1 SMP Thu Oct 15 15:56:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Surprised it came together and worked.
Anyway, imported some 3k .jpgs as well as some NEF * nikon raw files"
Picked on one of them to play. During the rotate feature, darktable deceided to segfault.
Tried again, but used gdb to see where its issue is located:
On 3/18/21 10:12 AM, Postmaster wrote:
thats all i know.
The text was updated successfully, but these errors were encountered: