Messages app memory leak

I notice when I leave Messages running, it begins to take massive amounts of RAM. I have 16 GB of RAM on my iMac, and I just sat at my computer see Messages using 12.58 GB of RAM according to Activity Monitor. That is absurd! It made my computer completely unusable (took lots of time just to get the computer to make a screen grab).
What should I do? This keeps happening.

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
Test while in safe mode. Same problem?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

Similar Messages

App Memory Leak When Open iPhoto

Hi everyone,
Does anyone have experienced app memory leak when open iPhoto? My free memory immediate dropped from 5000 mb to 15mb when I open iPhoto and the app never open. If I force to quit iPhoto, all return to normal and everything work fine. I only have iPhoto app running, not sure what caused the memory leak???
Looking for help.
Thanks
JHML

Actually the new library was a test to see if the problem occurred only with your current library or with all libraries. The fact that switching libraries cleared up the problem is just serendipitous.

Yosemite - Mail.app memory leak

I'm seeing a recurring issue with Mail.app taking up huge amounts of RAM memory. There's evidently a serious memory leak in Yosemite Mail. On three occasions today, I noticed my free memory below 20 MB (I have 16GB). Activity Monitor shows the culprit to be Mail.app taking any where from 20-65GB of memory! I've had to quit Mail and restart it, only to have the same issue surface later. Does anyone have a way to mitigate/resolve this issue?

I apologize this is not the Discussion that has all the solutions. It's this one:
Yosemite OS 10.10 Mail Memory Leak
There are 19 pages so far, I'll see if I can find my post with the suggestions. Found it, it was on page 7. Here ya go. Hope it works!
Doren_Sean_Michael
Oct 23, 2014 8:47 PM
Re: Yosemite OS 10.10 Mail Memory Leak
Re: Yosemite OS 10.10 Mail Memory Leak
in response to Doug Lerner2
Thanks mlwebber & etresoft. I think we were able to narrow down the 4 most effective methods of temporarily resolving this issue it seems. I only had to disable the drafts to get back to normal, but others are reporting that using that in conjunction with a combination of 3 of the other methods from mlwebber are resolving their issues. Albeit this is only a temp fix until Apple updates their software & truly fixes this bug/issue, but, at least, I hope, we all can get back to business as normal for the time being.
Doren (from etresoft’s observations):
- Preferences/Accounts/Mailbox Behaviors: UNCHECK “Store draft messages on the server”
mlwebber:
- Preferences/Accounts/Advanced: UNCHECK “Use IDLE command if the server supports it”
- Preferences/General/Check for new messages: “Every 5 minutes”
- Preferences/Junk Mail: UNCHECK “Enable junk mail filtering”
Please post in this discussion if none of these methods help you and we'll see what we can do. We'd also love to know if these methods also resolve your issue. Thank you.

Mail app memory leak affecting business productivity

Ever since upgrading both my 27" iMac (late 2012, i7, 3.4 Ghz, 32 Gb RAM, 3 Tb hybrid HDD) and my 15" MBP (late 2011, i7, 2.5 Ghz, 8 Gb RAM, 750 Gb HDD) using Mail has become almost impossible. Both machines experience severe memory issues when using Mail. It is not uncommon that Mail hogs between 90 and 95 Gb of memory (seen in Activity Monitor). The app crashes several times every day, sometimes multiple times per hour.
Going on more than four weeks since the upgrade and the problem started, this is really affecting my business productivity.
I have tried many of the suggested solutions found on different forums, e.g. checking for add-ons, which I don't have. Also checking my one GoDaddy account settings which is using IMAP port 993 and never changed during installation, which some have experiences. Use SSL is checked.
Today Mail crashed multiple times and a 49 page crash report was generated.
I need this issue solved. If anyone has a real solution, I would greatly appreciate if it could be shared here.

I don't know if there's a "real" solution yet. There seems to be a very specific problem with the Mail application and GoDaddy's IMAP service. That it happens _only_ with GoDaddy would maybe indicate that the GoDaddy server is doing something strange (i.e. operating differently to other IMAP servers), and whatever it's doing causes Mail to go berserk.
Probably best to sit tight and hope that Apple fixes this in an OS X release. It seems like in the past there has been a first update out around a month give or take after an OS release, so fingers crossed.
Stuff you could probably do in the interim:
* Disable the GoDaddy IMAP account in Mail and use their webmail
* Use another IMAP client (Mailmate looks nice) in 30-day trial mode and hope it gets you through
There are probably more options, but they're all variations on the same theme.

Mail.app memory leak. RAM use increases until system is no longer usable

