Serious memory leak in Safari 5.1.2 for Lion

Safari keeps on using memory and frees up almost nothing even after I close the web page.

You didn't REALLY believe they FINALLY fixed the leak, did you?
Safari's been leaking for years, no reason to believe they'd fix it now, regardless of what the release notes say.
You're unlikely to see any difference in memory usage by closing one or two pages.

Similar Messages

Inactive Memory leak in Safari 4.0.3

There is a memory leak in Safari 4.0.3. I haven't isolated it to a particular page since I usually have 15-20 tabs open when I notice the spinning ball, caused by VM paging. When this happens, according to Activity Monitor, Safari.app uses between 500-2000mb of "Real Memory", yet when I close it almost all of the blue "Inactive Memory" is released. The last time this happened, it freed 5.4gb.
This is getting annoying and is certainly bad for the SSD. Any idea if there's a fix?
BTW I've got the new Pro with 8 gigs of DDR3 and an SSD, and 20mbit FIOS internet... There is no excuse whatsoever for the spinning ball!

The way Safari accumulates memory is normal. The way it is trying to page the memory to disc and error-ing is not. I think the integrity of your disc volume / catalog and directories may be to blame.
Try a bit of basic maintenance:
Repairing permissions is important, and should always be carried out both before and after any software installation or update.
Go to Disk Utility (this is in your Utilities Folder in your Application folder) and click on the icon of your hard disk (not the one with all the numbers).
In First Aid, click on Repair Permissions.
This only takes a minute or two in Tiger, but much longer in Leopard.
Background information here:
http://docs.info.apple.com/article.html?artnum=25751
and here:
http://docs.info.apple.com/article.html?artnum=302672
An article on troubleshooting Permissions can be found here:
http://support.apple.com/kb/HT2963
By the way, you can ignore any messages about SUID or ACL file permissions, as explained here:
http://support.apple.com/kb/TS1448?viewlocale=en_US
If you were having any serious problems with your Mac you might as well complete the exercise by repairing your hard disk as well. You cannot do this from the same start-up disk. Reboot from your install disk (holding down the C key). Once it opens, select your language, and then go to Disk Utility from the Utilities menu. Select your hard disk as before and click Repair.
Once that is complete reboot again from your usual start-up disk.
More useful reading here:
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/TS1417?viewlocale=en_US
For a full description of how to resolve Disk, Permission and Cache Corruption, you should read this FAQ from the X Lab:
http://www.thexlab.com/faqs/repairprocess.html

Memory leak in Safari 4 & 5

In 10.5 and 10.6, Safari has what I think is called a memory leak. It ties up memory that it is not actually using, so that its use balloons. I can quit and re-open all the same windows and gain half a gig of memory back.
Anybody know a way to stop this?

There is an on-going thread from Aug 2009 about "Snow Leopard" and "Memory Leak" or similarly "Memory Hog" etc and not releasing memory as well as how Safari is one of the worst offenders for many others.
Some have 4GB RAM and no trouble, some with same amount but do.
And of course clearing Previews, History, Cache, even the Bookmarks cache.
~/Library/Caches/
Flash and other plug-ins, (flash has its own cache) and using something to only load Flash if desired.
But most found 10.5 and Safari 4 "better behaved" and not the issue 5.0 and 10.6 are.

2014.2 Crash by scrubbing - serious memory leak? (screenshot attached)

