I have fixed one obiviously wrong thing in
https://github.com/darktable-org/darktable/commit/e1b27201024c56747e81c46b9594290f20e1899b
It was found by Pascal Obry.
So now code actually reflects comment.
// last resort mem alloc for dead images. sizeof(dt_mipmap_buffer_dsc) +
dead image pixels (8x8)
// __m128 type for sse alignment.
-static __m128 dt_mipmap_cache_static_dead_image[1 + 64];
+static __m128 dt_mipmap_cache_static_dead_image[sizeof(struct
dt_mipmap_buffer_dsc)/sizeof(__m128) + 64];
That *might* help with the issue, but i expect that there is more.
On Mon, Sep 15, 2014 at 11:17 PM, Ulrich Pegelow <
[email protected]> wrote:
> Am 15.09.2014 21:10, schrieb Roman Lebedev:
> > Hi.
> >
> > As far as i am aware, struct dt_mipmap_buffer_dsc is *not* being stored
> > in on-disk mipmap cache.
> >
> >
> > Aside from that, so far i have no more ideas.
> >
>
> If you can't fix it you need to revert the one or two commits in
> question. You just can't let it as it is.
>
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
