Win 7 x64
Most recent wx.Net built (32-bit) against 2.8.12 wxWidgets (Unicode Release & Unicode Debug, 32-bit)
Create a virtual table from GridTableBase.
Run the application.
Simply scrolling up and down, changing the displayed area on the screen leads to massive memory growth that never appears to be reclaimed. I've been able to get the application up to 100 MB in a few minutes of scrolling.
I've run it through a debug build of the wx-c library with WXNET_LOG_MEM and did not see what appeared to be any significant memory leaks in the file.
Attached is the sample program.