Hello. I've bought one year premiere pro cc plan. After upgrate from 2014.1 to 2014.2 I suffer with many crashes a day. I can't roll back, because I am in the middle of the feature film edit and new files are not opened by 2014.1
The most anoying crash is about memory use growth.
First - my system and sequence specs:
I have 48gb ram, intel i73930k processor, 4TB main drive and 3x250SSD drives for scratch disks. My Gpu is 2 x nvidia gtx 780 (3gb ram each). I work in 4k workspace and with uhd timeline 2.35 : 1 ratio. (3840x1628)
Second - how to crash.
I open the pproj file (about 8mbytes in size). It is a full feature film, i edit it in 3 parts for better performance. My main codec is cineform, both for HD previews and final 4K encoding.
Then I move playhead over any clip already rendered with preview (HD - mpeg or cineform).
Then I hold left mouse button and I start to scrub playhead left/right randomly along timeline, the problem unfolds: ram usage starts to go up, after some time of scrubbing it hits the ceiling and premiere crashes (along with eventual other apps opened as firefox).
It seems like premiere is registering every displayed frame in memory, even if it is already rendered as preview. And there is no limit set for doing this, so it overflows and crash.
As you see on the picture, in preferences there is 8GB reserved for other apps, and optimization for memory set.
Scrubbing over non-rendered clips makes ram eating even worse, crash occurs earlier.
I wonder - do you people have this similar problem? Could someone reproduce this inside any larger project (30 minutes of standard movie edit).
I would like to find solution, because I cant allow for so many crashes during serious production workflow.
nl

I'm having the same problem too.
I've been posting my issues on another post entitled, "Just spent $7000. on new custom computer and PremiereProcc2014 crashing". (see my NEW profile computer specs as of two weeks ago)
I've been experiencing about 25 crashes in an 8 hour period. Some after 1/2 hour and others back to back crashes.
I didn't even think of why it was crashing until I called support, whereas they took over my computer and showed me that even when timeline is PAUSED, YES EVEN JUST PAUSED, we watched the RAM clime and clime to the ceiling until Premiere crashed.
It's so frigg'in frustrating that people here are complaining and there seem to be absolutely no talk about this issue. It's probably the cause of many Premiere issues, in my humble opinion.
Strangely enough, the tech fixed the problem (but this has been happening to me often and even with my older computer). Anyway he stopped several Adobe related running programs in the background, and took my timeline to a new project.
Basically, I'm not sure exactly what he did to solve the problem, and sadly I suspect it will return as it always has done so.
One strange note is that he reset all my preferences back to the defaults. I'm talking about maybe 15 presets that I have including a handful of changed key-strokes (to my liking), and simple things like "double-click opens in same folder" and "don't replay timeline after rendering" and "don't go to beginning of project after end of play-line" and changed around my user interphase to my liking.
These type of customization shouldn't cause Memory Leaks? I just don't get it.

Firefox 4 still suffering from a serious memory leak, ends up using 2GB of RAM on 5 tabs and a few plugins?!!

Why does even Firefox 4, which was supposed to have this issue fixed by now, still suffer from memory leaks?
I opened up 4-5 tabs, enabled Firebug to tweak a few pages, and an hour later Firefox usage is up to 2GB of RAM?
What a...?!
Now, seriously, if you run to suggest that it is most likely due to add-ons and that I should disable them all and start Firefox in safe mode, let me just cut you off right there and ask you this - out of millions of people who downloaded this browser, who the hell uses it without any plugins and/or in safe mode?
If you're gonna make a browser, make it so that it's lean and free of these issues to begin with, out of the box AND in case an addon or something else is added to it - can't they protect the core files and libraries from being victims to this, in case the addons are to blame?
And in case it's a Firefox issue to start off with, seriously, can you get a dedicated developer to look into this alone and get it fixed, once and for all?

I have six tabs open and generally have 3-5. It's been sitting here since last night. I'm using 296Mb ram which is high for me on Windows. My wife and son both use FF4 also and, having just checked, are between 210 and 268Mb respectively.
No one I know ever complains about high memory usage in FF4 and neither have I experienced it since FF2.5 when memory leaks any user would notice were all fixed.
So my advice is the same. If your add-ons aren't causing you problems, fix your system.

Memory leak in Safari WebFeedParser

Lately I've noticed that every so often a process com.apple.Safari.WebFeedParser is taking up more memory than it should be. Often times Has anyone seen this problem or know the cause of it?

Back up all data before proceeding.
Quit Safari if it’s running. Then select
           ▹ Force Quit…
from the menu bar. A small window will open with a list of running applications. Safari may appear in that list, even though you quit it. If so, select it and press return. Close the window.
Step 1
Hold down the option key and select
          Go ▹ Library
