Major Aperture 3 memory leak

Well, I've completed the migration of my A2 library over to A3, but it still needed to do some processing. I left it overnight and awoke to find a "Warning: Your startup disk is almost full" message, Aperture 3 paused, and everything else paged out of main memory.
Screenshot from activity viewer:
http://britton-photography.com/fm/aperture3memory.jpg
Anyone else experiencing this?

I just thought I'd weight in and say I too had this problem. I left Aperture 'upgrading' my library and went away all excited and when I came back my computer was at a crawl (I mean, it took several seconds just to check my password coming out of screensaver lol) and I had an autodialogue saying OSX had no more memory to run applications and suggested I quit several apps, nothing big, just Textedit and Safari etc. I clicked Finder and saw that my available disk space was...0Kb!
I agree with the previous poster, first impressions are important and this is a REALLY poor first impression. Fortunately I love Aperture so I'll forget about it in time I'm sure but it's poor that this was missed in the testing, it's clearly a non-local enough problem it should have been spotted.
I have to add that I typed the last paragraph about 10 minutes ago, my computer slowed to a virtual stop as I typed as Aperture again killed me.
After an absolute dearth of information about the very existence of Aperture 3 leaving the community of loyal users in the dark to an almost embarrassing degree for a year, this is hardly as auspicious start. When I have to force quit an application the very first time I use it, I'm not impressed. Rather an excitedly flicking through the new features, I'm trying to figure out how to stop my computer falling over every time I start it!

Similar Messages

There appears to be a MAJOR issue (hang/memory leak) in "about:home", also known as the Firefox Start Page, in Firefox 26.0 on Windows!

There appears to be a MAJOR issue (hang/memory leak) in "about:home", also known as the Firefox Start Page, in Firefox 26.0, on Windows!
observed on:
- Windows 7 x64 machine with 12GB RAM and high-performance CPU (core i7-920)
- Virtual Machine guest running WinXP SP3 (in Oracle VirtualBox) on the same machine
- Intel Atom D525 netbook with 4GB RAM, running Win7 x64
Neither of these machines are connected via Sync or anything like that. The Firefox instance on the VM is a fresh/clean install.
The problem:
- 100% cpu usage for 10 seconds, memory usage (PF usage in XP) goes up to 1.7GB
- if "about:home" is the Firefox Start Page, effectively it hangs the computer at Firefox startup for 10 seconds
- if "about:home" is NOT the Firefox Start Page, startup is fine - BUT if I press the "home" button on the toolbar it loads "about:home" which causes the same issue again

Thank you cor-el! Your suggestion has solved the problem on my WinXP VM which I was using to test, and I will soon confirm that it has also solved the problem on my primary Win7 desktop.
To recap:
- I set "browser.aboutHomeSnippets.updateUrl" to an empty string
OLD VALUE: https://snippets.mozilla.com/%STARTPAGE_VERSION%/%NAME%/%VERSION%/%APPBUILDID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/
NEW VALUE: (blank)
- I deleted the folder \storage\persistent\moz-safe-about+home under the Profile directory
Actual folder name on WINDOWS XP:
C:\Documents and Settings\<USERNAME>\Application Data\Mozilla\Firefox\Profiles\<PROFILENAME>\storage\persistent\moz-safe-about+home
However I have a concern that the '''OLD VALUE''' of "browser.aboutHomeSnippets.updateUrl" will creep back in, in a future update! Can you communicate this issue to someone on the development team?

Editing in aperture is doing crazy things. I've read that it is memory leaks. Whats the cure?

Aperture is doing crazy things while editing like leaving spots on faces when using skin smoothing tool among other things. Closing and reopening fixes it but how annoying. I've read that it is caused from memory leaks. What do I do to fix this?

What is your Aperture version?
And your MacOS X version?
With Aperture 3 make sure you have the latest versions, Aperture 3.5.1 and OS 10.9.3.
The memory leaks you are referring to occurred with MacOS 10.9.1 and onscreen proofing enabled.
If yor versions are current, check your plug-ins for compatibility.

Cropping Crashes Aperture 3 due to Video Card Memory Leak?

Recently after updating from 3.1.1 to 3.1.2 I have been experiencing crashing issues whenever I perform the cropping action. I see the death of wheel following hitting the return key. There was one time when the master version itself vaporized into thin air. I also noticed from the iStat Menus that the issue only occurs when the ATI Radeon HD 2400 memory usage has reach its full capcity. I quite firefox to release some of the memory then Aperture functions normally until the memory runs out again. I would then see the death of wheel once again when I crop.
Is Aperture crashing because I need a more powerful video card or is it a memory leak issue with the application?
Thanks!
iMac (Early 2008)
2.4 GHz Intel Core Duo
4 GB 800 MHz DDR2 SDRAM
ATI Radeon HD 2400

Frank Caggiano wrote:
Lets see if we understand this correctly.
You had a system on which Aperture was crashing when you used the crop tool. You then got a brand new system and the crop tool still causes Aperture to crash. Am I correct so far?
What are the common factors between the old and new systems as far as Aperture goes? Not knowing how you migrated from the old to the new the only thing we can say for certain is that the library is identical.
So have you run the basic library first aid steps? Another thing to try is to create a new empty library, put an image into it and try cropping it and see what happens.
Let us know what happens after those steps,
regards
Frank Caggiano wrote: Lets see if we understand this correctly. You had a system on which Aperture was crashing when you used the crop tool. You then got a brand new system and the crop tool still causes Aperture to crash. Am I correct so far? What are the common factors between the old and new systems as far as Aperture goes? Not knowing how you migrated from the old to the new the only thing we can say for certain is that the library is identical. So have you run the basic library first aid steps? Another thing to try is to create a new empty library, put an image into it and try cropping it and see what happens. Let us know what happens after those steps, regards
I migrated everything from the old computer to the new. I also tried creating a new library and the issue persists. I've also tried the First Aid options all of 'Repair Permission, Repair Database, and Rebuild Database' none of which worked. I've also tried reinstalling Aperture and it crashes on the first crop.
I will need to be editing many photos in a few weeks and now I'm stuck with this issue.. HELP!!!!!!!
It seems like others have run into the same issue also but no solutions!!
Why is aperture 3.1 crashing after cropping images, any one else?
http://www.google.com.hk/url?sa=t&source=web&cd=1&ved=0CBsQFjAA&url=https%3A%2F% 2Fdiscussions.apple.com%2Fthread%2F2642858%3Fstart%3D15%26tstart%3D0&ei=axUETrC0 DM3ciAL23ZXZDQ&usg=AFQjCNE9Kv1N--m8mCyaRkyWi3E9d-0aXg&sig2=qzgEONrK7vLfWetcPT69y A

How do I report a major memory leak problem with Firefox 3.6.10 in WinXP?

After I installed Firefox 3.6.9 on a WinXP desktop, I occasionally had minor memory leak problems, reflected by getting "out of virtual memory" messages. I upgraded to 3.6.10 when notified that it was available and that it supposedly fixed stability problems. Ever since then, whenever I use Firefox, it starts out quick as a flash, but very rapidly slows down to a crawl, and has twice brought my system to a halt. IE does not cause this, nor any other program I use, but the execution speed of all programs slows as badly as Firefox. If I knew where to get older versions, I would back up to 3.6.9 or earlier. The situation now prevents me from using Firefox much at all.

Im running windows 7, Firefox 3.6.10 and before i updated to 3.6.10 my CPU never went above 10% with Firefox open. Now it can spike well above 50% and i have nothing different from when i had 3.6.9 to now when i have 3.6.10.
There is no evidence for me to suggest one of the additions i have is causing it, its all pointing to Firefox itself and the last update.

Aperture Memory Management (swapping)

Hi
I have two Macbooks (early 2011 and Macbook Retina both 8GB RAM) with Mountain Lion installed and Aperture 3.3.2 on it.
If I only switch from photo to photo in Aperture it is after some pictures (100 sitches) extreamly slow..
So I looked to the activty montior and saw that the swap space was more than 2GB in use.
The joke is that the activty monitore said, that is a lot of memory is free.. Page in page out makes the system slow...
So I disabled the swap and try it again. The result:
Aperture is the only program that causes this behavior on both macbooks, it consumes too much memory.
If I use Iphoto with the same pictures, it is fast and the memory cosumion is good (no loading cricle etc).
I the OS community a user has the effect that hes has a lot of Memory but it also swap, in his activty monitor screenshot he has aperture running too :-)
There is a memory leak or something else in Aperture 3.3.2 ?
Regards
Frank

