SimonH

QUOTE (spsuamin @ Feb 2 2009, 07:46 PM)

I like SignalExpress but it doesn't work well for multiple data acquisition tasks.

Do you have any specific feedback about situations where you were disappointed with SignalExpress? Obviously the functionality in SignalExpress can be recreated (and likely surpassed/extended for your purposes) with a little effort in LabVIEW but the goal of the product is to provide a quick, almost turn-key solution for those who primarily just want to log and view data.

*Disclaimer* - I work for NI, any feedback you (or anyone else) posts will make it back to the development team. We'd love to hear how (if?) you use SignalExpress alongside LabVIEW in your day to day work.

Thanks,

Simon

QUOTE (jdunham @ Jan 8 2009, 04:52 PM)

No, there are plenty of things the profiler won't report. I don't believe that shows global memory like queues and notifiers or stuff allocated by ActiveX nodes that you've invoked.

Good point -- the profiler isn't an exhaustive tool but it's probably worth knowing about. I suppose I use it more for performance optimization than for hunting down memory leaks.

You could also use the VI Profiler that can be found at Tools » Profile » Performance and Memory…. If you check "Profile memory usage" it will show you the memory being used by each running VI as your program runs.