To avoid the use of Malloc() for every new svb a buffer is introduced in r237.
However, since the buffer has a fixed size, a buffer overflow is a possibility.
It may not be possible to flush the svb-DAG to avoid a buffer overflow, since
we compute a complete view-block at a time and it is not guaranteed that the
size of a single view-block does not excites the fixed buffer size.
A solution is to compute a single sub-view-block at a time and then guarantee
that the size of one svb does not excites the buffer size. An attempt to do
this is attached this issue, but it is a non-working draft.
Original issue reported on code.google.com by madsbk on 30 Jul 2010 at 11:56
Original issue reported on code.google.com by
madsbk
on 30 Jul 2010 at 11:56Attachments: