I re-wrote the sample program /cvi/samples/easyio/ai^log.c for dataloging. The program could run well at beginning. but after about 2000s running, the timer call back intervel began to increase, and system Kernal process usage increased to 100%.

dbyan · ‎03-28-2001

Why?
I re-write it by anync-time functions, it is not better anymore. system:
Labwindow/cvi 5.0.1
DAR Card-700
NI-DAQ 6.1
Windows98
PIII-700/128M

RobertoBozzolo · ‎03-29-2001

I had a similar problem in an application of mine and it was due to a progressive allocation of memory not freed in the program. You can see if this is your situation by monitoring the amount of memory dtnamically allocated during program execution: if this value increases progressively this can at the end cause the behaviour you look in your system.

In CVI 5.0.1 you can test the amount of memory dynamically allocated by using the Dynamic Memory... item in the Run menu of the source editor window. By suspending your program you can see at the total amount of memory allocated and then resume execution and test it again some time after.

If this is true, you have to check carefully in your program and free all dynamically allocated memory after using it.
Hope this
helps
Roberto

Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?

dbyan · ‎03-29-2001

Thank you, Roberto.
I change the graph control data mode from "Retain" to "Discard", it works very well now.

LabWindows/CVI

I re-wrote the sample program /cvi/samples/easyio/ai^log.c for dataloging. The program could run well at beginning. but after about 2000s running, the timer call back intervel began to increase, and system Kernal process usage increased to 100%.

I re-wrote the sample program /cvi/samples/easyio/ai^log.c for dataloging. The program could run well at beginning. but after about 2000s running, the timer call back intervel began to increase, and system Kernal process usage increased to 100%.

Re: I re-wrote the sample program /cvi/samples/easyio/ai^log.c for dataloging. The program could run well at beginning. but after about 2000s running, the timer call back intervel began to increase, and system Kernal process usage increased to 100%.

Re: I re-wrote the sample program /cvi/samples/easyio/ai^log.c for dataloging. The program could run well at beginning. but after about 2000s running, the timer call back intervel began to increase, and system Kernal process usage increased to 100%.