from the Finder menu bar. Delete the following items from the Library folder (some may not exist):
          Caches/com.apple.Safari
          Caches/com.apple.Safari.SearchHelper
          Caches/com.apple.SafariServices
          Caches/com.apple.WebKit.PluginProcess
          Caches/com.apple.WebProcess
          Caches/Metadata/Safari
          Preferences/com.apple.WebKit.PluginHost.plist
          Preferences/com.apple.WebKit.PluginProcess.plist
          Saved Application State/com.apple.Safari.savedState
Leave the Library folder open. Try Safari again. If the problem is solved, stop here. Close the Library folder. If you still have a problem, continue.
Step 2
Move the following items from the open Library folder to the Desktop (again, some may not exist):
          Cookies/Cookies.binarycookies
          Internet Plug-Ins
          Preferences/ByHost/com.apple.Safari.*.plist
          Preferences/com.apple.Safari.Extensions.plist
          Preferences/com.apple.Safari.LSSharedFileList.plist
          Preferences/com.apple.Safari.plist
          Preferences/com.apple.WebFoundation.plist
          PubSub/Database
          Safari
          SyncedPreferences/com.apple.Safari.plist
Here, "*" stands for a long string of letters, numbers, and dashes.
Note 1: You are not moving the Safari application. You’re moving a folder named “Safari.”
Note 2: This step will remove your Safari extensions, if any, and their settings. If you choose to reinstall them, do so one at a time, testing each time to make sure you haven’t restored the problem.
Try again. Your settings and bookmarks will be lost. The default set of bookmarks will be restored. Delete them all.
If Safari is now working normally (apart from the lost settings), look inside the “Safari” folder on the Desktop for a file named “Bookmarks.plist”. Select
          File ▹ Import Bookmarks...
from the Safari menu bar. Import from that file. Recreate the rest of your Safari settings. You can then delete the items you moved to the Desktop.
If the issue is still not resolved, quit Safari again and put all the items you moved to the Desktop back where they were, overwriting the newer ones that may have been created in their place. You don’t need to replace the files you deleted in Step 1. Stop here and post again.
If you don’t like the results of the last step, you can undo it completely by quitting Safari and restoring the items you moved or deleted in that step from your backup, overwriting any that were created in their place.

Serious Memory Leak Problem. Needs to be resolved ASAP

Ok, I have been researching this problem All Night and I cannot figure it out!
I am Running Final Cut Studio 2 Final Cut Pro 6. I Edited a piece Today and I have been trying to REnder it for 3 hours. I have cleared out the preferences. I have gone through all of the picture files, and I have deleted the Render Files and started over, No matter what, I watch in the activity monitor as it bleeds the memory and stops withj an out of memory error message. I would really appreciate if anyone has another solution i could try

I don't think the extensions are the problem. As David said If any of those images were saved in a color mode other than RGB, you'll have trouble. This usually only occurs when you put the shots in the timeline but you'll want to get rid of them from the browser as well just to be sure.
i basically imported a disc of random pics at the beginning of the project
I assume that you copied the contents of the disk to your hard drive first otherwise FCP will be forever reading those files from the CD.
rh

Memory leak in java / forcing garbage collection for unused resource?

Is there any possibility in big programs if not designed properly for leakage of memory?
If say i forget to force garbage collection of unused resouces what will happen?
Even if i am forcing garbage collection how much assurity can be given to do so?
I need answers w.r.t typical programming examples if someone can provide i will be happy.
Or any useful link.
Thanks
Vijendra

Memory leaks are usually much related with C/C++ programming since in that language you have direct access to memory using pointers.
Now, in Java you do not have access to pointers, however you could still tie up your objects in a way that the garbage collection can not remove them.
Basically, the grabage collection will search all the object implementation, and see if they are referenced or not. If not it will free that memory. However if you, somehow in you code allow a reference to your object then the garbage collection will not displose of that object.
An example I can think of is when developing web applications. For example storing objects in the session will mean that you will have a reference to the object from the session, therefore the garbage collection will not free up the meomry taken by those objects untill the session has expired.
That is how I know it... at least that is how they tought it to me!
regards,
sim085

There seems to be serious flash memory leak in ie7

