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.
Created attachment 155099 [details] messages.log java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at org.openide.util.RequestProcessor$Processor.get(RequestProcessor.java:1930) at org.openide.util.RequestProcessor.enqueue(RequestProcessor.java:611) at org.openide.util.RequestProcessor$TickTac.run(RequestProcessor.java:2260) Product Version: NetBeans IDE Dev (Build 201507280002) Updates: Updates available Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b14 System: Linux version 3.14.27-100.fc19.x86_64 running on amd64; UTF-8; en_US (nb) User directory: /home/toddb/.netbeans/dev Cache directory: /home/toddb/.cache/netbeans/dev
*** Bug 254146 has been marked as a duplicate of this bug. ***
It is difficult to fix without heap dump (which is missing). But there were quite a few changes to reduce memory consumption, so might be already fixed as part of https://netbeans.org/bugzilla/show_bug.cgi?id=255362
*** Bug 257364 has been marked as a duplicate of this bug. ***
See issue #257364 for the heap dump.
Just a thought (I'm not saying that we should not fix this bug): I see -Xmx735m and -Xmx1024m in reports. The former is obviously too small. The second is more or less ok. Although I personally never give it less than 2g This reminds me the idea to check it and warn user: if we are that greedy, we should at least be honest and say about that. Well, it's a matter of a separate discussion.
(In reply to Vladimir Kvashin from comment #5) > Just a thought (I'm not saying that we should not fix this bug): > I see -Xmx735m and -Xmx1024m in reports. > The former is obviously too small. The second is more or less ok. > Although I personally never give it less than 2g > This reminds me the idea to check it and warn user: if we are that greedy, > we should at least be honest and say about that. Well, it's a matter of a > separate discussion. Vladimir, did look at project size in the message log? I think that several projects with about 70 source files should be parsed in -Xmx735m. Your suggestion 2g is for projects with 10k source files.
(In reply to Alexander Simon from comment #6) > (In reply to Vladimir Kvashin from comment #5) > > Just a thought (I'm not saying that we should not fix this bug): > > I see -Xmx735m and -Xmx1024m in reports. > > The former is obviously too small. The second is more or less ok. > > Although I personally never give it less than 2g > > This reminds me the idea to check it and warn user: if we are that greedy, > > we should at least be honest and say about that. Well, it's a matter of a > > separate discussion. > > Vladimir, > did look at project size in the message log? > I think that several projects with about 70 source files should be parsed in > -Xmx735m. This projects uses whole Qt library according to names in parser threads... Please, reopen with new snapshot if -Xmx2G doesn't help