I am having this problem since a week ago more less.
Mail keeps increasing the memory use from a starting 100 Megas. Increasing something like 100 megas each 10 minutes, until the whole system is unresponsive.
Any ideas?
Thanks!
PD: I have 3 IMAP accounts and 1 POP. In total 3348 messages. Running 10.5.4

Thank for the fast reply!
Indeed it happened to me. Whenever I dropped a file to the icon it would just hang up the computer. Then I removed my custom plugins (3 columns plugin, and Encryption plugin , I thing). And it worked well. Or at least I could drop files to the Mail Dock icon.
My impression is that it might be related with IMAP and Gmail. I have 3 Gmail accounts. One of them is my primary email account, it has many many mail. The "all Mail" folder is a big one and probably Mail is trying to catch everything. It does so slowly in the background, creating the problem. May be. Just in case I selected the option not to download attachment in mails.
Other suspect is the iGTD program I have been using. It syncs with Calendar and the ToDo folder in Mail. But the problem is still there even if iGTD is not working.
I remember reading something about email with attachment that had numbers on the title, or something like that. It would create a similar problem but I can´t find it now.
I have tried to control the output from "lsof | grep Mail" and "fs_usage -w -f filesys Mail" but I can´t find anything suspicius (not that I am an expert on that, though)
THANKS a lot for the help.

Mail.app Memory Leak

While sending a photo heavy (200 small images @ a total of 12.6 mb) my mail app crashed, and now when I start it I see in iCleanMemory that it quickly grabs up all the resources, which brings my iMac to a grinding halt.
Are there any fixes anyone knows of? I trashed all my plist files from the MailData folder, but it didn't work. I went to see if I could re-download and install Lion from the App Store, but do not see a way to reinstall from there.

Another strange thing as I have tried to correct this problem manually (including starting in SAFE Mode) is that my home Library is hidden. Is this something particular to 10.7.1? I have to access my email attachments in a search in order to get to my Mail folder in the Library.

App performs inconsistantly...how to check for memory leaks?

I (was!) almost done with an app to submit to the app store but when I tested the final build on my iPad it started performing strangely.
It had never done this before, but it's crashing almost CONSTANTLY. Every few seconds or so. I haven't changed much of anything since the last time I tested it and I can't really figure out what would cause it to crash so much.
From the menu you can choose a button to go to other frames in the main timeline. Half of those work, half of them make the app crash. This is new and I think I might have a memory leak somewhere because it's consistently inconsistent.
At first I thought I had a stack overflow somewhere; however, testing in mobile debug mode doesn't cause any errors or even warning output messages - nothing. It runs just fine.
So is it possible that the problem is stemming from hardware? I can't imagine this app would be using up too much memory - it is full of vectors, but there's nothing more complicated than touch and drag because it's just a puzzle.
How would I test something like this if debug mode isn't throwing any exceptions?

You may want to try MonsterDebugger (free, open source). It also serves as a profiler. You might be able to get a better understanding on what your app is doing (and why it might be breaking on the iPad).

Memory Leak in Preview.app when switching Display Profiles

I found a weird memory leak in Max OS X Preview.app, which manifests itself when Display profiles (color calbration) is change. I wonder if anyone else can reproduce my experience.
1. Open up "System Preferences" -> "Displays", switch to the "Color" tab. You'll need at least 2 available profiles in the list. (If you only have 1, you can create another using "Calibrate..." button to launch Display Calibration Assistant.
2. Open an image file in Preview.app. The larger, the better. Zoom in full size to maximize the effect of the bug. I repro'ed easily with this image: http://www.donporter.net/NewSchool/Color/Examples/Printer%20Test%20file.jpg
3. Open up "Activity Monitor.app", and click on Preview to highlight it, so you can watch its memory usage.
4. Switch back to "Diplays" Preference Pane. Using the arrow keys, toggle up and down between two different Display profiles.
4a. At the same time, watch Preview's "Real Mem" in Activity Monitor, as well as the total "Active" memory.
5. Each time you switch profiles, Preview consumes more Active/Real memory, about 25MB per switch in my case. This continues until all physical memory is consumed, and then (I presume) starts swapping virtual memory to disk.
6. Bring Preview to foreground, and all the profile-induced memory usage is freed.
Weird, wild stuff.

Could it be possible that this is just the OS holding the memory for the app until another process requires it? Do you find that the memory increase eventually causes the app to become unstable?
It might be best to open a new bug report on this over at bugbase.adobe.com. When adding the bug, please include any source code, project or installer that will help us reproduce the issue internally. If you'd like to keep your code private, feel free to email it directly to [email protected] Once entered, please post back with the URL so that others effected can add their comments and votes.
Thanks,
Chris

Memory Leaking message when run the log in page in Jdev 11.1.2