Hi.. I have run into a serious memory leak issue with flash on
internet explorer 7.0.5730.13 (everything works with firefox). It can be
seen clearly browsing open flash charts site. Here are steps to
reproduce:
1) go to
http://www.websector.de/blog/2007/10/01 ... wsmonitor/
2) click start on WSMonitor
3) File->New Window paste following address in address bar and click
enter: http://teethgrinder.co.uk/open-flash-ch ... hollow.php
4) click from chart to chart and see each time how memory increases...
This does not happen with firefox.
Independently to trouble shoot it wasn't any code I confirmed by making an swf file with actionscript with simply following:
package {
import flash.display.Sprite;
     public class main extends Sprite {
          public function main() {
               trace("starting3");

hello, can you try to replicate this behaviour when you launch firefox in safe mode once? if not, maybe an addon is interfering here...
[[Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]]

Safari Flash Player Memory Leak?

I recently got a new macbook pro, 13" model (with the 2.2 GHz dual processor). Last night I noticed that it was running pretty slowly, something that I figured was weird considering the amount of power it has compared to my four year old desktop computer. I managed to isolate the problem: a memory leak with safari's flash player. I watch a lot of netflix and some TV episodes...and it turns out that the flash player accumulates up to 2 GB of RAM by itself. My pro has 4 GB of RAM and it never goes above 50% of that memory unless I watch videos. Only way to get around the problem is to force close the flash player application...but it's annoying to have to reload what I was watching. Any ideas on the fix for this?

Far as I know, Netflix doesn't use Flash, it uses Silverlight.
Your Flash likely got pwned.
So check here and update both
http://www.mozilla.org/en-US/plugincheck/
Then run ALL of OnyX's cleaning and maintainence aspects and reboot
http://www.titanium.free.fr/

Safari 4 memory leak?

With Safari 4 open for only 12 hours, it's VSize has already grown to over 35GB while it's RSize stays around a couple hundred MB. Any other users experiencing this?

Thanks -M@ for the post.
I've been waiting for Chrome to come out of beta.
When I first checked the VSize of Safari 4 on Dec 31 after it was open for about a week, it was close to 100GB! Before Safari 4's release, I could play any of my 1000 Logic Express 8 files without stopping because of insufficient system RAM, although it was close to the limit my 2GB provided. Logic Express 8's built-in CPU monitor would show one core peaking when the first notes were played but the music continued on to finish as both cores would then fairly equally share the processing load. After Safari 4's release and with the browser open for any appreciable length of time, I couldn't get past the first note on any of them the first time I tried to play them. They would play the second time I tried. System resource allocation was slow because of Safari 4?
Also post-Safari 4: Every other day, I was losing 100-300MBs of hard drive space after waking up my Mac. A shut down would restore the space back. Something to do with routine maintenance tasks and Console logs? As long as I close Safari before sleeping my Mac, this has not happened.
By the looks of other related topics in Safari for Mac discussions and the response here by Barry on Jan 1, there appears to be no performance issues related to any memory leaks in Safari 4, which makes me think my VSize problem is a Core Duo and/or Tiger specific one.

Memory leak in OCI while using AQ

There seems to be a serious memory leak in the OCI driver (9.2.0.1) when using a JAVA client to dequeue a database queue (Advanced Queuing).
Continuous dequeuing causes the heap memory to increase, and this memory never gets freed which leads me to suspect a memory leak in the OCI components (as the memory allocated for the JVM is constant). The heap memory increases by 3-4 MB after a dequeue of 1000 RAW messages,
Has anyone come across this problem before and if so are there any solutions? Changing to a thin driver is not a solution for me due to other requirements.
I'm using using Oracle client v9.2.0.1 libraries running on Solaris 8.
The source code for my JAVA test client is as below:
/* JAVA dequeue */
package com.ubsw.risk.pce.eventqueues.test;
import oracle.AQ.*;
import java.sql.*;
import oracle.jdbc.*;
public class testRawDequeue {
public testRawDequeue() {
public static void main(String[] args) {
Connection conn = null;
AQSession aq_sess = null;
try {
Class.forName("oracle.jdbc.driver.OracleDriver");
//Use OCI connection
conn = DriverManager.getConnection("jdbc:oracle:oci:@DB_NAME.world","user","password");
conn.setAutoCommit(false);
Class.forName("oracle.AQ.AQOracleDriver");
while(true) {
aq_sess = AQDriverManager.createAQSession(conn);
runTest(aq_sess);
aq_sess.close();
aq_sess = null;
System.gc();
} catch (Exception e) {
e.printStackTrace();
System.out.println(e.toString());
try {
if (aq_sess != null) {
aq_sess.close();
if (conn != null) {
conn.close();
} catch (SQLException sqle) {
public static void runTest(AQSession aq_sess) throws AQException, SQLException
AQQueueTable q_table;
AQQueue queue;
AQMessage message;
AQRawPayload raw_payload;
AQEnqueueOption enq_option;
String test_data = "new message";
AQDequeueOption deq_option;
byte[] b_array;
/* Get a handle to a queue - in aquser schema: */
queue = aq_sess.getQueue ("user", "raw_msg_queue");
System.out.println("Successful getQueue");
/* Creating a AQDequeueOption object with default options: */
deq_option = new AQDequeueOption();
/* Dequeue a message: */
message = queue.dequeue(deq_option);
System.out.println("Successful dequeue");
/* Retrieve raw data from the message: */
raw_payload = message.getRawPayload();
b_array = raw_payload.getBytes();
System.out.println("bytes:" + b_array.toString());
queue.close();
((AQOracleSession)aq_sess).getDBConnection().commit();

This sounds very similar to the memory leak I have in Oracle 9i using Pro*C++. Everytime a connect is made memory appears to leak and it only happens in multithreaded mode not default mode. There is a thread about this under the Oracle C++ call interface. Under 9i it appears to leak about 60K per connect rather than 60 bytes.
Paul

Memory Leak in Adobe Premiere CC on Windows

I installed Premiere CC on Windows 7 ( Intel Core i7-3770K [email protected] GHz, 16GB RAM). Software has a serious memory leak. After less than hour working on a very simple project (no rendering, no effects) memory usage reached 15 GB, at which point Premiere stopped responding. After closing and reopening software memory usage again started to increase. I was testing it by just scrubbing over timeline, no editing, memory usage still slowly crept-up. I called Adobe technical support, they tried to tell me, that this is normal. Right! It is normal to be forced to close and reopen application every hour? I do not think so. I have Premiere CC also installed on my MAC Book Pro, checked memory usage on much bigger project, it was steady, not creeping up, using beween 1 and 2 GB. I checked forums for this problem, there are several posts, but have not found any response from Adobe regarding this.
Update:
Tonight I continued working on same small project, within 2 hours I had to shut down Premiere 3 times. I also limited in setting memory Premier can use, that did not make any difference, usage by Premiere went to maximum - total 16 GB with about 2 GB taken by system and other stuff running. I am monitoring memory usage on resource monitor. Used Physical memory went 100 %, Commit Charge about 60%. This so far happened three times in a row.
Adobe, can you hear me?
Milan
Message was edited by: milan-to
Message was edited by: milan-to

Adobe, can you hear me?
Not guaranteed when posting here. Try below instead.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Having said that, this is not a problem I see on any of the four Windows machines I work on. And it's not a problem commonly reported here. So my inclination is to suggest that something may be funky with your install.

BUG: Apex4/Anychart5 - memory leak?

We are running into a pretty serious problem with resources. It seems that there is some kind of interaction between Apex and Anychart5 that is causing a pretty serious memory leak. For example, in one dashboard I am building, I have 9 charts on a page. When I click through a chart to a second page, I have three charts and an Interactive report.
None of the sql is really all that complex. But I will include one of the queries singled out by one of our DBAs as being involved in consuming over 20 GB of data (values slightly modified for security). The query:
SELECT CASE
WHEN quarter = 'Q1'
THEN
'/pls/apex/f?p=108:3:1111111111111111::::P3_YEAR1,P3_YEAR2,P3_CLICK_VAL,P3_QUARTER:2009,2008,2009,1:'
WHEN quarter = 'Q2'
THEN
'/pls/apex/f?p=108:3:1111111111111111::::P3_YEAR1,P3_YEAR2,P3_CLICK_VAL,P3_QUARTER:2009,2008,2009,2:'
WHEN quarter = 'Q3'
THEN
'/pls/apex/f?p=108:3:1111111111111111::::P3_YEAR1,P3_YEAR2,P3_CLICK_VAL,P3_QUARTER:2009,2008,2009,3:'
WHEN quarter = 'Q4'
THEN
'/pls/apex/f?p=108:3:1111111111111111::::P3_YEAR1,P3_YEAR2,P3_CLICK_VAL,P3_QUARTER:2009,2008,2009,4:'
END
link,
quarter label,
so_ext_price Sales_2009
FROM ( SELECT SUM (v.so_ext_price) so_ext_price,
('Q' || TO_CHAR (v.cal_qtr_num)) quarter
FROM owner.materialized_view_mv@db_link_name v
WHERE v.cal_year = TO_CHAR (2009)
AND v.account_number IN
(SELECT *
FROM TABLE(user_pkg.get_customer_numbers (
'APP_USER',
'USER_PROPERTY',
'CUSTOMER_NAME'
-- THE ABOVE SUBQUERY SELECTS FROM A PIPELINE FUNCTION TO RETURN A LIST OF STRINGS
GROUP BY v.cal_qtr_num
ORDER BY v.cal_qtr_num)
As you would expect, this query returns 4 records reflecting sales by quarter. The query takes about four seconds to run. Explain plan cost is just under 14K. The pipeline function literally returns a single column of about six values using a simple select distinct where the parameters passed are filters in the where clause. The pipeline function returns in approximately 1 second. The largest result set it ever returns is six rows. The pipeline function is innocuous on its own but I am suspicious that it may be where we're running into issues. We weren't seeing these problems (or at least they weren't as noticeable) until we needed to use pipline functions. 'Don't use pipeline functions' is not an acceptable work around in our case. While I can figure out a way around it in the charts by returning SQL from a function, I cannot do so in the interactive reports.
What our DBAs found is that the code pasted below is what was sucking down 22 GB of ram, then after clicking through to the second page the same code (for a different chart query) was consuming 17 GB of ram almost depleting our 48 GB of ram on our server in less than ten minutes. I disabled the chart running each 'offending' query and we had the same results with a different chart but the same underlying code below.
I don't know where in Apex this lives but it's the killer. Can I get some feedback? Anyone else having similar issues?
declare
rc__ number;
simple_list__ owa_util.vc_arr;
complex_list__ owa_util.vc_arr;
begin
owa.init_cgi_env(:n__,:nm__,:v__);
htp.HTBUF_LEN := 63;
null;
null;
simple_list__(1) := 'sys.%';
simple_list__(2) := 'dbms\_%';
simple_list__(3) := 'utl\_%';
simple_list__(4) := 'owa\_%';
simple_list__(5) := 'owa.%';
simple_list__(6) := 'htp.%';
simple_list__(7) := 'htf.%';
simple_list__(8) := 'wpg_docload.%';
if ((wwv_flow_epg_include_modules.authorize('apex_util.flash') = false) or (owa_match.match_pattern(p_string =>
'apex_util.flash'
/* */,p_simple_pattern =>
simple_list__
,p_complex_pattern =>
complex_list__
,p_use_special_chars =>
false)))
then
rc__ := 2;
else
null;
null;
apex_util.flash(p=>:p,XMLCallDate=>:XMLCallDate);
if (wpg_docload.is_file_download) then
rc__ := 1;
wpg_docload.get_download_file(:doc_info);
null;
null;
null;
commit;
else
rc__ := 0;
null;
null;
null;
commit;
owa.get_page(:data__,:ndata__);
end if;
end if;
If we are barking up the wrong tree, I'd be VERY happy. I'd rather it was something I could fix.
Edited by: WannaRock on Aug 24, 2010 9:53 AM

Thanks for looking at this post. We have resolved the issue for ourselves by working with our DBAs to narrow down where the problem actually started. We found that the particular SQL we were looking at was not the issue. In a chart on a subsequent page (via a click through), we were actually running into where apex was starting to consuming memory but we were catching it later.
What we found was that when we had a chart query that was SQL containing a pipeline function, the memory usage went up. And within 10 minutes, the server would crawl to a halt. To release the memory, the DBAs would have to bounce the Apex instance. When I changed the query to be a function returning SQL, the problem stopped. I don't know what the correlation was between SQL and moving to a PL/SQL function returning SQL.
I am not even 100% positive of the pipeline function being the cause. I only know that this started happening about the same time as when I implemented the pipeline function. I understand you are leery of a one-second function/query running up that kind of utilization. No one here believed me either (including me really). We figured it HAD to be a coincidence. But once I changed the query from SQL to a function returning PL/SQL, our problem went away.
Thanks to all who looked at and thought about this.
Walter

Memory leak in Digital Waveform

I have a program with a pretty serious memory leak that uses up all my system RAM and crashes my computer within a few hours of running the program.
The program takes an array of U16s where each bit represents a digital signal. The VI converts each U16 to a digital array and groups the resulting 16 digital signals into different busses for display on a Digital Waveform Graph. The profiler doesn't show any excessive memory usage in the VI. I put the whole VI into a Diagram Disable structure and moved a few pieces out at a time, and eventually the only thing inside the disable structure was the Digital Waveform Graph indicator. When this indicator is enabled, the memory usage of my system rises slowly and steadily until it uses all available RAM and crashes the system.
If I replace the Digital Waveform Graph indicator with a cluster, the memory leak still occurs (but much more slowly). I thought using the cluster fixed the leak until I reran the VI overnight while using the cluster instead of the Graph.
If I stop the VI before all the RAM is used, the RAM will not release until I close LabVIEW entirely. Once LabVIEW closes, the memory is released slowly and exponentially unless I use the "End Process" option in Task Manager.
This is a continuation of a previous post I made where I thought the memory leak was due to problems transferring data from an FPGA for display.
I ran the MemLeak vi (attached) on two separate systems, both running LV 2013 SP1, and got the same results. The memory leak is noticeably fast when using the enable structure connected to the Digital Waveform Graph but still present when using the cluster of Digital Waveforms.
Attachments:
MemLeak.vi ‏33 KB
LV shutdown.PNG ‏101 KB

Thanks for the replies.
In response to John's points:
1. The attached VI is a simplification of an FPGA VI that read a fixed number of samples from a DMA FIFO using an FPGA Interface Invoke Method approach. I'm using a card (PXI-7842R) that doesn't allow use of the Acquire Read Region method. In order to allow people without an FPGA card to hopefully see the issue, I replaced it with the for loop. Assuming that this for loop does leak (which I don't believe it does; as altenbach said, it's a fixed size allocation that LV should be able to reuse), why would I see a difference in the leak magnitude depending on which indicator I connect to the array?
2. I've previously reviewed the document you referenced, and I don't see any errors from it present in my code; do you? I have no global/local variables, strings/arrays displayed on front panel, property nodes, coercion dots, altered memory sizes, resizing/reallocations, etc. I don't see any weird buffer allocations. I used to have the conversion from U16 array to digital waveforms in a subVI but placed it on the same diagram to allow incremental use of the Diagram Disable structure.
3. The forum post you referenced had many of the items discussed above, plus it was solved using an RT FIFO. I'm not passing data from a producer to a consumer; I'm just displaying acquisition results. I guess you could say I'm processing the data, but I'm really only converting it to a format that the indicator will take; I'm not operating on the data.
It's good that the leak doesn't show up in 2014, but my SSP runs out in a couple of days; I never got an upgrade to 2014. This is the last item remaining on the development path, and we've already spent ~$4k to upgrade the controllers enough to display the acquisition without dragging down the CPU. I will be in hot water if I spent all that money and then end up having to scrap the display...

Serious memory leak in Safari 5.1.2 for Lion

Similar Messages

Maybe you are looking for