PDE freezes after switching into the Android mode

[codeanticode]

Observed on PR3 under OS X 10.10

[codeanticode]

After waiting for a while, the PDE is responsive again, but the following error shows up in the console (3.0.2):

Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: GC overhead limit exceeded
    at java.util.regex.Matcher.<init>(Matcher.java:225)
    at java.util.regex.Pattern.matcher(Pattern.java:1093)
    at com.google.classpath.RegExpResourceFilter.match(RegExpResourceFilter.java:37)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:50)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:32)
    at com.google.classpath.DirectoryClassPath.findResources(DirectoryClassPath.java:90)
    at com.google.classpath.CompositeClassPath.findResources(CompositeClassPath.java:78)
    at processing.mode.java.pdex.ASTGenerator.getSuggestImports(ASTGenerator.java:3288)

Same thing happens with latest revision from Processing (0249), the error is slightly different:

Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Arrays.java:3236)
    at java.lang.StringCoding.safeTrim(StringCoding.java:79)
    at java.lang.StringCoding.access$300(StringCoding.java:50)
    at java.lang.StringCoding$StringEncoder.encode(StringCoding.java:305)
    at java.lang.StringCoding.encode(StringCoding.java:344)
    at java.lang.String.getBytes(String.java:918)
    at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
    at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242)
    at java.io.File.isFile(File.java:882)
    at com.google.classpath.DirectoryClassPath$FileFileFilter.accept(DirectoryClassPath.java:34)
    at java.io.File.listFiles(File.java:1291)
    at com.google.classpath.DirectoryClassPath.listNames(DirectoryClassPath.java:62)
    at com.google.classpath.DirectoryClassPath.listResources(DirectoryClassPath.java:74)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:49)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)
    at com.google.classpath.ResourceFinder.findResources(ResourceFinder.java:46)

[Manindra29]

This error is from the google classpath explorer library which is used for providing import suggestions. It's running out of memory while performing a regex match to find all possible classes that match some class in the classpath. The Android SDK definitely adds a lot more classes to its search path on top of the default pde classpath classes. I'll investigate further and report back.

[codeanticode]

The only jar in the Android SDK that should be searched for classes to import is platforms-xy/android.jar, and if several platforms are available, only the currently selected one . Is there any way to specific the particular jar to include in the classpath?

[codeanticode]

Just a quick update: forcing ASTGenerator.getSuggestImports() to return null regardless of the situation does in fact eliminate the UI hanging and the OutOfMemoryError. So we clearly need a way to limit the extent of search by the classpath explorer...

[codeanticode]

A temporary workaround is to disable the "Suggest import statements" option in the Preferences.

[codeanticode]

@JakubValtar adding you to this discussion. As Manindra pointed out above, this issue is due to the classpath explorer library, used by the suggest imports features. The Android SDK has too many classes, and this leads to the out-of-memory error.

[JakubValtar]

@codeanticode Update processing to latest and try again. I did error checker overhaul (merged yesterday) and it works great for me with -Xmx256m. Problem might be that previously whole processing app class path was added to search path, which is certainly not what we wanted and for example IDEs are adding tons of stuff to class path, so some people may have experienced problems with having too much stuff there.

[JakubValtar]

@codeanticode I fixed memory leak in AndroidEditor which was preventing closed editors to be GC'd. Might solve this. I can run more than 10 editors within 256 MB. See #215