08-05-2005 07:39 AM
08-08-2005 02:28 PM
Hello Rakesh,
Can you reattach the code that demonstrates the behavior? It seems to have gotten lost.
Thanks.
08-09-2005 02:24 AM
08-09-2005 06:34 PM
I had to reorganize your code a bit since I don't have your database or datasocket sources. However, I think my modified version hits all your code paths. The only leaked memory I found was being leaked in DSCallbackAlarms; at the bottom when you free up all the memory, you fail to free ChValue.
Note that you can use CVIDynamicMemoryInfo() to track the number of allocated blocks and their sizes to help find problems like these.
If you think you are seeing other leakage, please post more details indicating what you are observing.
Regards,
-alex
08-10-2005 08:38 AM
08-11-2005 03:03 AM
08-11-2005 03:30 PM
08-12-2005 05:37 AM
Hello Alex
Thanks a lot....I used your modified version and i am not finding any memory leaks but now i will investigate more my application to check for memory leak. and let you know. There is another acitivity which is making my application slower i.e. updation of rows. As you must have observed some columns like" End Alarm Date and Time", "Value" and "Status" these columns will be filled once and channel comes out from previous Alarm State. And i have separate callback DSCallbackEndAlarms which provide me necessary information. This values may not be in order unlike when i add new rows in order for new alarms. So i have to do cell by cell using SetTableCellVal. This makes my application very slow. Please advice...
If memory leak problem continue i will make application which you will be able to run without any modification but i may take some time to do so..
Hoping for your kind cooperation as before
Regards and Many Thanks
Rakesh