Home/ Questions/Q 8926039
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T07:52:01+00:00

I have a problem. I’ve been working with Android in Eclipse for the past

  • 0

I have a problem.
I’ve been working with Android in Eclipse for the past 4-5 weeks now and never had a problem with the VM (they were slow, yes. But never crashed).

Now, I believe since 4.2 when I started working on a new project for uni (deadline next week) my 4.2 VM suddently starts crashing on launch, because of “Kernel Panic” (resport at the end).

I wanted to ask if there is anything I could do, maybe download a hotfix or anything. Both the API and Eclipse are pretty much up to date or might there be something wrong with my computer?
(Somehow even my old VMs (2.3.3, 3.1 and 4.1) crash on launch 99% of the time)

Any advice would be highly appreciated. Here the beginning of the Crash-Log:

Process: emulator64-arm [1334] Path:
/Users/USER/*/emulator64-arm Identifier: emulator64-arm Version:
??? Code Type: X86-64 (Native) Parent Process: eclipse [1156]
User ID: 501

Date/Time: 2012-12-01 00:25:27.469 +0100 OS Version: Mac OS
X 10.8.2 (12C2034) Report Version: 10

Interval Since Last Report: 130686 sec Crashes Since Last
Report: 96 Per-App Crashes Since Last Report: 32 Anonymous
UUID: ABE51F99-F7A9-2595-016E-C47FFD1F6C50

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes:
KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
–>
__TEXT 0000000100000000-0000000100247000 [ 2332K] r-x/rwx SM=COW /Users/USER/*

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do you have two screens? if yes, did you launch avd/vm on secondary screen last time?
    If yes, then check config vm file at: 

    cd ~/.android/avd/  
ls -la   => here you see all avds
cd [your_vm.avd]
joe emulator-user.ini => edit this config file and see value

    window.x = 2054 – this is stupid value, cause says where to display emulator window. Value is set cause emulator window was displayed at second screen on x position 2054 but as I say it’s bug at avd. Simply change it to better value to display window at your main screen so like my case: 

    window.x = 954
window.y = 199
uuid = 1342941165631

    Save config file, start eclipse, start your avd/vm and all must run well.

    • 0