Le 30/10/2013 11:25, johannes hanika a écrit : > there is a report on irc about a case where data was initially present
Yep, indeed the info was there at first and disappear just after entering the darkroom. I'm almost 100% sure of this. > and got zeroed out at some point. since we don't really write that stuff > into db any more it might have happened during back-syncing of the image > cache. so maybe there is a case where someone memset(0)'s the dt_image_t > and then syncs it back to the cache? that'll be very hard to debug, > could be everywhere. maybe we should just put an assertion into > dt_image_cache_write_release() and wait for crash reports..? Good idea! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
