Home/ Questions/Q 980837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T04:27:06+00:00

a million error per day using eclipse with the Android plug-in i tried everything

  • 0

a million error per day using eclipse with the Android plug-in i tried everything uninstall plug-in ,eclipse,JDK,JRE and install them again and using different ver. also changes Workspaces , i thought the problem with the new Java and Eclipse but i solved it and still . what the alternative is there a way so it could be more stable is other IDE with Android Plugin is mature enough to use them instead of all the problem and headache that eclipse give me in my life .

Edit: i use Eclipse 3.5 and im running Win7 in 4 Gig of ram ,i read the info about the known bug with Eclipse and JDK 6 update 21 and try what they suggest but i think thats not the problem.

some of the problem that i had ,XML editor for Android also sometime the disable of the Auto-complete (i made new Workspaces now i have 10’s of them ) and when i open the DDMS nothing appears even when i try to add the LogCat also alot of error msgs that prompt to me and close the IDE and sometime it just close by-itself .

Edit 2 : New Error it display to me “permGen space” ?!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What version of Eclipse are you using?

    The ADT Plugin for Eclipse site warns about this:

    Caution: There are known issues with
    the ADT plugin running with Eclipse
    3.6. Please stay on 3.5 until further notice.

    Also, check your JDK to be the latest. If you are on Windows, there’s a known bug with Eclipse and JDK 6 update 21. Check that you are using the latest version since Oracle fixed it.

    Must add I’ve used Eclipse for Java Developers version 3.5 with the ADT plugin, and haven’t had any of the mentioned problems so far.

    EDIT: Could you be more specific with those errors?

    XML editor for Android works fine with auto-complete in my case, so does the debugger. I’ve been able to debug applications correctly. Take in consideration when launching the emulator, it takes a few minutes for the emulated system to boot, launch your app, etc.

    You should copy and paste the error messages that Eclipse displays, in order to have an idea of what is happening.

    It could be a problem with the memory assigned to Eclipse, the JVM, or who knows what, but we need more detailed information in order to assist you.

    EDIT 2: This is quite a common error in Eclipse. From Eclipse’s Wiki:

    If you see java.lang.OutOfMemoryError:
    PermGen space errors, you need to
    increase the permanent generation
    space available to Eclipse.

    PermGen is the permanent generation of
    objects in the VM (Class names,
    internalized strings, objects that
    will never get garbage-collected). An
    easy, if somewhat memory-hungry fix is
    to enlarge the maximum space for these
    objects by adding

    eclipse [normal arguments] -vmargs -XX:PermSize=64M -XX:MaxPermSize=128M [more VM args]

    The arguments after -vmargs are
    directly passed to the VM. Run java -X
    for the list of options your VM
    accepts. Options starting with -X are
    implementation-specific and may not be
    applicable to all VMs.

    You can also put the extra options in
    eclipse.ini.

    Check the link for further information, you can find common errors and bugs in the Eclipse and Sun VMs on Windows part.

    • 0