Hi,
On 2/7/20 11:46 PM, KOVÁCS István wrote:
Thanks for the info. Interesting. As I said, in the case above, I just quit darktable and started it again. I did see that sometimes if I have a browser open, darktable displays this error; quitting darktable, closing the browser, launching darktable again often solves the problem.
The difference in used memory is only about 100MB. I believe firefox adjusts the memory-usage based on how much you have available and the first start of darktable might get firefox to release enough for OpenCL to work on the second try.
You could look at how much memory is free/available before you start darktable, it seems to need approximately 300MB for OpenCL and half without.
Holger ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
