Hi I am using wintoolbars 2008 v2.
Strange thing happening to me is that on first click of a button menu tool or the first drop down of a menu tool, application takes a lot of memory (>400 MB) and ultimately gives a system.OutOfMemoryException.
I tried to single out the cause by remote debugging and ultimately found that inside the toolclick event, I am passing on the control to another procedure called HandleTool(oTool as Toolbase) which processes the tool to decide what action to take. The passing of control from the event handler into the above procedure itself is taking that much time and memory. I ruled out looping error because I am using Step Into (F8 in VB) while debugging.
As I mentioned this is happening only on the first click or first dropdown. Also, this is happening only on the deployment machine. Development machine is fine!
Is this a bug ? Am I doing something wrongly ?
Thanks
Abhishek
Hi
I tried applying service release for 2008 v2. But the problem remains as it is. Also, I thought I will mention here that I am using "release" mode to build.
Customer productivity is getting badly affected. Please help !
Turns out that the Handletool procedure had references to other objects. These objects were not being instantiated but since any reference means automatic loading of corresponding dlls, that was causing the delay and memory.
When I moved the references / portion of the code to another procedure, the problem was solved.
Infragistics components were not the issue...