Hi
I am re design our 10g application in Jdev 11.1.2, I am using .jsf and ADF business component.
at the moment, the project has only two pages. login and home page.
when I run the login page, I see the message below. this is happening during the deployment process to the embeded weblogic
<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
Anyone know why?
thanks

Hi Timo
Thanks for your reply, I read the thread you pointed to.
however, I am not sure my is related to the case mentioned. I am re design the application from scratch in Jdev 11.1.2, and my adfc-config.xml is as simple as this:
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<view id="Login">
<page>/commom/Login.jsf</page>
</view>
<view id="home">
<page>/commom/home.jsf</page>
</view>
<control-flow-rule id="__2">
<from-activity-id>*</from-activity-id>
<control-flow-case id="__3">
<to-activity-id>Login</to-activity-id>
</control-flow-case>
</control-flow-rule>
<control-flow-rule id="__4">
<from-activity-id>Login</from-activity-id>
<control-flow-case id="__5">
<from-outcome>success</from-outcome>
<to-activity-id>home</to-activity-id>
</control-flow-case>
</control-flow-rule>
<managed-bean id="__1">
<managed-bean-name>backing_login</managed-bean-name>
<managed-bean-class>com.mycompany.view.backing.login</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
</adfc-config>
also, I am using a session filter registered in web.xml --- basically, if the page is not Login.jsf then redirect to Login.jsf page. but even though I removed the session filter.java from the web.xml , it still show the message.

Memory leak issue in iPhone app

We developed a little program to display PDF's on the iPhone, but it's crashing after scrolling through xx number of pages with low memory error. The app runs fine in the simulator but crashes on the original iphone. I ran the memory leak debugger tool from xcode and got the following:
http://picasaweb.google.com/momopi/MiscCollection#5384555524546579922
(click on magnify glass tool to zoom in)
Weird part is when I run the same on iphone simulator I only get 2 small memory leak warnings (128 bytes each), but on the iphone I get a lot more warnings and it crashes.
Has anyone seen anything like this?

Perhaps you don't have any meaningful leaks. Your program could simply consume too much memory. It has been many years since keeping a small memory footprint was important. Now that Apple has thrown embedded programming to the masses, everyone has forgotten about that.

JSF (RI) app hot-deploy memory leak

I have a standard JSF (RI) based web app that appears to be working just fine in terms of functionality. However, I believe that there is a memory leak associated with the sort of frequent hot-deploy cycles that are typical during a normal development cycle. I have been monitoring the app via the jvmstat 3.0 tools and have witnessed NO memory growth in the young or old generation areas - regardless of useage pattern. All of the growth seems to happen in the perm area of memory and be directly coincidental with the occurence of a deploy. Eventually, continued hot-deply cycles will result in an OutOfMemory error on the container - please note that continued and extensive use of the app WITHOUT the aforementioned hot-deploys does NOT result in the OutOfMemory error.
From my research so far, I have discovered the following thread:
http://forum.hibernate.org/viewtopic.php?t=935948&postdays=0&postorder=asc&start=75
It refers to a similar problem with hiberate (which I am NOT using) as well as a commons-logging and several others. From the looks of it, I strongly suspect that there may be an issue with JSF when it's implementation is bundled inside the WEB-INF/lib dir - i.e. inside the specific web app's ClassLoader.
Based on the above, I have implemented a SessionContextListener that invokes the org.apache.commons.logging.LogFactory.release() inside the contextDestroyed( ServletContextEvent e ) method. This does appear to free up some perm memory but there is still large growth that appears to be directly related to the FacesServlet initialization (navigation handlers, etc). I looked into calling the FacesContext.release() method which seems to have purpose similar to that of the LogFactory.release() method. However, at the time of the contextDestroyed() invocation, FacesContext.getCurrentInstance() always returns null, so I do not ever have an opportunity to invoke the release method that I am aware of. If my suspicions are correct, than I would likely be able to avoid this problem entirely by simply placing the JSF implementation jars in the conatiner's shared lib dir - instead of bundling it inside WEB-INF/lib. However, this is not an option for this container as multiple web apps (which require the flexibility to use differing JSF implementations and versions - i.e. RI vs MyFaces, etc) will run on this container.
I don't believe it is at all related to the problem at hand, but my container is JBoss 4.0.2.
Any and all assistance and suggestion will be greatly appreciated! Has anyone else seen this sort of behavior? Are there any work arounds or corrective actions?
TIA

Has anyone else run into this? I'd greatly appreciate any assistance as I cannot seem to resolve this hot-deploy related leak.

Fixing Memory Leaks in AIR App?

