Not enough memory error when passing an array to a chart

Hello.
I am trying to pass some data from a reading loop to a display loop using queues and charts.
In order to save on redraws I am reading the queue just once a while, flush it and pass the resulting array to the Chart. It is actually an array with clusters of three values.
Everything works fine unitl I actualy want to display the chart. I can pass the data and see it using an indicator without any problems.
When I wire the data to the chart it randomly shows : "not enough memory to complete this operation"
The fact is the array being passed to the chart is of random size.
The queue size is good for about 20 min. Labview shows an error after a few seconds. After clicking ok it prints out the results correctly and then a second or two later same error.
What am I missing here? Thanks
LV 2012 f3 I7 2.4GHz 16GB RAM
Attachments:
TestChart.vi ‏17 KB

Not sure if it helps or not but here is the error.
I put about 200 elements/s in the queue. That is why instead of reading it 200/s I just want it to read it once a while.
I am not sure what is a bigger burden:copying one 500 elements array twice a second or 200/s and 200 calls to the Queue.
The max size of the queue is not important here. I can set it to something more reasonable and will get the same error.
What will happen to my CPU usage if I put the Chart in the for loop and make 500 call to it? And then half a second later another 500 calls?
As I said at this point I do not know how much history I need or not but all I want is to be able to see a few s of it. If I loose the rest it is ok for now.
Lets says that all I care is to see it close to real time with a history of 5s. It would mean the queue buffer size of 1000.
Back to the main problem: why do I see the memory error window when I know clearly that I have plenty of memory left.
Attachments:
Error.jpg ‏18 KB

Similar Messages

P800 "Not Enough Memory" error when trying to use Contacts

Now even after I reset my P800 from iSync I get this 'Not enough memory' error when I try to use my contact list.
This is getting really frustrating! I want to downgrade...

I suspect it's the feed as I've just tried it and the latest episode fails. Try contacting the Podcast's producer/publisher to let them know, since they may not. From your linked page, click on their name and follow that to their website, where you should find contact details.
By the way, even if the problem is with iTunes, it's still down to the producer/publisher to rectify it, which is why I suggest you contact them
Phil

Not enough memory error when attempting export

Whenever I try exporting an 111Mb freehand file to a
pdf/gif/jpg/bmp/png I get a not enough memory error unless I set
the image quality to be very low. I am using Freehand MX 11.0.2 for
Windows. Does anyone know if there is asetting somewhere to prevent
this from happening?

> Whenever I try exporting an 111Mb freehand file to a
pdf/gif/jpg/bmp/png I get
> a not enough memory error unless I set the image quality
to be very low. I am
> using Freehand MX 11.0.2 for Windows. Does anyone know
if there is asetting
> somewhere to prevent this from happening?
Export and Import filters in FreeHand are not very good and
exporting large document as bitmap just can't be done. If you use
raster effects with high resolution export fails sooner or later or
at least takes even days.
To create a bitmap image I usually make pdf with Acrobat (the
only reliable way) and open it in Photoshop where you can define
dimensions, color space, etc. Photoshop opens some FreeHand created
eps and ai files too. Also Acrobat can export bitmap files.
Jukka

Not Enough Memory error when updating a podcast??

I am having difficulties with the Radio GoDaddy podcast. Last week when I subscribed, I entered the URL and iTunes downloaded the latest episode, no problem. They release a new episode every Wednesday. So this morning I clicked the Update button and I was presented with an error message in iTunes:
“There was a problem downloading http://radiogodaddy.com/feed. There is not enough memory available. Please check that the URL is correct and the connection to the network is active and try again.”
I’ve got 1.5 GB physical RAM and over 75 GB of free space on my HDD. The other two podcasts I subscribe to, both are from NPR, seem to work just fine. This would lead me to believe that it was an issue with the GoDaddy podcast. Has anyone else had this problem?

Marking this question as answered. The problem has since resolved itself. Problem with the podcast feed.

"not enough memory" error when attempting to get some podcast episodes

I subscribe to several podcasts. All but one seem to be working perfectly. Here's the url of the one I'm having trouble with:
http://feeds.feedburner.com/KBCAudio
Here's the problem:
All episodes appear as they should. However, some of the episides WILL download when I select "Get" and some WILL NOT. Those that will not yield the following error message:
"There is a problem dowloading {episode name}. There is not enough memory available. Please check that the URL is correct and the connection to the network is active and try again."
Any ideas how to resolve this? I've tried:
1. Deleting old files.
2. Deleting and re-subscribing to the feed.
Is this a problem with iTunes or a problem with the feed?

