Interesting (and hard to reproduce) bug:
The UI thread is using BeginUpdate and EndUpdate to fire change events as batch to the grid. While EndUpdate is called an InvalidOperationException occurres somewhere between GridControlBase::EndUpdate and NativeWindow::Callback, and the application starts to leak memory. It''s an "Object in Use" exception. Turns out that on a separate thread the Finalizer thread of the GC calls SafeNativeMethods::GdipDeleteFontFamily and gets stuck on this exception. No further GC is carried out. The app continues to work on some machines and not works on others but memory is no longer released.
We checked our code and really most of the operations are within the grid so I post this here in case somebody has seen this behavior before.
ADAdministrator Syncfusion Team February 3, 2004 03:45 PM
What version of our grid are you using? In versions earlier than 188.8.131.52, there were threading issues that could generate such a problem.
Are you making sure all calls into the grid code are being protected with grid.InvokeRequired checks?
JLJens LippmannFebruary 4, 2004 08:03 AM
We are using 184.108.40.206 and I''m currently checking all execution threads to make sure they check InvokeRequired.
What''s the upgrade path to 220.127.116.11.?
>What version of our grid are you using? In versions earlier than 18.104.22.168, there were threading issues that could generate such a problem.
>Are you making sure all calls into the grid code are being protected with grid.InvokeRequired checks?
ADAdministrator Syncfusion Team February 4, 2004 09:40 AM
You can download 22.214.171.124 from your support home page in Direct Trac. If you have invalid resx problems after updating, you can use the tool from this kb to convert your resx files.