Shot in the dark -- try and disable "Preload next image" and make "Decoded 
image cache size" a small 
value in Preferences -> General in Geeqie?

Regards,
Dariusz


On 03/11/14 11:30 AM, Matthias Bodenbinder wrote:
> I made some more tests also with newest NVIDIA driver 343.22. What I found so 
> far is that the picture viewer geeqie seems to play an important role in that.
>
> When watching JPG pictures with geeqie while exporting from DT I get the 
> memory issue as soon as geeqie has opened a few pictures. When I quit geeqie 
> the memory issue is gone. That happens even with opencl_memory_headroom: 700
>
> I can not provoke the error with gwenview or ristretto even when both run 
> parrallel. This leads me to the assumption that geeqie is somehow using to 
> much opencl memory. Does that sound reasonable? Any idea how to proof this 
> assumption?
>
> Kind Regards
> Matthias
>
> PS:
>
> ||/ Name                              Version               Architektur       
>     Beschreibung
> +++-=================================-=====================-=====================-=======================================================================
> ii  ristretto                         0.6.3-2               amd64             
>     lightweight picture-viewer for the Xfce desktop environment
> ii  geeqie                            1:1.2-3+b1            amd64             
>     image viewer using GTK+
> ii  gwenview                          4:4.14.2-1            amd64             
>     image viewer
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> darktable-devel mailing list
> darktable-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>


------------------------------------------------------------------------------
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to