Did you check if this also opens when you open a menu and leave it open (see my earlier reply)?
I'm assuming that's addressed to manu.NET.
But I did, and it did, see my earlier reply to your earlier reply. 🙂
manu.NET - it would be worth taking a look at the link tst indicated early in the thread.
The error only occurs when i launch the calendar dialog by clicking on the calendar button !
On the same VI i can ...
But what about opening and leaving open a menu, as suggseted by tst - have you tried that?
Please try and post a simple piece of code that demonstrates the problem, so it can be reproduced. Something that opens the TCP connection, uses it in a loop, and closes it again at the end while presenting the option to generate the error from the time stamp browse button. It's probably easier to construct it from scratch if your application code is complex. If the example code doesn't exhibit the problem then you will have something to compare your application and possibly locate the problem.
I should add that I'm unlikley to pick anything up until the New Year.
We are also having an issue with the timestamp control. It is sometimes causing our application to crash, but only if the browse (date time picker) button is visible.
I did some windows low level debugging and figured out that, in our case, the crash came from mesa.dll (openGL implementation) function glMultiTexCoord2d.
I believe that this function is called whenever the browse icon is repainted (If you scale up the browse button, you see that it uses quite complicated multitexturing graphics).
We are using Labview 2011 SP1.