Thorsten Froehlich <thorsten [at] trf de> wrote:
> This is not a bug, it is an internal buffer that trades speed for memory
> limits. It should not be needed, but a better solution is complicated and
> time intensive to implement.
Could the reaching this limit be detected and a better error message be
shown? Now it looks just like a regular "out of memory" error while it
really isn't, as it's a particular special case. Perhaps a more informative
message could be better in this situation.
--
- Warp
Post a reply to this message
|