OK, thanks for testing. Then I would say that - given the inherent limitations of GPU memory - darktable does a pretty decent job :)
We cannot influence other applications claiming GPU memory. All we can do is deal with this situation - fall back to CPU but continue trying to use the GPU if possible. Ulrich Am 05.11.2014 um 16:49 schrieb Matthias Bodenbinder: > Am 03.11.2014 um 21:09 schrieb Dariusz J. Garbowski: >> Shot in the dark -- try and disable "Preload next image" and make "Decoded >> image cache size" a small >> value in Preferences -> General in Geeqie? > > I did that and it does not help. I did also check what an idle geeqie will > do, as suggested by Ulrich. > If geeqie is idle (= one picture loaded and window minimized) it does not > provoke the error. Tested with your suggested settings. But as soon as I > start to do window operations with geeqie: maximize, resize, minimize, etc. > the error occurs almost immediately. When I exit geeqie, start it again and > let it sit idle the DT export is full speed again. > > Kind Regards > Matthias > > ------------------------------------------------------------------------------ _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
