LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Task monitor for memory leakage

I'm going crazy trying to find the cause of a memory leakage problem.

I have a LabVIEW executable running as a service on a server that read via modbus some data from a device and write results to a MSSQL database.
Somehow, at a certain point the RAM memory of the executable goes from 40 to 400MB. and it returns an error.
"system error  8: Not enough storage is available to process this command. (ODBC Driver 17 for SQL Server, C:\Windows\SysWOW64\msodbcsql17.dll)"
It is not a DB problem or a driver problem but a memory problem.
I'd like to find when and how the memory leak occur, if it happens gradually or suddenly.

So I would like to monitor, like in task manager a specific task and it's memory occupation.

 

I found something similar here
https://forums.ni.com/t5/LabVIEW/How-to-monitor-total-memory-occupied-by-a-running-project/td-p/1725...

But it uses the same application to get the task ID, I need to select the task ID from the running task like in task manger and all the memory info it returns doesn't seems to be the one I can see in the task manager...

 

I tried running the executable on my laptop and it doesn't give any problem.

 

0 Kudos
Message 1 of 5
(387 Views)

@gepponline wrote:

It is not a DB problem or a driver problem but a memory problem.


I'm not sure why you say that, since the error clearly identifies itself as coming from the ODBC driver.

 

I'm not saying that you don't have a memory issue, but I have personally never seen this error and 400 MB for a process is usually not a reason to see an out of memory error.

 

I would suggest digging through some of these: https://www.google.com/search?q=%22sql+server%22+%22not+enough+storage+is+available+to+process+this+...


___________________
Try to take over the world!
0 Kudos
Message 2 of 5
(348 Views)

Maybe this?

windows 7 - Not enough storage is available to process this command - Server Fault

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 5
(338 Views)
No, System error 8 is a generic WIndows error and it can occur with different actions. The problem is that at a certain pint It cannot open the ODBC driver as it do some seconds before due to a lack of memory. It is not the DB 'cause the DB is not yet involved during the call of the dll.
The problem is not the 400mb by itself, the problem is that the executable should be 40mb in RAM but somehow, at some point it grows to 400 and more that is a symptom that something unexpected is happened.
0 Kudos
Message 4 of 5
(322 Views)
I'll try this way 😉
0 Kudos
Message 5 of 5
(322 Views)