I have read the many threads regarding this issue, but none of the
proposed solutions has actually solved the problem for me. And judging
by the frequency of threads about it, that hasn't solved it for a lot
of other people either. =)
Here's the problem: When I run my code, seemingly out of nowhere I'll
get the error shown in the subject line:
ERROR: the user data image is used by another emulator. aborting
This *seems* straightforward, but I only have one emulator running. =\
As evidence, please see this screenshot:
http://screencast.com/t/YzQ5MGUyNTkt
This happens after I run a varying number of successful executions.
Sometimes I may get three in before the error, sometimes I may get
twenty. In this most recent case I had probably run the code fifteen
times in 45 minutes. Here's the output from the console:
http://screencast.com/t/YjAzYzk1NmYt
When this happens, I can try to run it as many times as I like, but
I'll continue to get the same error every time:
[2009-11-12 20:14:21 - AnalogClockWidget]Android Launch!
[2009-11-12 20:14:21 - AnalogClockWidget]adb is running normally.
[2009-11-12 20:14:21 - AnalogClockWidget]No Launcher activity
found!
[2009-11-12 20:14:21 - AnalogClockWidget]The launch will only
sync the application package on the device!
[2009-11-12 20:14:21 - AnalogClockWidget]Performing sync
[2009-11-12 20:14:21 - AnalogClockWidget]Automatic Target Mode:
launching new emulator with compatible AVD 'savd2'
[2009-11-12 20:14:21 - AnalogClockWidget]Launching a new emulator
with Virtual Device 'savd2'
[2009-11-12 20:14:21 - Emulator]emulator: ERROR: the user data
image is used by another emulator. aborting
The first million times this happened I thought there might be some
sort of conflict with having more than one AVD set up -- maybe somehow
one started automatically if the other was busy or something -- so I
finally deleted all my AVDs and created one single AVD that is now the
only one in existence. Here is a screenshot of the SDK and AVD manager
showing that there is only one AVD hanging around:
http://screencast.com/t/YjM4NmMwNG
The problem is fixable by closing the emulator and making a new one,
but as we all know that takes a painful 3-6 minutes each time.
Does anybody know what could be causing this? The first twenty times I
restarted the emulator this afternoon, I was able to spend the
intervening five minutes straightening up the kitchen. But I'm running
out of stuff to clean. =(
Thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
