This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Open any Java Project and do some refactoring (renaming methods, classes,..) et observe that Memory Usage just don't stop from increasing. IN my case, memory goes up from 300Mo to 600, 700Mo... On the 32-bits version, it just run out of memory after 1 or 2 hours of refactoring. This is very painfull. And only since Netbeans 8.0.2
Please attach a heap dump[1] to the issue. And could you clarify, is the memory usage increasing after performing a refactoring by itself, or are you performing multiple refactorings and is the memory consumption increasing after each refactoring? Thanks! [1] - http://wiki.netbeans.org/FaqMemoryDump
Yesterday, I make a few heapdump showing memory incresaing from 300M to about 730M, but each heapdump is about 150ko, too large to attach to the issue. How can I send them to you ?
Instructions to upload the heap dump file are at the link in comment #1. Thanks!
Exact. and I use the jmap tool : "jmap -dump:live,format=b,file=heap.bin <pid>" but netbeans bugzilla limits uploads to 10Mo et my heapdumps are 150Mo!
Heap dump files are invariably very large, while they compress quite well using zip or gzip, it is not practical to attach them as an attachment to bugzilla. Rather, please use the following Hudson job, intended specifically for uploading large files: http://deadlock.netbeans.org/hudson/job/upload/build - Compress the heap dump file using zip or gzip - Select a file using the Choose File button at http://deadlock.netbeans.org/hudson/job/upload/build - Press Build and wait until the upload completed (this will take a long time) The job will display a link to the uploaded file - paste this link to the bug report