Circular.Resize (gb.data)

Depending on the current indices of the read and write poniters, this can add empty elements or remove unread elements between the pointers. This leads to accidentally lost information and is normally not what you would expect. You should only use this functionality when the Circular shall enter a better defined state immediately after this or has entered one just before, e.g. by Reset() or Clear().

If, however, anybody reports that they need Resize() in the middle of some work, I'll fix the code. Just use the mailing list.