Desktop trace Execution toolkit memory overflow

[wideofthemark]

I have been trying to debug some possible memory leaks with desktop execution toolkit.  And what do you know - the toolkit crashes because it logs too many events! It doesn't seem to be possible to get it to log to file, or to do anything else. 

Aside from liking the irony that the toolkit that is supposed to track memory leaks has't got this sort of protection - has anyone managed to find a way around this?

(I know that this is a long running problem with this toolkit - see http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Improvements-to-the-Desktop-Execution-Trace-Toolkit/id...

JP

[Larry.C · Accepted solution]

Hi JP,

I'm sorry you are having difficulties with the Desktop Execution Trace Toolkit.

What version of the DETT have you currently got? Make sure you are using the most recent version as there have been many changes over the different version that have been released.

I noticed on the other forum post that you could alter the number of events which it caps at. Have you tried changing this setting?:

"The current implementation keeps all the traces in memory in order to keep up with the potential fast rate of events generated.  There's a setting in the TraceTool.ini file (MaxEvents=4000000) that specifies when the tool will stop tracing due to too many traces."

Kind Regards,

[wideofthemark]

Thanks for replying.  I have the version that came with lv 2011.  Is this the most recent version?

I saw the editing ini file option in the previous post, but I guess i was surprised that what seemed to be a good suggestion 2 years ago didn't seem to have been implimented.  I'll have a play around with it and see what happens.

JP

[wideofthemark]

Thanks for the advice - changing the number does stop it crashing - although it gets to the point where it becomes less and less useful if you restrict the number of events it can follow.  I would strongly NI to impliment logging properly.