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.
Build: NetBeans IDE Dev (Build 201401100002) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Windows 7 User Comments: zdenek.rod: I try to open big xml file - cca 40 MB. Stacktrace: java.lang.OutOfMemoryError: GC overhead limit exceeded at java.io.Reader.read(Reader.java:120) at org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:211) at org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:165) at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2994) at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3048) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1177)
Created attachment 144235 [details] stacktrace
the big char array I see has 82M (appears to be your xml file) reassigning to xml for evaluation, biggest chunks of data on stack appear to be coming from tokenizing the huge xml file. BTW don't we have some sort of generic warning for people opening big files in editor?
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss