Memory leak in IMAQ Write PNG File

Hi,
I have a labview program that I'm using to do Speckle Patter Interferometry - it takes an image, takes a second image after some time, then subtracts the original image from the first and saves the subtraction. The process reveals fringes on an object deformed on wavelength scales.
The problem currently is that the program seems to have a memory leak. When I run the program, the amount of memory being used (according to Windows Task Manager) just keeps going up and up then after about 20 minutes, it crashes with the error:
Error 1074396159
Not enough memory for required operation
The error is normally when the file tries to write the png file - though that is the part of the program that takes the most time so it could just be coincidence that it happens at this point in the loop.
I've tried using the labview profiler (output attached), but can't see a particular VI that is using an abhorrent amount of memory.
I'm fairly stuck for ideas - I've attached a library with the VI and its sub VIs - if anyone would be so kind as to give me a hand I'd be very much appreciative. I realise that my code is quiet messy - this is my first attempt at labview (albeit quite a long way into my first attempt) so any suggestions would be much appreciated also.
Thanks
Sam
Attachments:
ESPI.llb ‏556 KB
memory_profile.txt ‏237 KB

Hi Sam,
I'm glad to hear that you managed to fix the problem in your code. I have had a look at the code you posted and I have a few suggestions on how you can improve it.
In your code you haven't included the error clusters from the VIs. Most sub VI functions included in LabVIEW will have an Error In and Error Out port that will transfer any error information through the VI. If an error does occur in the code, the error will be passed through the rest of the VI. If a sub VI or function receives an error at its error in port the VI will not execute and the error will pass through until it reaches the end of the VI. At the end of a the VI there needs to be an Error Handler function to display the error information. As error information flows through the VI the same as the data, using error clusters is a good way to determine the flow of data through a VI. This is a good way to determine the data flow through the VI as opposed to Sequence Structures which should be used in moderation.
I have taken a segment of you code and made some minor modifications to demonstrate how error clusters can be used (see screenshot below).
Error clusters can be implemented into any logic for the stop condition of a while loop. The Unbundle by Name using the Status option can be used in conjunction with the error cluster to produce a boolean output depending on if an error has occurred. If an error does occur, the function will produce a true and if an error does not occur it will produce a false. The error cluster can also be expanded by hovering the mouse over the top or bottom of the function and dragging the grey box up or down. This is useful for when you want to produce multiple outputs from the same data, such as the histogram data in your VI.
Another thing I noticed in you code was some redundant logic. You had set the Stop button default on your front panel to true, which meant that an inverter had to be used to stop the first while loop and the stop condition in the last while loop had been changed to Continue if True. If you had kept the stop button default to False and the stop condition of the last while loop to Stop if True, the inverter on the first while loop would not be needed. This however is only a small issue but its something you could keep in mind when writing other code.
Hopefully these suggestions will help you to further develop you LabVIEW code. I understand that implementing these suggestions into you current code could be an issue due to the size of it, but they are good features to consider when developing any code in the future.
If there is anything you are unsure of please do not hesitate to post any questions. I will be more than happy to assist you.
Kind Regards
Jason W.
Applications Engineer
National Instruments UK & Ireland

Similar Messages

IMAQ Write JPEG File doesn't save color

Hi, I'm writing an 8 bit image to file. If I save it as bmp (using "IMAQ Write BMP.vi") File then color data is saved. If I save it as Jpeg using "IMAQ Write JPEG File", then I only get grayscale. I have attached a demonstration. There appears to be a bug in the IMAQ vi.
Attachments:
ni_demo.llb ‏203 KB

At IMAQ create.vi you need to specify RGB image type. You are actually using 8 bit, that is a grayscale type.
Attachments:
ni_demo.llb ‏203 KB

I am experiencing a memory leak when I write to a file in a loop.

