Anders Broman wrote:
> Well as I see it EP memory is not a problem we only use one chunk (10M)
> During the life time of a packet so memory efficency isn't a big issue.
>
> But when dealing with large files waisting +30% of the memory is not an
> option I think.
> A way to still test se_alloc() could be to let the buildbot doing fuzz
> test use canaries forinstance.
>
> I don't see that a new allocator would solve the problem, when to use
> it?
We could add a preference item which lets the user disable SE canaries.
Maybe a slider with "fast" on one end and "safe" on the other, just to
let them know what they're getting into. :)