Hi Friends,
I'm been facing this memory leaks issue in our app and this has taken enough of our time and resources and we are not being able to find a solution for it.
I have identified the problem in the module where we primarily need memory related fixes which is - We are setting Repeater's recycleChildren() property to true/false based upon certain conditions which we cant change. Now when this property is set to false Repeater is supposed to be removing its last created objects from memory and creating fresh ones. In our case repeater is unable to delete those. When I managed to get their instances (using createdChildren()) and freed them in code I called System.gc() for releasing the memory back to OS. Now what is happening is that this approach works fine when I run the app from code but when I create its installer (from Installsheild) and formally out in on machines it does not work. I came to know the reason from following blogs:
http://jvalentino.blogspot.com/2009/05/flex-memory-issue-3-garbage-collection.html
http://gskinner.com/blog/archives/2006/06/as3_resource_ma.html
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/System.htm l#gc()
http://stackoverflow.com/questions/192373/force-garbage-collection-in-as3
http://gskinner.com/blog/archives/2006/08/as3_resource_ma_2.html
Guys, can anyone of you suggest what should I do here? This has become a delivery bottleneck and we need to give a fix where the memroy is released periodically and efficiently so that the end user's system does not hang.
Please help.
Shubhra

Are you sure it doesn't ? Maybe flash does release memory but the OS leaves it assigned as described in the below comment from http://www.mikechambers.com/blog/2008/08/06/what-are-your-biggest-issues-with-adobe-air/co mment-page-3/#comment-26330
"I just finished doing more experiments, I looks like the AIR app does free the memory, but the OS leaves it assignned to the app process, until other apps requiere that memory. So, looks like it is a natural behaviour and the memory leak is not as terrible as I thougth."

Can I locate "memory leaks" to keep apps from crashing?

Hello clever people,
Since the iPhone 4s is still on the market, I assume that my 2 year old 4s should be able to work fine. However, I am constantly plagued by apps crashing and, most frustratingly, apps often fail to remain running in the background, even with one or no other apps running.
I had a similar issue with my iPad2, just before it ran out of applecare, and the chap had me run through with sending anaylitcs to him, and his conclusion was that a few apps were causing 'memory leaks' - had me reset the iPad and reinstall everything. So I also did this on the iPhone, which did help, but it has not solved the issue. I have also removed most apps from the device, in a bid to locate the offending app.
Searching on Google for "memory leak" only brings up info for developers, and nothing for someone who is actually using their phone and having issues. My usual scenario is going for a bike ride and running Strava, which then cuts out when I stop to take a picture - with no other apps running.
Does anyone know how to solve the issue - return the phone to its 'as new' state, or locate the problem and remove it?
Cheers,
Tobias

There are differenty types of, "resets" ..
Have you tried the folloiwng ??
Reset the device:
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
If that doesn't help, tap Settings > General > Reset > Reset All Settings
No data is lost due to a reset.
Use iTunes to restore your iOS device to factory settings

App-V 5.0 memory leak problem & slow program launch

App-V 5 clients with most recent updates have a memory leak problem. Windows 7 64bit workstations with 8GB of memory will be useless within couple of days because memory has run out. Terminating App-V client process will free the memory, but system starts
to consume it again after that. All hotfixes (up to 5) have been installed.
Another problem is that launching some large (locally cached) programs, for example SolidWorks, takes many minutes for a program to start. With 4.6 there wasn't any performance issues.
Any suggestions?

I saw the exact same issue with slow load times and 50% utilization by AppVClient.exe during that time.
AppV 5 first launch application performance
AppV 5 - Measuring RegistryStaging load times
The issue, specifically, is the amount of time the application takes to stage the registry is what causes the slow load and 50% CPU utilization. I've written a script that stages the registry on your behalf that we use on server startup, after all
the packages are loaded.
Original Thread on MS forums:
https://social.technet.microsoft.com/Forums/en-US/44944302-d8f3-4df1-b104-9c63345f88e0/poor-first-launch-performance-with-appv-5?forum=mdopappv

Memory Leak with the new PatchMix App Beta?

E6300/ASUS P5B-D/2GB RAM/EMU 0404/Vista Ultimate 32bit
The problem happens after I upgrade to the PatchMix driver set dated 9/11.
The physical memory usage bumps from ~24M to 150M after running 24 hours, and I didnt load any FX.
The commit size(real memory usage) is over 500M!
This doesnt happen with the old beta driver.
Anyone has the same problem?

Emon wrote:
jreid wrote:
Dare I suggest the problem might be Vista?
Yes? How exactly would Vista cause a memory leak within PatchMix DSP's GUI?
Well, just a thought. The OS is ultimately responsible for all memory management, and also the low-level graphics functions that would be called by e.g. the GUI code. I just noticed that people on XP didn't seem to be having the same problems with this beta.

Messages app memory leak

Similar Messages

Maybe you are looking for