The following forum message was posted by rekveld at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/4739830:
Hi Fabio, finally managed to do a 554MB heapdump and uploaded it to http://rekveld.home.xs4all.nl/stuff (i have to run now and it still has 30mins of uploading to go) I modified the settings a bit in order to avoid having to upload a 1.2GB dump, but I don't think that makes a difference for tracking down the problem. And for those who ever need to do this, what I figured out is to add these two lines to your eclipse.ini file. The last one specifies the directory and it is wise to make a directory especially for it, since the analysis produces lots of little files you don't want to pollute your working directory or home folder. It took me a while to find this out, since all the documentation is mostly explaining you how to find memoryleaks in your own code, not in the IDE you're using. I had a look and it seems to have to do with code analysis. A couple of times Eclipse froze on completing an Open_GL attribute, and in the system monitor I could see it filling up 1.2G of memory in 2 or 3 minutes. --launcher.XXMaxPermSize 256m openFile -vmargs -Xms128m -Xmx384m -Xss4m -XX:PermSize=128m -XX:MaxPermSize=384m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/your/path/here ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