I suspect it's the feed as I've just tried it and the latest episode fails. Try contacting the Podcast's producer/publisher to let them know, since they may not. From your linked page, click on their name and follow that to their website, where you should find contact details.
By the way, even if the problem is with iTunes, it's still down to the producer/publisher to rectify it, which is why I suggest you contact them
Phil

Why "not enough memory" error when saving edited files?

I've been editing photos from one folder and saving them to another, hundreds of them. Suddenly when I tried to open Photoshop Elements 9 from the raw editor I got an error that says "could not complete the command because there is not enough memory." I have noticed that when I go back and open a photo from the first file that I've already edited, the changes are applied to that file, even though I saved the edited file into the second folder. What can I do? I don't really want the photos in the first folder edited, just the ones in the second, and I don't need to store all my changes in memory. I still have hundreds to edit.

Is there a simple way to get back to my original RAW files in folder 1, without the edits that have been made applied to them?
The simplest way is to change your mindset, and say ... hey, no problem, that's the way the PSE RAW editor works, I will leave things as they are.
What could be simpler, you basically have to do nothing?
(And by the way, I say again that your original RAWs have NOT been changed in any way).

Not enough memory error when disconnecting device on a virtual com port

I maintain a large application that collects data from many data source channels (using coustom hardware read thru a conventional COM port) and I am adding a GPS data source on a USB port using a virtual COM port driver. The application runs 24/7/365 and works well including the GPS data, if undisturbed. However, the application needs to tolerate a physical disconnect and reconnect of the GPS device without user intervention. When I disconnect the GPS, the application becomes unresponsive most of the time (the mouse responds and other programs that are open on the desktop work fine). I abstracted the serial code and made a separate vi (below) for testing. When I disconnect the GPS from the COM port, I get a "Not enough memory to complete this operation" message 9 out of 10 times and the vi is unresponsive until I clear the error message (the tenth time it continues working). I built the vi this way to collect data continuously. I suspect that this is the problem with the full app but I don't see the Not enough memory message there and therefore the full app does not respond and must be terminated via Task Manager. The full app runs full screen mode.
The LV app runs on Windows XP and LabView 7.0 (the client doesn't want to upgrade).
I have tried probing the error message lines at all points in the vi but they don't show anything when the 'Not enough memory' message occurs (they show the expected device not found error after clearing the error message).
Any suggestions would be greatly appreciated,
Mel
Still learning LV......
Please post any code suggestions as graphics as I don't have access to any version of LabView newer than 7.0.
Attachments:
SerialPortRead.png ‏22 KB

Jeff·Þ·Bohrer wrote:
First, there likley WAS human intervention that caused the GPS device to be removed. That wont happen when you lock the device inside a cabinet with the rest of the test system. Physical access control first! If someone goes and mucks with your experiment setup while its running, that's a "poor Labratory procedure" not a "new software requirement"
I think he was meaning to say without user intervention on the software side.
I have seen odd behavior if you disconnect from a com port whilst LV still has the port open. There are a couple things I myself woud try, being the experimenting type that I am. Perhaps setting up a com port check to see if it has a valid connection before polling for data. If not then a blank case or some other generic code.
The issue with this would be if it became disconnected while LV was polling data. Hard to get around this condition. Is there a way that the cause of the of the connect/disconnect (whether human or otherwise) could be set up so that a signal can be sent to the controlling system (pre-disconnect and post-connect) to trigger an event to handle the software side? A simple signal switch or something. Just thinking out loud. Withoug knowing all the particulars, it's hard to make detailed recommendations.
Doug
"My only wish is that I am capable of learning each and every day until my last breath."

Need Help with "Not Enough Memory Error" when running executable (is my VI reworkable?)

When I started making this VI, I had no clue about proper VI flow, sub-VI usuage, and much more I'm sure.
The VI is a program that outputs a 0-5V digiatl signal to a relay board (to actuate an air cylinder) and monitors 4 input voltages (lets say from a pressure transducer) . The program would then shut down the corresponding output channel if a pressure threshold is not met.
Surprissingly for my first LV program, The VI functions "fine" (the quotes are because I know my programming flow is a mess and probably not efficient) unitl I reach a given cycle count or time elasped, at which time my VI blows up and I receive an error for "not enough memory to complete operatoin".
I am wondering if there is a simple DAQmx (or something else) command misplaced or missing that would solve this issue. When I started making this VI I had a poor top down design layout, or lack of one. I would like to believe I have learned a lot from making this program with no LV training and if I were to do it again I would utilize state machines and sub VI's more. However, with time not on my side and LV not a priority in my job I would like to know if this VI is reworkable..?
I should also mention that this program is being run as an executable on a laptop without the full LV development software. I dont know if the executable creation process could have left to this problem either...
Attached is LV version 10 and 11
Thanks for the help
Attachments:
LCT_DAQmx v11.0.vi ‏173 KB
LCT_DAQmx.vi ‏135 KB

There are some things you can probabaly do fairly easily. Four of the inner while loops appear to be very similar. You could probably make a subVI from one of them and reuse the code. Some of the shift registers are initialized and some are not. I suspect that this is an error, although I did not look closely enough to determine which way is intended. Read up on reentrancy. You may need that for the subVI.
The outer loop, if it is needed at all should be stopped by a front panel boolean, not by the Abort button. Someone on the Forums has suggested that using the Abort button to stop a VI is like using a tree to stop a car - it works but may have undesirable consequences!
Re-initializing the DAQ tasks and clearing them on each iteration is not very effficient, is slow, and may lead to problems.
The inner inner while loops (inside On Cycle and Off Cycle) are very similar, differing mostly in the data written. Perhaps you only need Idle and Run (with Data as a parameter). The inner inner loops might be combined with the outer loops with some change in the way the timing is handled.
You Dequeue in two places in each loop. There is no data dependency bewteen the two Dequeue functions, meaning that you cannot be sure which will execute first. Also, none of the Dequeues has a timeout set. They will wait forever if no data is available. Queues should not usually be read in more than one location to avoid loss of data or confusion about which data came first.
Lynn

"Not Enough Memory" Error when programming Keithley 2400 using LabView 6i

I'm trying to use LabView 6i drivers to control a keithley 2400 via GPIB interface. Most of the drivers work fine but the high level operations such as a the sweep functions or even functions that perform a single measurement gives a "Not enough memory" driver error. What doesn't have enough memory? A single measurement can't overload the PC's or Keithley's memory buffer so why am I getting the error?
Thanks for any help you can offer...
Evan

Evan,
That's not a LabVIEW, GPIB, or NI-VISA error code - that error is generated by the instrument driver. I went ahead and downloaded this driver from keithley.com to take a look at this Perform DC VI.vi function's source. But unfortunately, the heart of the Perform DC VI function is a "Call Library Node" call to a keithley DLL, so that is a black box. Also, no c-source included that I could find, so I could not look at that either. And since I don't have a Keithley 2400 to play with, that brings me to the end of the rope on my system.
A couple of more things you could try, however, since you actually have the instrument.
(1) Definately build a simple VI to eliminate other aspects of your program. In this case, the most simple
VI would be an Init, Perform DC VI.vi, and then a close. Make sure this simple program reproduces the error. If it doesn't, then the problem is likely introduced in your code, not the driver.
(2) If #1 reproduces the problem, then check that you have all the driver pre-requisites correct (ie, that NI-VISA is installed, that the GPIB board is working properly, etc).
(3) If #1 and #2 do not result in any discoveries, then you will have to enter the black box of that DLL. Primary method to do that, to be honest, is to contact Keithley and ask for help, since they developed the driver. Second method is to use our NI-SPY utility, which can capture all calls to VISA drivers, (since this is a VXIpnp driver, it should be fundamentally using VISA within the DLL). Within NI-SPY, you will be able to see the individual function calls, and which ones are returning errors. That may help point in the right direction.
Regards,
Greg Caesar
National Instruments
Applications Engineer

A FIX for error message: When I try to open Snood (it's a game) I get this message. Not enough memory {Error # :: 0, in sound.cp@line 101 Can you help?

After years of playing Snood, w/o problems, I started getting this error message, on my iMac, OS 10.5.8,
with 4 GB of memory when opening Snood: Not enough memory {Error # :: 0, in sound.cp@line 101
My MacBook Pro w. Mac OS 10.6.8 did not have this problem.
Initially I thought that Snood raised its minimum requirement to Mac OS 10.6.
I had several correspondences with Snood. Their tech support is great. Quick and thorough responses.
They thought the issue was in Mac's system preferences/ Sound. It was.
I didn't realize that my sound input and output devices were gone.
The fix was resetting the PRAM. I found this advice on MacFixIt.com.
MacFixIt help with volume: http://reviews.cnet.com/8301-13727_7-10415659-263.html
Resetting the PRAM is on Apple support: http://support.apple.com/kb/HT1379
My sound (music!) is back, along with Snood. So glad I reset the PRAM before reinstalling the OS software!
Thank you to Snood, MacFixIt and Apple.
Happy new year all!

Good work, nice post/tip, thanks!

Troubleshoot not enough memory error

I am getting a not enough memory error, and while there are tons of posts about this on the forums, I had some additional questions. First, I have two cRIOs, and think the error may have been thrown by one of them. Is this even possible though? I'm trying to narrow down which exe the error may be in. Second, does anyone have an order of steps they take when they get these errors in order to troubleshoot them?
CLA, LabVIEW Versions 2010-2013
Solved!
Go to Solution.

Found the REAL problem! I was not reading my header correctly, this resulted in type casting the wrong bytes of data. Every now and then I would be type casting bytes of data that when type casted from a string to a I32 resulted in a number around 17 million. I am assuming the TCP read tries to malloc this memory (or new if its c++ ) and was unable to do so. That's why I got the not enough memory error. When I started reading my TCP bytes correctly, the error went away.
CLA, LabVIEW Versions 2010-2013

Not enough memory message when opening excel and powerpoint

I am running Mac OS X version 10.5.8. I installed Microsoft Office 2008 for Mac about a year ago and was running it without any trouble until about 3 months ago. I can still open Word, but receive a 'not enough memory' message when I try to open Excel or Powerpoint. Has anyone else encountered this problem and does anyone know how to fix it? Thanks

Yes I have and I think that's when the problem occurred. I've just read another post from someone who was having the same problem. Apparently the solution is just to keep hitting the escape button every time the error message pops up and eventually the application opens! Not very high tech, but I'll give it a go and let you know how I get on.

Not Enough Memory Error During Update

There is a new update for Ovi Maps 3.04 today. I tried to install it using the Software Update app and kept getting a not enough memory error. I even tried closing all programs, deleted a few apps I no longer use and restared my phone. Still I get the error.
Any suggestions?
<\
\>tuntman

Have a read of this thread as i suffered the same problem:
/t5/Maps-Navigation-and-GPS/E52-error-when-installing-ovimaps/m-p/751192#M27026

Export several Fuji X-Trans Files got "Not Enough Memory" Error

When I tried to export several (say 15) Fuji X-Trans files at the same time, I got a "Not Enough Memory" Error. This problem only occurred after after upgrading to Lightroom 4.4. I can now only export a few (3-5) X-Trans files at the same time. Does anyone encounter this problem and know how to fix it?
I am using Windows 7 32-bit with 4GB memory, SSD System drive, and Radeon 7700 Graphics card. For Virtual memory, I set "no paging file" on C drive and "system managed size" on another SSD drive.
Thanks in advance.
Wilson

One might expect an Export function is single-threaded so the number of files exported wouldn’t matter, but perhaps if you are very close to the limit, memory fragmentation comes into play, where LR is requiring contiguous blocks and there aren’t any big enough. It’s probably time to upgrade to a 64-bit Windows system and start getting used to the Metro interface which isn’t bad as long as your frequently-used programs have tiles on the first screen.
Go to Help / System Info… and see how much memory LR has available. On my 32-bit system with 4GB of RAM installed LR only has 716.8MB available which is typical for 32-bit Windows applications:
Built-in memory: 3327.0 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 160.5 MB (22.3%)
Virtual memory used by Lightroom: 160.8 MB
Memory cache size: 33.2 MB
You could change your VM settings to allocate a multi-gigabyte minimum pagefile size to see if it makes any difference, in case LR is waiting on the VMM to allocate more and then gives up, but I’d expect LR is requiring actual RAM for processing images, not VM which is much , much slower.

INTERNAL ERROR & NOT ENOUGH MEMORY error

Somehow 4 gig of memory is not enough!!
I am on Win Vista ultimate. intel Core 2 Duo 2.66 4 BG of
Ram.
And I'm working on a local hard drive with fat all else
running
I constantly get "Internal Error occurred...could not complete
request"
particularly alarming if that request was to save!!!!. I have
been using the 'fireworks autobackup" air app...save me heaps of
time...But its taking longer and longer to save the file as I work
on it.
If i save every 10 minutes !!!! its taking 1:20 to save..this
is 12% of my time...FW STILL sucks memory somehow..
any one with solution to this!!!???
Ive also had the "not enough memory" error a few times..In
which every thing done on the file is lost since last it was
opened...whether I saved it a million times or not. I've started
making copy backups and restarting FW every few hours to purge the
memory..but this sucks. This memory leak seemed to be mostly gone
in CS3 according to others so assumed CS4 had it sorted

One of our users is running across a similar issue using the
pen tool. A file that's 3000x2000 having sections cut out using the
pen tool will spike FW up to 2gig of used ram. Eventually the
Internal Error messages will start but, you can still trace your
path. The issue is it pops up every time you click a new point. The
only current work around I have for the user is to shrink the file
or decrease the dpi. Has anyone else run across this?
Specs
XP SP3
Core2 3.0ghz
4 gig ram.

Not enough memory error when passing an array to a chart

Similar Messages

Maybe you are looking for