FATAL ERROR (aborting debug session): Unable to allocate system resource

[bmihura]

I get the above message popping up from nowhere, at random times, after I do some serial port reads and writes.

What is this "system resource" the obscure error message speaks of?

[Wendy L]

Hello bmihura,

You usually get that error when your application or CVI runs out of memory, so it cannot allocated any additional internal memory it needs.  So I would check to make sure any memory you allocated is freed when it is no longer needed.  Also, you may want to try installing the latest runtime engine if you are using a previous version.  If you are able to isolate which function returns that error and also which version of CVI you are using, that might be more helpful in resolving this error.

Thanks.

[Graziano]

Hi!

It's quite simple, but...   you can just launch your application while Windows task Manager is running, with "performance" tab selected.  You can control memory usage.

you can also run it, checking for your application's memory usage, in "processes" tab.  Maybe it is not the best, but it may help!

Greetings.

graziano

[Captain_Jack]

For what it's worth, I was also seeing this issue when attempting to debug (or even sometimes just use) a DLL with CVI v7.1 and its latest Run-Time Engine patch 7.1.1.314. Per the suggestion in this thread, I ran the Run-Time Engine updater for v8.0 and this appears to have resolved this issue with debugging of a DLL.