Am 17.09.2014 19:35, schrieb Pascal Obry: > > After a full day to rebuild my mipmap cache (40% was done): > > [mipmap_cache] serialization to > `/home/obry/.cache/darktable/mipmaps-62d87cbcad56aa2b4a21cd680776714d70e93ef6' > failed! > > Shouldn't we consider reverting the recent patches on this code? > I really support that suggestion! The original problem, which the recent code changes wanted to fix, is the handling of some really huge Tiff files - a case that can occur but which is not frequent.
Now we have for several users the situation that they cannot properly use darktable at all. Problems seem to be diverse, for some it helps to disable compression, for others the mipmap cache causes severe problems at some unpredicatable point in time. In other cases there is not even a chance to reproduce and fix. The balance between benefits of these changes and their downside is not good. Too many people rely on the current master so we cannot just leave it crashing until hopefully a solution is found. I strongly recomend to revert the changes that have led to the problem and move them into a feature branch. Only if the problem can be reproduced in this branch and a final fix is found it should be re-integrated into master. Ulrich ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
