[SOLVED] Strange memory leak

After updating to systemd (maybe after it) strange things with memory:
In one moment count of free memory precipitously start decrease, in 10 seconds in decrease to 0, after it same happen
to swap.
http://i.imgur.com/ANqbn.png
In that screenshot you can see, that top-memory process (luakit) owns only 10% (200mb). I can't say who owns all memory, but this is not one process. Next time I try to get ps all -A output, but its a bit difficult - system hung-up very fast.
Journal log:
https://www.dropbox.com/sh/oq5yk03tzyfj … _crash.log
Watch from start to --Reboot-- line.
My systemd services:
cronie, dhcpcd@eth0, netcfg, remote-fs, wicd.
Packages status:
http://pastebin.com/RRsy0tDw
Used apps:
In one time: luakit, vim, mocp, weechat
Another one: mplayer
Last edited by ShadowPrince (2012-12-15 04:49:07)

Ahahahahahahahahah.
I finnaly got ps -Af output and found there many copies of one script, who runs itself recursively.
That script was binded to cron.hourly, and after hour of work start to multiply.
Yeah, script was mine, I think in one update (when I practice in VIM) I put here that code accidentally.
Anyway, that was fun. Linux rule.

Similar Messages

IOS - Strange memory leak using ABPeoplePickerNavigationController