Hi Léonie
The face detecion is not activated and Apperture is idle. What I can see is that he uses ~28% CPU for every picture switch (temporary).
If I use Apertue I see that in the messages
macx_swapon SUCCESS
memorystatus_thread: idle exiting pid 4102 [com.apple.qtkits]
(default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
macx_swapon SUCCESS
After ~30 switches in Aperture, he paged out 52,6 M but 2GB are free..
I run a repair on the Aperture like you suggest and I exported some pictures and imported then as a new project (to sort out RAW).
I did some testing... It looks like that Aperture hold many data in the memory, he clesans up the memory very late in special in the splited view. Iphoto has not this behavior, if you switch the photo the memory consumtion ist stable. Aperture I get a load circle if I switch the picture many times (fast switching) Iphoto I get a direct response.
Regards
Frank

Is this a memory leak issue ?

We are using Jdev10g + BC4J + Struts + JSP to build our enterprise application,
but when the application running some days in our Application Server(RedHat AS3-86, with 4GB RAM), the memory consumed is serious ! we doubt and worry
about maybe our application suffer the memory leak problem, so we want to know have the command to find out whether our application caused the memory leak
issue and which program is the major murderer for memory.
In EM console , the memory utilization chart have big memory consumed in "other" legend ? the "other" legend is mean what ? I cannot find the consumer process in system level through ps command ? it seems disapear ! but after I reboot the server , the "other" legend is clear !

The second scenario is, as we perform some deployment activity on 10g, the memory usage chart shows a sharp consumption of memory about 1.5GB .the loss memory almost be display in "other" legend chart !
Please give us some advice , thanks in advance

Memory leak using pthreads on Solaris 7

I'm on Solaris 7
uname -a:
SunOS zelda 5.7 Generic_106541-18 sun4u sparc SUNW,Ultra-250
compiling with g++ (2.95.2)
purify 5.2
I consistently get memory leaks related (apparently)
to the pthreads lib. I've set the error reporting chain length to 30 (way big), the start of the chain in every case starts with threadstart [ libthread.so.1 ]
when I end my process, I Join the threads before deleting them. What else can I do to get rid of these leaks?
thanks,
rich

is it worth upgrading to a 64 bit OS with more ram.
Well you're talking a fairly hefty investment in fact your best bets buying a new machine at that point since the motherboard would need to be upgraded as well as memory and OS.
Now I run on a 64 bit OS 12 gigs of ram, but i love my plug-ins, and most are 32 bit, so you would still be using the 32 bit Photoshop if you want the majority of all plugins for photoshop to work. Well while the 32 bit version still have the memory limitations on how much memory it can use, Because its in the 64 bit OS, you have available the full amount of that limitation available to the application.
I can run several different memory intensive applications at one time and normally not have an issue. I say normally cause, sometimes i will crash my graphics driver if i open one too many 3d apps hooked into the Nvidia drivers.
I normally only reboot maybe once a week.
So in short, would it help you to be able to go 64 bit with more ram, Most Certainly even more so if you could care less about plug-ins and want to use the 64 bit version. should you go to 16 gigs of ram.. That depends on your budget really,
Personally I always plan to upgrade when I build my systems, Putting in the largest chips you can with out filling all the slots leaving room for upgrading if needed. that way you're not filling all your slots with cheaper lower memory ram that you would have to replace them all to upgrade.
Hope this helps a bit

Memory Leak in WindowsTreeUI?

I'm hunting memory leaks in my app (of which there are alarmingly many), and have just stumbled across one which appears to be a bug in the class com.sun.java.swing.plaf.windows.WindowsTreeUI
When the tree is populated, each treenode contains a reference to a node in our own rather large data structure.
When we close the application-level model, we also call tree.setModel(null) and expect the tree to lose all its references. From a memory management point of view, it is important that the entire old model goes out of scope before we start loading a new one.
If the tree is visible, everything works as expected.
But if the tree is not visible (but still in scope) e.g. because we overlay a component in a JLayeredPanel, we get some dangling references in the (private) drawingCache member of the WindowsTreeUI class. And a single dangling reference keeps the whole caboodle in scope until something else comes along.
I have a bad feeling I'm going to have code around painfully by substitiuting in some lite dummy model and then modifying all the event handlers that get confused as a result.
Or does anyone have a bright idea how I can persuade the drawingCache to flush itself (presumably this only happens on windows)?
Ian

I also had a similar problem. My app has a number of large jtrees (200-300 nodes) with other data objects attached. I was doing a simple null of the JTree thinking that it would be GC'd. Using the NetBeans profiler I could see that it never went away. I found one location where I was temporarily hang on to node references within Swing controls. I've eliminated those. I then released the listeners I specifically assigned. There seems to be other listeners hanging on to node references. I have found little in the way of documentation or advice on how to clean these up. As a work around, when I'm done with a JTree, I traverse the nodes bottom up and remove each node from its parent (DefaultMutableTreeNode - removeNodeFromParent() ). This seems to work. The NetBeans profiler shows the vast majority of the JTree objects as GC'd. I'm sure this is not a perfect solution but it seems to be serviceable.
I would appreciate hearing about any experiences in getting JTrees to GC.

Memory Leak in Applet

Hello Good people,
I am facing a troubling memory problem in my applet.
Apparently, it suffers from some major memory leaks and every time I reload my applet the memory is consumed with additional 5Mb. I am looking for ways to work around this (or better yet to completely solve it) - I've noticed that the JVM is still alive when the applet is disposed and destroyed, it is not being killed until I close the parent IE windows. Because of this, the heap of the JVM is never totally cleaned and after several applet invocations I get to the heap's limit and everything is stuck.
I am looking for ways to control the JVM - is there a way to manually reset its memory or even kill it through javascript after the applet is disposed?
Thanks a lot!
Tal

Hi Andrew,
I appreciate your help but I remember that in the research I did when I just started the project I have found that the web start technology is not suitable to me because it always open a new window and I need my applet to be embeded in an exisitng window.
Do you know differently?
Thanks,
Tal

Whether our application caused the memory leak

whether have the command to find out whether our application caused the memory leak !
We are using Jdev10g + JHeadstart(Release 9.0.5.1, BC4J + Struts + JSP) to build our enterprise application,
but when the application running some days in our Application Server(RedHat AMD64, with 8GB RAM), the memory consumed was growth seriously in production environment (one OC4J instance will caused almost 2G memory ulilization after running 2 days) that is caused us to restart the instance each day ! we doubt and worry
about maybe our application suffer the memory leak problem, so we want to know have the command to find out whether our application caused the memory leak
issue and which program is the major murderer for memory.

Ting,
Unfortunately there is no 'command' that will show you the location of a memory leak. First I would scrutinizing your code for any obvious 'leaks'. Then, you should obtain some statistics about the usage of your system. One important aspect is how long a HttpSession usually lives. If you have thousands of users that stay online the entire day and never 'time out', and if you have users on the system 24 hours a day, then the sheer number of HttpSessions might be a problem.
JHeadstart 9.0.x tends to have rather 'heavy' session objects. This can easily be solved by adding some actions to clear up DataObjects and DataObjectSets of previous 'Groups' when entering a new Group. A good place would be between the 'DynamicActionRouter' and the 'ActionRouters'. Just before entering the 'EmployeeActionRouter', you could remove all DataObjects and DataObjectSets that might be left on the Session by actions of the other ActionRouters.
Also it would be interesting to see if the garbage collector can do its thing when the system is less busy. For instance, if your application has a smaller load during the weekend, what is the memory usage on Sunday at midnight compared to, say, Friday at noon. Has the memory load dropped consistently with the decreased number of online users, or does too much memory stay allocated? If so, then there's more going on than just HttpSession objects.
If all this does not lead to a solution, I suggest using a profiling tool such as OptimizeIt to investigate the memory usage of the application in detail.
Kind regards,
Peter Ebell
JHeadstart Team

Memory leaks in Lion?

I have a 2008 21-inch iMac, and a 2010 MacBook Pro, both with 4 GB RAM, running OS X Lion 10.7.3. Ever since I installed Lion, I've had this problem of available memory dwindling to almost nothing (10-20 MB) after a day or so of usage. Last night I went to bed and the MacBook Pro had 400 MB available (according to Activity Monitor) and when I woke up this morning it was nearly frozen with only 10 MB available.
I'm not an extreme techie but I've been working in the IT world for over 30 years, including 3 years with Apple, and in my experience this situation is called a Memory Leak. If it were just one of my systems I would suspect something local, but they both behave the same way. (My partner's machine does the same thing.) I've installed the 3rd-party app Memory Freer, which frees up 6-800 GB each time I run it. But as time goes on the memory fills back up again more quickly, and finally I have to reboot.
Checking Activity Monitor, it's not just one app that takes up memory - they all seem to grow over time. (Mail, iPhoto, iTunes, Word, Chrome, etc.) Chrome seems to be the worst offender, with a plethora of Worker and Renderer processes grabbing 10-80 MBs for each open window - and I often leave 10-15 open at any given time. But all apps' memory usage grows over time, even if I haven't accessed them - witness last night's spontaneous bloat on my MacBook.
I've read a couple of other threads on Memory Leaks, but most point to a single app or just suggest Memory Freer. Does Apple know it's got a major league problem here? Are they doing anything about it?
One other point - I get the spinning ball on a lot of tasks, most often with Word and and Excel re-calc, which can last 3-5 seconds, and is another indicator of system overload, even when I've cleared the memory with MemoryFreer and there is supposedly several hundred GB of RAM available. This issue lessens after reboot, but is almost constant with Microsoft Office apps.

LKHill wrote:
I tried the kextstat message and the response was:
Index Refs Address Size Wired Name (Version) <Linked Against>
which apparently indicates that there are no kernel extensions running.
That means you don't hve any non-Apple kernel extension. There are still lots of other possibilities for third party interference. Are you running any kind of anti-virus or clean-up software? Those aren't needed and will likely just cause problems.
I understand what you're all saying about unused memory going to waste, but for MacOS to operate "correctly" it would need to free up previously-allocated memory as it is needed by other or new applications, and it doesn't seem to be doing that. It's just acting like it's out of memory, with all processes slowing to a crawl.
"Free"? You are still looking at memory. If all processes are slowing to a crawl, then that is a problem worth investigating. If you can't get past the assumption that memory is the cause, you'll never figure it out.
I did check CPU utilization as well, and it's rarely over 25%. However, on one of my systems, Page Outs were about equal to Page Ins, substantially over the 10% "healthy" threshold that was suggested. So I upgraded to 10.7.4, and Page Outs are down in the acceptable range. The overnight bloat also seems to have gone away, but each app still creeps up with time, albeit more slowly now.
I too would like to return to the days of 10.6 where I didn't reboot for days - or weeks - and Microsoft apps didn't display spinning wheels with each reactivation task or any simple calculation or text move.
So, in other words, you fixed the memory problem but the performance issues remain. That tells me that it isn't a memory problem.
Also, because you seem unwilling to look past memory, I'm unwilling to accept your CPU usage claims. Sometimes it takes several attempts before I can get people to setup Activity Monitor correctly to see exactly what is going on with their systems. That is step 1. We haven't made it to step 1 yet.
It seems clear that Lion's new process model is at least partially to blame here. With two completely different systems running (work MacBook, home iMac) plus my work partner's MacBook experiencing all the same symptoms, it's not likely my own setup. So I've also ordered an upgrade to 8 GB RAM.
Here's the rub. If low memory isn't the cause, buying more won't help.
I guess I'm just not accustomed to hating a new MacOS release, but between these performance problems and the inexplicable need to Duplicate TextEdit documents in order to do a Save-As (yeah, I know, Versioning is a great idea, blah blah - please get rid of it anyway) I really, really hate Lion.
It's just an operating system and doesn't care how you feel. I strongly suspect that feeling is more the explanation of any issues you have. I hate Linux. I really do. Therefore, I don't use it. While I would love to help you figure out what is wrong with your machine, that will only work if you meet me halfway and help look. If you have already identified the cause, then you don't need my help. The problem is Lion. Erase your hard drive and the problem will be gone.

Memory leak when LineUnavailableException thrown

I think I've found a Java bug that I'd like to run past you folks first before submitting it; perhaps you've come across this and can confirm it also?
I play audio clips (using javax.sound in 1.3.1_02 and 1.4.0-b92) in my app on certain events but if the audio system is unavailable a LineUnavailableException gets thrown when I do clip.open(stream). I retry playing the audio pausing each time, until I reach a timeout and then give up.
Every time the exception is thrown I can see the JVM swallow more memory (about 500k on WinNT 4.0); which is a major problem if the app ends up retrying lots of audio.
This is VERY easy to reproduce with the Java Sound Demo! All you need do is keep the audio system busy - play some MP3s/a CD etc then set up some AU/WAVs in the Java Sound Demo on a loop and watch it throw LineUnavailableExceptions in your cmd window! Bring up Task Manager then watch the JVM grow in size as it gobbles up memory and doesn't release it. It'll go from 15Mb to 50Mb in 60 seconds. It also seems to bypass the -Xmx max JVM memory setting also, presumably due to the allocs happening in native code??
Anyone else seen this or care to reproduce just in case I'm going mad?
cheers,
- Justin

Note that there was a similar bug reported which this seems very related to...
"Memory leaks on opening and closing source DataLines"
http://developer.java.sun.com/developer/bugParade/bugs/4319431.html
- Justin

How to track Memory Leaks in 3.6.8?

I've been noticing for several updates now that I seem to be getting major memory leaks. Firefox starts off around 1-200,000 K memory usage in task manager, but within a few hours it will be past 800,000 K. Now, the things I've seen so far talk about disabling plugins and all to find the problem, but this doesn't happen immediately, so disabling things one by one isn't very feasible. How can i track the memory leak to a specific plugin, or else make it leak much, much faster so I can do the one by one thing?
== This happened ==
Every time Firefox opened
== A few updates ago

Well, It just has taken a turn for the worse... In the attached screenshot you can see firefox took 1.123.112kb out of my memory at which point the GUI became unresponsive. This has actually happened before, but not as soon...
I had 18 tabs open (but at the moment I have all of them opened again after a restart of firefox and it takes 143.988 kb at this very moment, which still is a lot actually). My computer has 4gb RAM-memory of which 46% is in use at the moment according to windows task manager.
It would be great if the whole tabstructure and maybe the garbage collector for the TraceMonkey javascript engine was reviewed... This might point out where the memory leaks are located.

Find out whether our application caused the memory leak

whether have the command to find out whether our application caused the memory leak !
We are using Jdev10g + BC4J + Struts + JSP to build our enterprise application,
but when the application running some days in our Application Server(RedHat AS3-86, with 4GB RAM), the memory consumed is serious ! we doubt and worry
about maybe our application suffer the memory leak problem, so we want to know have the command to find out whether our application caused the memory leak
issue and which program is the major murderer for memory.

The second scenario is, as we perform some deployment activity on 10g, the memory usage chart shows a sharp consumption of memory about 1.5GB .the loss memory almost be display in "other" legend chart !
Please give us some advice , thanks in advance

[Bug?] X-Control Memory Leak with Large Data Array

[LV2009]
[Cross-posted to LAVA]
I have found that if I pass a large data array (~4MB in this example) into an X-Control, it causes massive memory allocations (1 GB+).
Is this a known issue?
The X-Control in the video was created, then the Data.ctl was changed to 2D Array - it has not been edited in any other way.
I also compare the allocations to that of a native 2D Array (which is only ~4MB).
Note: I jiggled the Windows Task Manager about so that JING would update correctly, its a bit slow, but it essentially just keeps rolling up and doesn't stop.
Demo code attached.
Cheers
-JG
Unable to display content. Adobe Flash is required.
Certified LabVIEW Architect * LabVIEW Champion
Attachments:
X Control Bug [LV2009].zip ‏42 KB

Hi Jon (cool name)
Thank you very much for your reply. We came to this conclusion in the cross post and it is good to have it confirmed by LabVIEW R&D. Your response is also similar to that of my AE which I got this morning as well - see below:
Note: Your reference number is included in the Subject field of this
message. It is very important that you do not remove or modify this
reference number, or your message may be returned to you.
Hi Jon,
You probably found some information from the forum. The US engineer has gotten back and he said that unfortunately that's expected behaviour after they have conducted some tests and this is what he replied:
"X Controls in the background use events structures. In particular the Data Change Event is called when the value of the XControl changes (writing to the terminal, local variable, or value change property). What is happening in this case is the XControl is getting called to fast with a large set of data that the event structure is queuing the events and data that a memory leak is produced. It is, unfortunately, expect behavior. The main work around for the customer in this case is not call the XControl as often. Another possibility is to use the Synchronous Display Property to defer updates to the Xcontrol, this might slow down a leak."
He would also like to know if you can provide with more details how you are using the Xcontrol, perhaps there is a better way. Please refer to the link below for synchronous display. Thank you.
http://zone.ni.com/reference/en-XX/help/371361G-01/lvprop/control_synchronous_display/
In my application I updated the X-Control @ 1Hz and it allocated at MBs/s up to 1+GB before it crashed, all within a few hours. That is why I called it a leak. I am really worried that if this CAR gets killed, there will still be an issue lingering that makes using X-Controls a major problem under the above conditions. I have had to pull two sets of libraries from my code because of this - when they got replaced with native LabVIEW controls the leak when away (but I lost reuse and encapsulation etc...).
Anyways, I really want to use X-Control tho (now and in the future) as I like all other aspect of them. If you do not consider this a leak, can a different #CAR be raised that may modify the existing behavior? I offer the suggestion (in the cross-post) that the data be ignored rather than queued? Similar to Christian's idea, but for X-Controls. Maybe as an option?
I look forward to discussing this with you further.
Regards
-Jon
Certified LabVIEW Architect * LabVIEW Champion

Major Aperture 3 memory leak

Similar Messages

Maybe you are looking for