The problem is your-avd-name.ini (configuration files) , which is located in .android (search in Windows search) on your Windows computer (if you are using a Windows user). When an error occurs during the avd.ini analyzer, the Google ADT plugin tries to access the map with a value of zero. The workaround is to remove the corrupt .ini file and restore your avd (s).
source share