Hi there!.
I 've read other posts regarding this problem but I wasn't capable of guessing what's going on with this memory leak.
To keep it simple, let's say I have an IBAction which triggers once the user has pressed a button. The code is as follows:
- (IBAction) showBorrowersPicker:(id)sender{
ABPeoplePickerNavigationController *picker =
[[ABPeoplePickerNavigationController alloc] init];
picker.peoplePickerDelegate = self;
[self presentModalViewController:picker animated:YES];
[picker release];
The code works fine but it leaks a small quantity of memory and I can't understand why. I think it's a problem with the ABPeoplePickerNavigationController because if I comment the line "self presentModalViewController.picker animated:YES" it obviously doesn't present the modal view with the AB's contacts but the app continues leaking memory.
I've read it might be a reported bug but the post where I've read it is from 2009 or so. I don't know if the bug persists of, more likely, I'm doing something wrong but I don't know what. I'm releasing the picker instance so I don't know why is it leaking memory.
Running Instruments I get the following info:
Leaked Object: ABStyleProvider
Address: 0x19f810
Size: 16 Bytes
Responsible Library: AddressBookUI
Responsible Frame: +[ABStyleProvider
Any help would be much appreciated!

Hi George,
thank you very much!. I've tried it and seems to work perfectly. No memory leaks at all!. A couple of weeks ago I was working with Apple's QuickContacts source code and it had the same problem with this strange memory leak so I think it's really weird since I can't believe that Apple's engineers would commit such an error... but who knows!
Thank you very much for your help! :-D

[SOLVED] Big Memory Leak with Pacman - Xterm - Openbox

Hi Everyone,
I Don't know if this is the place to post this, and if not please correct me.
I've installed Arch Linux in a virtual machine HDD using VirtualBox on Linux Mint. Then I made a simple install with openbox and slim just to make some testes before putting the all thing in my laptop.
So after installing slim and openbox, i've checked free -m and he noticed me that the system was using 80mb of ram (really cool ^^). Then I start installing some apps just for test.
I start installing libreoffice like this "sudo pacman -S libreoffice", in a xterm terminal and on another xterm terminal I had the fallowing command running "watch free -m" just to see the ram usage evolution...
And then, during downloading/instalations, things became wierd... during download the ram usage start to grow up to 120mb and during instalation the ram usage start's growing more and more, to finish at 770mb !
I doesn't make any sense ! But I don't really know if this is a pacman, openbox or xterm problem :S...
Can someone give me any information about that ?
Thanks in advance !
PS : after a "sudo pacman -Scc" the ram drop at 633mb...
Luis Da Costa
Last edited by aliasbody (2011-07-07 18:33:56)

Leonid.I wrote:
aliasbody wrote:
I'm sorry, I'm not making myself clear - my problem isn't the usage of Swap itself. I know that when RAM reaches its maximum, it uses Swap. I know that. And that's not what I'm "complaining" about.
Problem is - why does updating via pacman uses so much allocated RAM? I think there's a memory leak in here somewhere and that's what I was aiming at - I'm basically asking if it's just me or if this has happened to someone else and if it's really a problem or it has a simple explanation....
Well, pacman's memory usage depends on a particular package in question. Installing TexLive, for instance, takes a tremendous amount of RAM/swap compared to netcfg. Pacman does not simply copy files, but also executes scripts.
It is not true that swap is used when the RAM is full. The kernel decides which data in RAM is relevant and the irrelevant data goes to swap, even if you have 300mb of RAM still available. /proc/sys/vm/swappiness controls this logic.
In your atom netbook you have only 3mb in swap... this can not be the cause of a slowdown.
Thank you for your answer this make me understand more about the all thing ^^
I was just scared about a possibile memory leak, I didn't know that pacman.
Thanks in advance for all, I will marked it as Solved then !

How to solve UIDatePicker memory leak problem in iOS 5.1?

Hi,
I am developing an application in Xcode 4.3.2. There is a page where I am using UIDatePicker to enter DOB (Date of birth). The functionality works fine but I am facing problem of memory leaks with UIDatePicker. I am followed many forums but all they say is, UIDatepicker is faulty component; it is the bug in ios 5.1. Is that correct? Should I not use this component in my application? Can anybody guide me what should I do?
Regards
Anil

It's up to date. Anything else?

How to solve this memory leak???

I've noticed as of recently that my 13" mbp, 2.7ghz, early 2011, OSX Lion 10.7.5 has been getting less and less memory as I use it throughout the day.
I upgraded my memory from 4gb to 8gbs recently thinking this would be the solution, but its still the same problem occuring.
Help please, I have no idea how to solve!

It's up to date. Anything else?

Strange Memory Leak

Our application monitor (Panorama) is showing that our recently deployed ActiveMQ seems to be consuming a lot of memory. We allocated 512MB to the JVM. Within 2 hours it eats all that up and each full GC only frees up about 20% of memory. Over time this gradually decreases.
verbose:gc shows that the heap is less than 100MB and the permgen is only about 50MB. E.g.
10177.573: [Full GC [PSYoungGen: 370K->0K(4480K)] [PSOldGen: 58372K->40910K(55360K)] 58743K->40910K(59840K) [PSPermGen: 29417K->29417K(49728K)]
This doesn't change much over time.
We thought there might be a classloader leak, but verbose:class shows that most of the classes are loaded in the first minute and very little memory has been consumed by then.
This seems to leave hundreds of MBs unaccounted for. Where can this be and how to we look for it?
-- Frank

Hi 835631,
Can you please provide the following:
- JDK vendor and version
- Your JVM start-up arguments e.g. -Xms, -Xmx and more
- 1 verbose GC snapshot right after server restart
- 1 verbose GC snapshot when the memory is running low
It will also help to get a JVM Heap Dump generated. This will provide you with clear view on the your new application Java Heap footprint post MQ implementation.
Keep in mind that messaging system like MQ or pure JMS messaging via MDB can use a lot of Java Heap depending on the tuning settings , # of bean in the pool, # of messages etc.
Regards,
P-H
http://javaeesupportpatterns.blogspot.com/
Edited by: PHCharbonneau on 10-Feb-2011 11:54 AM

Is memory leak Problem Solved in this new FW 4.08...

Hi frnds,This is my very first post. Im happy to be a member of N Series Family by owing a brand New N73 ME One Week Before (July 2008). The phone really Fascinated me with its features, Since my Previous Phone was Nokia 6630. Now let me Come to my problem.
A "Memory Full. Close some application" Error is encountering me twice or thrice a day. if i knowledge is correct, its Low RAM error & i found my RAM in the range of 18-20MB just after startup & along with usage of applications & closing, it maintain a range b/w 4-8MB. In this time wen i open a picture in inbuilt PicEditor this Memory full Error occurs(And sometimes while zooming a picture in gallery also). Will updating to the new FW according to my product code 0543843 is 4.0812.4.2.1 will solve the Memory leak problem ? i have gone through all the post regarding the issues on latest firmware updates Good & Bad. So im a bit confused that shud i update or not. Coz i have only this memory problem. Everything else is fine.
Please help me.
N73 ME
v 4.0736.3.2.1
04-09-2007
RM-133
Code:0543843
INDIA

I have 4.0812.4.2.1 and I have the same problem..I think that in 4.0736 is best memory usage than other firmwares,but I can't downgrade firmware

Memory leak in the JVM leading to system oom

Hi,
We are running application server using java 1.5, tomcat 5.5 ...
The problem is that the JVM is allocating memory continuously.
If we look at the JVM memory from JConsole everything is OK the amount of memory allocated in the heap does not grow significantly.
If we look at the JVM memory consumption from the system perspective, the memory usage is growing until the system runs out of memory and kill the JVM. The JVM memory usage goes beyong 1.5 Go of memory whatever options you use when launching the JVM.
The memory allocation is so intense that it can lead to a crash in few hours with very few users connected to the application.
We have tried JDK 1.5.05 and 1.5.06 still the same.
We are running on a Linux Debian system wth a 2.6.8 kernel.
Any idea of where all this memory goes ?
Any idea on how to track and solve this memory leak ?

Hi Martinux,
Tiger and Mustang come with a number of diagnosing tools that could help
you spot memory problems. In particular there's something called 'jmap' which can
take a snapshot of the JVM memory.
Danny Coward has recently written a nice blog to emphasize the existence
of this new tools - see
"Crash Course: Java SE Monitoring, Management and Troubleshooting"
http://blogs.sun.com/roller/page/dannycoward?entry=crash_course_java_se_monitoring
Of course if the problem isn't in the JVM...
BTW: you did also look at the non-heap memory, right? and also at the total
number of loaded classes?
hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/roller/page/jmxetc

Huge memory leak in java jvm after update 2 for Snow leopard

Since I updated to Java Update 2 for Snow Leopard my JVM suddenly grows massive (10GB+ real memory - -Xmx=3500m) consuming all memory and rendering my iMac unusable. This does not happen predictably but does happen several times a day now requiring I power off and on again.
I had been living happily with update 1 with no such problem.
I need to either go back to update 1 (should have it on Time Machine) or find a solution for this problem.

Our application is a j2ee-based commercial application facing to specified customers, having about 120 access request an hour.
We ' re doing stress test on the test server. The strange memory leak occurs at 1:20 am this morning while we're out of company , and no job was scheduled to run at that time. So I have the tendency to image that there is something inside oc4j had occured.
I have used OptimizeIt to monitor the heap status. However , as the memory leak problem occurs very occasionally ,and that tool deadly slows our server, we are currently using no profiling tools.

FLVPlayback Memory Leak in Flash CS3

Hi There,
I' making a flash file with AS2 in Flash CS3. I put a FlVPlayback in stage and let it load a couple of FLV files from my local HDD and playing continuously. I use "addEventListener" to check the current running flash movie is completed. After complete event occur, I load another flv movie to paly again.Here, I noticed that memory usage is increasing every time a new flv file is loaded and played. I heard "addEventListener" in CS3 is causing the memory leak and not being detected by GC.
Please let me know if there is a solution to solve the memory leak issue. I posted my codes here to know something I'm doing wrong.
Thanks in advance...
================================
onClipEvent (load)
    function _fun_complete(eventObj)
        this.autoRewind = "true";
        var _v1 = _root.v;
        var _v2 = _root.FLVlists.length;
        --__v2;
        if (_v1 < _v2)
            ++_v1;
        else
            _v1 = 0;
        this.contentPath = _root.FLVlists[_v1].path;
        var _v3 = _root.listVids[_v1].width;
        var _v4 = (stage._width - _v3) / 2;
        this._x = _v4;
        _root.v = _v1;
        this.play();
    this.addEventListener("complete", _fun_complete);

Helllo Friend,
Thanks for your feedback. The problem with removeEventListener is that , the player stops and not playing anymore. In my application, I nned to loop and play one FLV files after another. For example, I need to play 3 flv files, File1.flv, File2.flv, File3.flv. I load and play File1.flv first. Once complete event trigger from "addEventlisterner" , then I load File2.flv and then File3.flv and then Flie1.flv. So it needs play continuously and causing memory leak. Please let me know if there is another way of working around.
Regards

Memory Leak / Strange Garbage Collection

Help!
We are having strange problems that appear to be related to a memory leak. The
strange part is that even if we don't hit the site, it appears to leak. Can someone
please explain the output below: Notice how freespace is decreasing, even with
no direct site activity:
[GC 48857K->35514K(130560K), 0.0136978 secs]
[GC 49018K->35548K(130560K), 0.0144821 secs]
[GC 49052K->35550K(130560K), 0.0128796 secs]
[GC 49054K->35549K(130560K), 0.0121789 secs]
[GC 49053K->35547K(130560K), 0.0126394 secs]
[GC 49051K->35582K(130560K), 0.0161642 secs]
[GC 49086K->35770K(130560K), 0.0209171 secs]
[GC 49247K->36005K(130560K), 0.0188181 secs]
[GC 49509K->36198K(130560K), 0.0129967 secs]
etc...
If I understand the numbers correctly, we have less and less free space available.
If anyone has any insights into this it will be greatly appreciated. We have problems
moving into production.
Our environment: Solaris 8, Jdk1.3.1, WL 5.1
Chris

Chris - turn off verbose GC and and don't worry about it.
Visit java.sun.com and read all about Java and Garbage Collection and JVMs.
Weblogic does 'stuff' all on it's own even when it is not being accessed - just
like your refrigerator runs when are on vacation - (please tell me you don't worry
about that too). Objects get created and deleted. There is no pressing need for
the garbage collector to recover every scrap of unused memory - so it doesn't.
When the JVM does desperately need memory, it will run a Full GC and recover (almost)
all of that.
Then again it's nice to see someone who is curious about how the darn thing works.
:) Mike
"Chris" <[email protected]> wrote:
>
Thanks for the information. I guess I didn't understand it properly.
Is there a
reason why the numbers keep increasing, even with no site activity? It
looks like
there is less and less free space every few minutes....? After running
the whole
night after posting the original message, the numbers now look like:
[GC 55586K->42276K(130560K), 0.0136978 secs]
ie. Just keeps going up. Why does it increase? Thanks for any explanations!
Dimitri Rakitine <[email protected]> wrote:
You are not 'leaking memory' (hopefully!) - these are minor collections
(quickly
copying objects which lived long enough to the old generation portion
of the heap
and reclaiming space used by objects which died young) - wait until
major collection
(when it says [Full GC ...]).
Chris <[email protected]> wrote:
Help!
We are having strange problems that appear to be related to a memoryleak. The
strange part is that even if we don't hit the site, it appears to
leak.
Can someone
please explain the output below: Notice how freespace is decreasing,even with
no direct site activity:
[GC 48857K->35514K(130560K), 0.0136978 secs]
[GC 49018K->35548K(130560K), 0.0144821 secs]
[GC 49052K->35550K(130560K), 0.0128796 secs]
[GC 49054K->35549K(130560K), 0.0121789 secs]
[GC 49053K->35547K(130560K), 0.0126394 secs]
[GC 49051K->35582K(130560K), 0.0161642 secs]
[GC 49086K->35770K(130560K), 0.0209171 secs]
[GC 49247K->36005K(130560K), 0.0188181 secs]
[GC 49509K->36198K(130560K), 0.0129967 secs]
etc...
If I understand the numbers correctly, we have less and less free
space
available.
If anyone has any insights into this it will be greatly appreciated.We have problems
moving into production.
Our environment: Solaris 8, Jdk1.3.1, WL 5.1
Chris--
Dimitri

[updatedb/mlocate] memory leak[solved]

Hello,
I have a memory leak with updatedb.
Do you have the same problems?
Is this a known bug?
Thanks.
┏━━━┫ root@pc14570 ~ ┣━━━━━━━━━━━━━━━━━━━━
┗━┫ free -m ; updatedb ;free -m
total used free shared buffers cached
Mem: 15925 395 15529 47 19 146
-/+ buffers/cache: 229 15695
Swap: 0 0 0
total used free shared buffers cached
Mem: 15925 566 15358 47 114 156
-/+ buffers/cache: 295 15629
Swap: 0 0 0
┏━━━┫ root@pc14570 ~ ┣━━━━━━━━━━━━━━━━━━━━
┗━┫locate -S
Database /var/lib/mlocate/mlocate.db:
49063 directories
443871 files
29061235 bytes in file names
10911126 bytes used to store database
┏━━━┫ root@pc14570 ~ ┣━━━━━━━━━━━━━━━━━━━━
┗━┫
Last edited by nenesse (2014-06-22 15:43:43)

You are misinterpreting things.
Regardless of whether a program looses track of memory it has been allocated by the kernel and therefore fails to properly free it, the kernel does not forget. When the application exits, all of the memory it had allocated will be released by the kernel.
What you are seeing is an increase the amount of stuff that is cached. Unused memory is wasted memory. Updatedb happens to read a bunch of files. The kernel takes some of that unused memory and keeps some of the interesting stuff in the files that were read in memory so that if you turn around and ask for that information again, it is at hand. If you need the memory for something else, the kernel will release the stuff in that cached space and allocate it as needed.

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.

ImageComponent2DRetained.set memory leak

hi,
anybody aware of a memory leak in imagecomponent2DRetained.set??
i am using java3d 1.3.1.
my application will creates Text2D objs and then detach them from the scenegraph and create new Text2D objs over and over again.
Somehow, the array of bytes in imagecomponent2dretained does not get cleared.
Any ideas please??

yes.. it is registered and is solved in the 1.2.1 release.
However i am still getting a leak in 1.3.1. Strange.
Since node.clonetree and text2d also uses image2dcomponentretained.set,
this should be a big problem.
However, i can't spot the leak in image2dcomponentretained.set. Can anyone here spot it??

I am getting a memory leak that sometimes leads to an unresponsive Firefox, but does not crash per se.

Hello, For the last couple of months, I am having issues with one of my tabs or the program itself causing a memory leak. I was hoping that subsequent releases would fix the problem, but when I downloaded V.11 it did not help.
I use tab mix plus and at any time, usually have about 25 tabs open. Everything functioned okay for 8 or so months up until recently.
I am wondering if there is a way to try to track down what is causing the leak. If it is one of my open pages, i will get rid of it. I tried opening one page at a time from scratch, but could not find the issue. .
I always have flash block enabled to cut down on the website junk.
using OSX firefox v11.

Now, I'm not going to say it's an Add-On problem because from the research I've been doing on this problem for the last half hour shows that everyone has DIFFERENT add-ons, but everyone's having the SAME problem....
So I went through my add-ons and disabled them one by one, and the single add-on that has been giving me grief is the latest WOT add-on. So, I have Firefox 11 (so does my wife) and we both have the WOT add-on. But that's where the similarity ends... I have Windows 7 x64, she has Windows XP x86.... but she doesn't have the memory leak problem.
What I see is a sawtooth pattern over time. Memory goes up a little over 30+ seconds, then drops down. But over half an hour, the peaks of the sawtooth are larger, and it doesn't drop back down to the same level again - always a little more than before. And before you know it, FF is peaking at 1.5+GB, dropping down to 1.2GB... and FF is running very, very slowly.... excessive disk accesses (paging probably, though I apparently I still have 1.5 to 2.0 GB of free RAM). Killing FF frees it all up, and if I open FF again, it's back to using 250MB of RAM.
So, it's not the add-ons per se, but how they're interacting with FF (or the other way round).... most likely, it's this plug-in container they created to stop add-ons from taking FF with them when they crashed. Seems to have created more problems than it has solved..... would be great if you could choose not to use it....

[SOLVED] Strange memory leak

Similar Messages

Maybe you are looking for