-
Notifications
You must be signed in to change notification settings - Fork 36
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
Segfault while opening a second RAW loader #40
Comments
Thanks for reporting this issue, I will have a look into it as soon as possible. Meanwhile, I think it is useful to clarify how RAW images are loaded in photoflow: the "RAW loader" merely reads and decodes the RAW data, but does not apply any post-processing. In order to convert the RAW data into something useful, you need to add a "RAW developer" above the "RAW loader". To add a second RAW file above a first one, I recommend to follow those steps:
Hope this helps. |
Ah, yes, I should have mentioned I did give groups of loader + developer a try, with segfault as well. Thanks for the recommendation though, and also for this very attractive piece of software. I'll be happy to provide more debug output if you somehow don't encounter the issue. |
You are welcome! I'll try to reproduce your issue tomorrow, and I'll post a working PFI if I cannot reproduce the crash. |
Thank you, the bug is fixed as far as I can tell! The latest batch of commits added a new bug, though (commit ad16291 I believe, as it works when reverted). When I add a RAW developer layer on top of a single RAW loader with the above EOS 1000D file, PhotoFlow gets stuck after outputting
Please let me know if I should file a new report for this, and thanks again for your response! |
Ooops, I'll have a look into that as soon as possible, that's really a serious regression! |
For the moment I could no reproduce the lock you observed, at least not on my Mint system... If you have some experience with gdb, here is what you could do to greatly help me pin down the problem:
This way I can see where each thread is blocking, and therefore what is causing the deadlock condition. Just let me know if you need further help. Thanks! |
UPDATE: I've probably finally managed to reproduce the lock, and it should now be fixed in the "stable" branch. Could you check that? This also means that there is no need to do the gdb "gymnastics" for the moment... Thanks! |
Thanks for the fix! That seems to have fixed the deadlock I reported, but by testing I accidentally found another one. I got it by opening a RAW file, adding a group, moving the RAW loader into the group, adding a RAW developer on top of the group, then moving the raw developer at the top position inside the group. That last move got me a lock. I can reproduce the issue consistently in a current stable debug build by opening this pfi file for the EOS 1000D raw sample and, while the view is loading, moving the raw developer on top of the loader into the group. After the view is loaded, the move seems to work fine. I seem to be able to trigger a lock without using groups too, by moving the develop layer around. At least this lock isn't as nasty from a usability point of view. Here's a backtrace from that
|
Thanks for the detailed backtrace, that will be really helpful! I've already some idea of what could be wrong, will try to look into that later. However, the fix might not be as trivial as the last one... I'll still leave this issue opened until everything is fixed. |
Great! Thanks again for your perseverance, I greatly appreciate it 😄 |
Should be fixed in 0.2.1, closing issue. |
I can't seem to open two RAW files in the same project. I'm not a regular photoflow user so pardon my inaccuracies and lack of experience with the software.
Steps to reproduce:
I am running Arch Linux, with VIPS 7.42.3 from the official Arch repositories.
Here's a gdb backtrace from a debug build (
./build.sh debug
) of current master, although I don't know whether that's useful. Please let me know if I can provide more information.Another backtrace using two copies of this Olympus E-M5 image from rawsamples:
Thanks!
The text was updated successfully, but these errors were encountered: