Indeed, the Windows version is the less stable one, firstly because it is the only OS I cannot test directly, secondly because either there are Windows-specific bugs or bugs that are occurring more frequently under Windows (due to the different OS and/or compiler).
Anyhow, in case you will have some time to help me identifying and solving those bugs, I have prepared an updated windows version which has debugging symbols included and which ships a gdb.exe command that can be used to debug a photoflow instance. You can get the latest installer (tagged 20170111) from here.
The procedure for generating a useful crash report is pretty much the same as the one suggested here for RawTherapee:
- open the windows console
- go into the folder where the photoflow.exe executable is stored (install_directory\bin)
- run photoflow through gdb:
gdb.exe photoflow.exe
and then type
r
at the GDB prompt to start photoflow - when the program crashes, save the full backtrace to a
log.txtfile with those commands:
set pagination off
set logging file log.txt
set logging on
thread apply all bt full
You might want to try blending the a and/or b channels in overlay mode as well… this allows to do some interesting “contrast by color” adjustment, as I described here.
Thanks for your feedback!