I am conducting a cycling test, each cycle represents about 48k of memory. I collect a selectable number of cycles into a shift register. When the chosen number of cycles is reached, I write the data to text files and then clear out the shift register. Unfortunately, I do not free up any memory space when this happens. I have been able to isolate the memory leak to the file writing function. I thought I was closing the reference when I closed the file, but apparently that is not happening. What space I free up by clearing the buffer, is cancelled by the memory required to make a reference to the file (I am guessing). This is all happening in a loop that must run as many as 500,000 times. Ideally, I
would like to write as many as 1500 records at a time. At this point the memory leak makes this almost impossible. I have ordered some more memory, but I would rather plug the leak. I have read that LabView leaves a reference open to the file even after the file is closed. What can I do to clear the memory used up by leaving the reference open? Any insights would be very appreciated.

The behaviour you describe is strange. Something to try: Open a refernce to the file one time before entering the loop, then inside the loop use that reference to do all the writing. Finally close the reference when the loop completes.If this doesn't work, post your code in 6.0 format and I'll be glad to look at it.Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Memory leak in AudioServicesCreateSystemSoundID with sound files

hi !
Instruments indicates a 64Ko memory leak in "AudioServicesCreateSystemSoundID" when I use a sound that I have created with GBand / iTunes. When I use the sound file "tap.aif" from the "sysSound" sample, there is no memory leak.
What's wrong with my audio file ?
It's a AIFF file, 95Ko, 8 bit mono 22Khz @ 176kbps.
thanks...

appFile = [ [ NSBundle mainBundle ] pathForResource : _filename ofType : _extension ];
FileUrl = [ NSURL fileURLWithPath: appFile ];
if ( AudioServicesCreateSystemSoundID( ( CFURLRef ) FileUrl, &soundID ) != kAudioServicesNoError )
return false;
I don't think the code is wrong because when I change the name of the sound in '_filename', there is no leak.
I haven't found in the documentation the audio file properties ( 8/16 bits, ... ) supported by 'AudioServicesCreateSystemSoundID'.
The code is for iPhone.

IMAQ Write JPEG File Error

Hi,
I am trying to save the image file captured by a camera (.tiff) to JPEG file, but it came up with an error. Can anyone tell me how to fix this issue?
The sample VI and the TIFF image file are attached. Thanks a lot.
Jane
Solved!
Go to Solution.
Attachments:
SaveJPEG.vi ‏47 KB
SaveJPEG.vi ‏47 KB
IR_Image.zip ‏443 KB

The VI "IMAQ Dispose" is not used immediately after creating the image with the VI "IMAQ Create" and is closing a session you will process later, you must also change the location at which to save the image, because to the location "C: \" and "C: \ temp \" often generates problems with operating system permissions.
Regards.
Jonathan Cruz
CHALLENGER
K U D O S __ B I E N V E N I D O S

[SOLVED] ffmpeg 1:1.0.1-1 memory leak? it was the file nevermind

Running devede with ffmpeg and my memory usage with 1:1.0.1-1 went from about 1.29 GB to 18 GB while encoding a film. Thought it may be my setup so I downgraded ffmpeg to try a test and see and sure enough no large memory needed (about 2.19 GB at max). Back to normal. Can anyone else verify this? I searched on the bug tracker and didn't see anything posted. Is there something new ffmpeg does that requires more space?
Edit: Nope. It was the file I was working on. Should have tried another file I guess. It is a little disturbing that a video encode could do this but nonetheless it was an issue on my end.
Mod: Please throw this post in the trash if you want.
Last edited by dodo3773 (2013-01-28 00:56:55)

