AOSP Emulator not running anymore (segfault)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, linux, ubuntu
- Domain
- operating-systems
Research direction
Start by reproducing the issue with the listed AOSP Android 12.1.0_r5 commands in the Ubuntu 20.04 WSL 2 environment, then inspect dmesg.txt and the kernel logs. Compare the reported WSL and kernel versions; done means identifying the regression or restoring emulator startup without a segmentation fault.
Written by the indexing model from the issue text.
Description
Version
Microsoft Windows [Version 10.0.22622.450]
WSL Version
- WSL 2
- WSL 1
Kernel Version
5.15.57.1
Distro Version
Ubuntu 20.04
Other Software
I was running aosp emulator correctly since 1 month but now it segfaults
Here are the kernel logs :
Seems that there is a regression on the latest release.. I don't know how to fix.
I also tried with Kernel 5.10.102.1 and wsl v0.64.0 but same problem, same segfault.
Repro Steps
mkdir aosp && cd aosp
repo init -u https://android.googlesource.com/platform/manifest -b android-12.1.0_r5 --depth=1
repo sync -j4
. ./build/envsetup.sh && lunch 73
make -j4
emulator
Expected Behavior
Actual Behavior
Diagnostic Logs
No response
- Dominant language
- C++
- Stars
- 11.9k
- Forks
- 429
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/wslg
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·