#1 0x0000000000b1fe1c in BibbleIccTransform::Apply(BImage*, bool volatile&, int, int, bool, int) () #0 0x0000000000d08573 in void Labby::matrixRgbToRgbPlanar16SIMD(BImage*, FMatrixType const&, unsigned short const*, unsigned short const*, int, int, int, int) () (Each trace is of the same thread in the same running context, gathered a few seconds apart while the program is stuck.) So, if I get the program stuck in this state where it isn't doing anything, here is an example of the only thread that has any meaningful difference - it's clearly not a classic thread deadlock, but something is stuck. Sudo gdb -pid=$(pgrep After) -x dump_backtraces.gdb -batch > $(date +%s).gdb.txt Script to gather thread backtraces from running app: Prefs Home: /home/user/.config/Corel/AfterShot Pro.conf System Home: /opt/AfterShotPro2(64-bit)/supportfiles
* looking at the logfile (nothing interesting, just adding items to batch, and processing raw file.)Īpp Path: /opt/AfterShotPro2(64-bit)/bin/AfterShotPro
* manually pinning the task to a single core (to minimize chance of deadlocks) * using OpenCL (crashes / makes corrupted output images) * using the default "performance" options * setting all "performance" options to 1 (and restarting the application afterwards) I can add additional items to the batch, but they are just at the end of a FIFO that never consumes any more items. UI is still responsive and quitting still (eventually) works without killing app, but it is clearly stuck on processing.
Basically, I can't reliably batch process images - after some (semi-correlated but not entirely reliable) number of images have been processed, no further work is done, and the program consumes CPU at a high rate. I've been struggling for a while with a problem with AfterShotPro2X64 and am about to give up in frustration.
0 kommentar(er)