hjorthboggild wrote:Sunnemer, one more question for you: Can you have the Subversion package excisting on your system when using Eclipse and SVN (with the JavaSVN option)
I've installed subversion and eclipse via pacman, the subclipse-plugin via the eclipse-update-manager. I set up an local repository and where able connecting my running svnserve without any problem. If i remember correctly JavaSVN doesn't support accessing the repository with file://path/to/repository/project.
Set-up steps:
1. edit /etc/conf.d/svnserve to set the repository root (-r /path/to/repository)
2a. svnadmin create add /path/to/my/repository/root/project
2b. edit /path/to/my/repository/root/project/conf/*
3. svn co svn://localhost/project
4. create some files and add them to your repository
svn add filenames
5. svn commit
How did you set up your subversion repository? Have you ever tried to checkout an existing project with:
svn co svn://localhost/my/repository
Maybe there is something wrong with you server configuration. Have a look at http://svnbook.red-bean.com/ .
Greets
Sunnemer

Memory Leak? (Update)

Thanks for all the responses for this problem. Here is what I've come
up with so far. I believe I have found the culprit.
1) First, I used the LabVIEW VI profiler with memory tracking enabled.
This didn't show what VI was hogging the memory, so it didn't help. It
reported only 10M of memory was being used, when Windows NT reported
110M in use by LabVIEW.
2) VI references had been mentioned as the possible culprit if the
references had not been closed. I then opened a VI reference at the
beginning of the program, used these references throughout the loop, and
then closed them at the end of the loop. Result: still had a memory
leak.
3) After some troubleshooting, I started deleting some sub-VIs out of
my program to see when
the memory was freed. I thought I could isolate
which VI was hogging the memory. This seemed to have worked, because
I've done it twice, deleting different VIs up to a point, and when I
delete one of them out of the diagram, the memory is freed. This is
what I'll explain below.
Every iteration of the loop, the front panel is converted to a .png file
and saved to the drive for output across the network to any browser
which has connected. Using the LabVIEW/vi.lib/utility/printvi.llb/Get
Panel Image.VI, the front panel can be changed into a .png format. The
next step is where the problem lies. A Java applet is looking for a png
file to download to a browser when a request is made. Therefore, the
panel image which has just been made needs to be saved to a file. The
Graphics & Sound -> Graphics Formats -> Write PNG file.VI is used for
this. This is the VI which is causing the problem. Upon looking at the
VI, it just calls a CIN. Therefore, I'm not sure how to find out why it
is
hogging the memory. If I delete this VI, and I don't save the front
panel to a png file (but I do convert it to png format), I don't have
the memory leak.
Any ideas?
Mark
Sent via Deja.com http://www.deja.com/
Before you buy.

I wish I could update to LV 6i, but I can't now. I'm stuck with 5.1.1
for now. I don't know how I could "legally" get the .dll and png write
VI from 6.
Mark
In article <[email protected]>,
"news.t-online.de" wrote:
> Hi Mark,
>
> you are right. It looks like lvpng.dll is causing the problem.
>
> Are you able to switch to LabVIEW6? The lvpng.dll has been changed
> and I didn't see the memory leak here. You can also try to use only
the
> Write PNG File.VI and/or lvpng.dll shipped with labview 6 instead of
> porting the complete application to labview 6.
>
> Martin
>
> --
> Martin Henz Systemtechnik
> Dipl. Ing. (FH) Martin Henz
> Walchensee Str. 3
> 70378 Stuttgart
> Tel. ++49-711-5302605
> Fax ++49-711-5058649
> http://www.mhst.de
> schrieb im Newsbeitrag
news:[email protected]...
> > Thanks for all the responses for this problem. Here is what I've
come
> > up with so far. I believe I have found the culprit.
> >
> > 1) First, I used the LabVIEW VI profiler with memory tracking
enabled.
> > This didn't show what VI was hogging the memory, so it didn't help.
It
> > reported only 10M of memory was being used, when Windows NT reported
> > 110M in use by LabVIEW.
> >
> > 2) VI references had been mentioned as the possible culprit if the
> > references had not been closed. I then opened a VI reference at the
> > beginning of the program, used these references throughout the loop,
and
> > then closed them at the end of the loop. Result: still had a memory
> > leak.
> >
> > 3) After some troubleshooting, I started deleting some sub-VIs out
of
> > my program to see when the memory was freed. I thought I could
isolate
> > which VI was hogging the memory. This seemed to have worked,
because
> > I've done it twice, deleting different VIs up to a point, and when I
> > delete one of them out of the diagram, the memory is freed. This is
> > what I'll explain below.
> >
> > Every iteration of the loop, the front panel is converted to a .png
file
> > and saved to the drive for output across the network to any browser
> > which has connected. Using the
LabVIEW/vi.lib/utility/printvi.llb/Get
> > Panel Image.VI, the front panel can be changed into a .png format.
The
> > next step is where the problem lies. A Java applet is looking for a
png
> > file to download to a browser when a request is made. Therefore,
the
> > panel image which has just been made needs to be saved to a file.
The
> > Graphics & Sound -> Graphics Formats -> Write PNG file.VI is used
for
> > this. This is the VI which is causing the problem. Upon looking at
the
> > VI, it just calls a CIN. Therefore, I'm not sure how to find out
why it
> > is hogging the memory. If I delete this VI, and I don't save the
front
> > panel to a png file (but I do convert it to png format), I don't
have
> > the memory leak.
> >
> > Any ideas?
> >
> > Mark
> >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.

How to read and write Png and jpeg with Alpha

Hi
I have trouble reading and writeing PNG and JPEGs that have an alpha channel (for transparency).
Reading works, if i use Toolkit.getImage() method, but works NOT if i use ImageIO.read() method.
Writing does NOT work using ImageIO.write()method. Instead i got a "java.lang.UnsupportedOperationException: Unsupported write variant!"
See Test class and commandline output below:
/****************START*****************************/
package de.multivisual.bodo.test;
import java.awt.*;
import java.awt.image.*;
import java.io.File;
import java.net.URL;
import java.util.Iterator;
import javax.imageio.*;
import javax.imageio.metadata.IIOMetadata;
import javax.imageio.stream.ImageInputStream;
import javax.imageio.stream.ImageOutputStream;
public class AlphaChannelTest implements ImageObserver {
Toolkit toolkit;
Image img;
public AlphaChannelTest() {
    super();
    toolkit = Toolkit.getDefaultToolkit();
    URL url =
      AlphaChannelTest.class.getResource(
        "/de/multivisual/bodo/test/" + "alphatest.png");
    img = toolkit.getImage(url);
    try {
      ImageInputStream imageInput =
        ImageIO.createImageInputStream(url.openStream());
      Iterator it = ImageIO.getImageReaders(imageInput);
      ImageReader reader = null;
      while (it.hasNext()) {
        reader = (ImageReader) it.next();
        System.out.println(reader.toString());
      reader.setInput(imageInput);
      ImageReadParam param = reader.getDefaultReadParam();
      BufferedImage bimg = reader.read(0, param);
      SampleModel samMod = bimg.getSampleModel();
      ColorModel colMod =       bimg.getColorModel();
      String[] propNames = bimg.getPropertyNames();
      IIOMetadata meta = reader.getImageMetadata(0);
      System.err.println("\n*****test image that was read using new Jdk 1.4 ImageIO.read() method");
      alphaTest(bimg);
    } catch (Exception e) {
      //e.printStackTrace();
    if (img != null)
      toolkit.prepareImage(img, -1, -1, this);
    try {
      synchronized (this) {
        System.out.println("wait");
        this.wait();
    } catch (Exception e) {
      e.printStackTrace();
    System.out.println("end");
public void alphaTest(BufferedImage bi) {
    Raster raster = bi.getData();
    float[] sample = null;
    System.out.println("raster :");
    for (int y = 0; y < raster.getHeight(); y++) {
      for (int x = 0; x < raster.getWidth(); x++) {
        sample = raster.getPixel(x, y, sample);
        System.out.print("(");
        for (int i = 0; i < sample.length; i++) {
          System.out.print(":" + sample);
System.out.print(")");
System.out.println();
Raster araster = bi.getAlphaRaster();
if (araster == null){
     System.err.println("there is no Alpha channel!!!!!!!!!");
     return ;
} else {
     System.out.println("Alpha channel found !");
float[] asample = null;
System.out.println("raster alpha:");
for (int y = 0; y < araster.getHeight(); y++) {
for (int x = 0; x < araster.getWidth(); x++) {
asample = araster.getPixel(x, y, asample);
for (int i = 0; i < asample.length; i++) {
System.out.print(" " + asample[i]);
System.out.println();
String format ="PNG";
System.out.println("##########Test Writing using new JDK1.4.1 ImageIO:");
Iterator writers = ImageIO.getImageWritersByFormatName(format);
ImageWriter writer = (ImageWriter) writers.next();
ImageWriteParam param = writer.getDefaultWriteParam();
ImageTypeSpecifier imTy = param.getDestinationType();
ImageTypeSpecifier imTySp =
ImageTypeSpecifier.createFromRenderedImage(bi);
param.setDestinationType(imTySp);
File f = new File("c:/tmp/myimage."+format);
try {
ImageOutputStream ios = ImageIO.createImageOutputStream(f);
writer.setOutput(ios);
writer.writeInsert(0, new IIOImage(bi, null, null), param);
} catch (Exception e) {
     System.err.println("could not write "+format+" file with alpha channel !");
e.printStackTrace();
public boolean imageUpdate(
Image img,
int infoflags,
int x,
int y,
int width,
int height) {
if ((toolkit.checkImage(img, -1, -1, null)
& (ImageObserver.HEIGHT | ImageObserver.WIDTH | ImageObserver.ALLBITS))
== 35) {
int iw = img.getWidth(this);
int ih = img.getHeight(this);
BufferedImage bi = new BufferedImage(iw, ih, BufferedImage.TYPE_4BYTE_ABGR);
Graphics2D big = bi.createGraphics();
big.drawImage(img, 0, 0, this);
System.err.println("+++++test image that was read using old Toolkti.getImage method");
alphaTest(bi);
synchronized (this) {
this.notifyAll();
return false;
return true; // image is not yet completely loaded into memory
public static void main(String[] args) {
//     BufferedImage image = new
// BufferedImage();
new AlphaChannelTest();
/*************************END********************/
The commandline looks like this:
[i]
com.sun.imageio.plugins.png.PNGImageReader@d1fa5
*****test image that was read using new Jdk 1.4 ImageIO.read() method
raster :
there is no Alpha channel!!!!!!!!!
wait
+++++test image that was read using old Toolkti.getImage method
raster :
Alpha channel found !
raster alpha:
##########Test Writing using new JDK1.4.1 ImageIO:
could not write PNG file with alpha channel !
java.lang.UnsupportedOperationException: Unsupported write variant!
     at javax.imageio.ImageWriter.unsupported(ImageWriter.java:600)
     at javax.imageio.ImageWriter.writeInsert(ImageWriter.java:973)
     at de.multivisual.bodo.test.AlphaChannelTest.alphaTest(AlphaChannelTest.java:113)
     at de.multivisual.bodo.test.AlphaChannelTest.imageUpdate(AlphaChannelTest.java:135)
     at sun.awt.image.ImageWatched.newInfo(ImageWatched.java:55)
     at sun.awt.image.ImageRepresentation.imageComplete(ImageRepresentation.java:636)
     at sun.awt.image.ImageDecoder.imageComplete(ImageDecoder.java:135)
     at sun.awt.image.PNGImageDecoder.produceImage(PNGImageDecoder.java:511)
     at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:257)
     at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:168)
     at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
end

in between i found out that the my png and jpeg test images did not have an alpha channel, since the tool i used to create them, did not write the alpha channel to disk.
if i use png with alpha channel, then the read works correktly with ImageIO.read()
however the read problem still remains for gifs and the write does not work for gifs and neither for pngs.
whether jpegs can be read with alphachannel i don't know since i don't have a tool to create jpeg with alpha channel. (at least gimp and corel9 are not able to )
and it is not possible to write the previous read png with alpha channel back as and jpeg with alpha channel

Memory Leak / J2ee Restart

We have a memory leak situation with our ep6 sps13 installation and we are not able to determine where the memory leak is. The stdout file shows the jvm heap being used up and even a gc doesnot bring down the used memory. Can you suggest any low-cost leak hunter software?
Thanks
Raj

I feel your pain.........
We are running SP11 Patch3. We have a custom app running on the portal that is VERY demanding. We experienced (and still do) many out of memory errors, crashing the portal and restarting the engine.
This shed some light on things.
http://www.tagtraum.com/gcviewer.html
This tool showed that when a major GC occured it was happening when the app was validating an order. Minor GC's could not keep up and when the generations hit max a major GC triggered. This kills the information the customer was working on and sometimes restarts the engine.
A temporary fix: We increased RAM to 8 Gig and made two engines of 1.5 gig (the max) That give the app more room and when one of the engines does a major GC and an OOO error kills the engine, it has the other engine to keep the going and the portal does not crash. Anyone working on the engine that took a dump gets kicked off but, the other engine keeps going.
With this tool, I was able to prove that the leak is coming from the app and not the portal.

Memory leak with File Write.vi

Hi All,
I am trying to save a big data cluster, which includes images, into a data log file. The vis I use are: New File.vi, Write File.vi, Close File.vi.
The problem is Write File.vi has memory leak when the data cluster includes images .
Anyone sees similar case? Any solution?
Thanks.
Aiqiu

Aiqiu,
I am glad you found out about flattening your image to a string. I was about to post and say that you probably didn't want to save the IMAQ image reference to a file, because after you closed the image in memory, there wouldn't be anything for the IMAQ image reference to point to. You are correct to flatten the image to a string. Below is a link to a document which discusses doing this to communicate over datasocket, but the processes of flattening the image to a string is the same regardless of whether or not you are sending the image across a datasocket connection or saving to a file.
Transfering Images with DataSocket
As for the memory leak. I am pretty sure that if you passed all of the IMAQ Image references created in the "Image Init Buffer.vi" subVI and then closed each reference individually, that the memory leak would probably go away.
Lorne Hengst
Application Engineer
National Instruments

Probleme avec Imaq write file qui n'enregistre pas les images en jpg

Bonjour,
dans le cadre d'un stage, je suis en train de dévellopper un programme qui récupère une vidéo issue d'une caméra usb. Jusque là tout vas bien. Mais je souhaite réalisé une vidéo a partir d'une suite d'image au format jpeg que le programme aura enregistrer dans un dossier.
Mon probleme etant que Imaq write file 2 que j'utilise n'arrive pas a enregistrer les image au format jpg (alors qu'il y arrive au forma png, tiff ou jpg2000). Ainsi, lorsque je lance la capture, le programme a l'air de faire des opération mais lorsque je vais dans le dossier où doivent etre entreposé les jpeg, celui ci est vide.
J'utilise labview 2010 et suis sous windows 7 x64 bits.
Merci d'avance pour l'aide que vous pourez m'apporter.

oui bien sur, le voila :
Pièces jointes :
test Controle_caméra_prosilica_2.8_2121.vi ‏3752 KB
CalculateFPS.vi ‏12 KB

How to configure license file for Memory Leak tool and WL Server 9.2?

(I posted to general JRockit forum before realizing existence of this forum which is probably more applicable.)
Here's our problem:
Running latest version of WL 9.2 MP3 and JRockit Mission Control 3.0.1
Able to run Mission Control, and connect to the WL Server and to run View Console with no problems.
I can't get Memory Leak tool to run because it complains about needing a license file.
First I tried with off the shelf WL 9.2 MP3.
Get error:
A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (192).
Error: Can not find component Memory Leak Detector for JRockit * in the license file. Please check http://www.jrockit.com/license for license updates.
So I downloaded license file from JRockit download site - wls92.zip. It contains several files, but no clear instructions on what to do with these files. I copied one of these files "LIC-WLSP92.txt" to my JRockit home as C:\bea\JROCKI~1\jre\license.bea
Tried again. Restarted WL server. Restarted JRockit Mission Control.
Get error: A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (3052).
The license file does not exist at: C:\bea\JROCKI~1\jre\license.bea
Any advise on how to install license or who to contact for help?

Installed Mission Control 3.0.3.
Got following message when I attempted to run Memory Leak:
A license for Memory Leak Detector could not be found on the JRockit at (1.5) weblogic.Server (192).
Error: Can not find component Memory Leak Detector for JRockit * in the license file.
Please check http://www.jrockit.com/license for license updates.
I believe that we're using the latest downloads of WebLogic 9.2.x and JRockit.
WebLogic is running using 9.2.3 and JRockit build R27.4.0-90_CR358515-94243-1.5.0_12-20080118-1154-windows-ia2
Contents of C:\bea\jrockit_150_12\jre\license.bea:
<?xml version="1.0" encoding="ISO-8859-1"?>
<bea-licenses>
<license-group format="1.0" product="JRockit" release="*">
</license-group>
</bea-licenses>
Could WebLogic be misconfigured?
Any diagnostics to help figure out the licensing?
Any other ideas?

Photoshop CS2 Cannot read PNG files--"Not Enough Memory"

Hi! I have a bit of a problem. I've scoured the interwebs for days but can't find a solution.
My copy of PSCS2 was able to open PNGs in the past, but it just up and decided it doesn't want to anymore. I'm serious--I can't think of any major overhaul or anything I did to cause it, but now it won't read them correctly. It says there's "not enough memory," which doesn't really make sense, when I have a Macbook Pro and nothing running in the background. On top of that, the particular files I've been trying to open are barely 100kb. I've used canvases upwards of ten thousand square pixels in dimension with no problem.
This is with any PNG file. It's not an "incorrect extension" problem, because I made these files and just need to reopen them to edit things.
Here are some screenshots that show what's been happening; nothing exciting, but just in case someone notices something I don't:
That's the picture I want to open.
And that's what pops up.
:/ I'm a little dumbfounded. Halp?

Now, this is strange.
I restarted my computer and now the message has changed--to a simple one, but albeit still confusing.
Sigh.
I didn't do anything but restart my computer.

Getting error could not place the document because there is not enough memory RAM wile importing .png file into Photoshop cc

getting error could not place the document because there is not enough memory RAM wile importing .png file into Photoshop cc

Without knowing anything about your system, your image file, your working document and so on nobody can even begin to guess. The file could be damaged, there could be color management issues at play and what have you...
Mylenium

Memory leak with large files and this code?

Okay, so the following code will not complete.
Basically what I am doing is opening 5 files and generating a PDF document from the already opened Report file, which is renewed prior to the PDF export operation. I left out the general stuff at the start. I am also writing out the location of the PDF to a HTML file, which acts as an index of the exported PDF documents.
I believe it is due to some sort of memory leak issue, but it could be something else or just my code. I have not stepped through this code, but for small file sizes of say less than 40 megs per file, it works fine. For file sizes along these lines:
File 1 = 230 megs
File 2,3 = 26 megs
File 4,5 = 8 megs
it will belch erors at the end of about the 5th iteration through the For loop. It will complete the 5th iteration however. Here are the errors generated:
84   10/26/2006 9:35:15 AM Error:
85   File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p1.TDM" file is invalid.
     (Error no. 6)
86   10/26/2006 9:40:19 AM Error:
87   File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p2.TDM" file is invalid.
     (Error no. 6)
88   10/26/2006 9:45:17 AM Error:
89   File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p3.TDM" file is invalid.
     (Error no. 6)
90   10/26/2006 9:53:07 AM Error:
91   File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p8.TDM" file is invalid.
     (Error no. 6)
92   10/26/2006 10:00:39 AM Error:
93   File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p9.TDM" file is invalid.
     (Error no. 6)
94   10/26/2006 10:01:01 AM Error:Error occured during file creation.
95   10/26/2006 10:01:01 AM Error:
     Error in <GM315 Pa...sing.VBS> (Line: 185, Column: 5):
     File handle for "W:\TR-2051-2100\TR-2060 - BAS Arctic PTC\Vnom\00-99\VnomCombined00-99\p1.TDM" file is invalid.
     (Error no. 6)
For files of a larger size, like:
File 1 = 7500 megs
File 2,3 = 80 megs
File 4,5 = 25 megs
This occurs after about 2-3 iterations through the loop.
see attachment for code.
Attachments:
ForLoopCode.txt ‏11 KB

i am having a similar error randomly inserted in the log
25   10/1/2009 1:58:36 PM Error:
26   File handle for "C:\Program Files\Summitek\Spartan\data\tdm\S Parameter Test $SSN$ 49.TDMS" file is invalid.
     (Error no. 6)
and
31   10/1/2009 1:58:37 PM Error:
32   File handle for "C:\Program Files\Summitek\Spartan\www\temp\Test_$SSN$ 49_602313172.pdf" file is invalid.
     (Error no. 6)
it doesn't seem to be causing an immediate problem, but i have had several unexplained Diadem lockups.
they occur in log after i use CALL DATAFILELOADSEL and CALL PICpdfexport
help? what does this mean
jim

Memory leak in IMAQ Write PNG File

Similar Messages

Maybe you are looking for