有没有碰到过这种tombstone？

[daichen]

发现有些进程dump会挂掉

backtrace:
#00 pc 00000000002f32f4 /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::LookupClassId(art::mirror::Class*)+68) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#1 pc 00000000002f289c /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::DumpHeapInstanceObject(art::mirror::Object*, art::mirror::Class*, std::__1::set<art::mirror::Object*, std::__1::lessart::mirror::Object*, std::__1::allocatorart::mirror::Object* > const&)+220) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#2 pc 00000000002efbec /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::DumpHeapObject(art::mirror::Object*)+1024) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#3 pc 00000000002f8414 /apex/com.android.art/lib64/libart.so (void art::gc::accounting::SpaceBitmap<8ul>::VisitMarkedRangeart::hprof::Hprof::ProcessBody()::'lambda'(art::mirror::Object*)&(unsigned long, unsigned long, art::hprof::Hprof::ProcessBody()::'lambda'(art::mirror::Object*)&) const+216) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#4 pc 00000000002f63b4 /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::ProcessBody()+1096) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#5 pc 00000000002f5b08 /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::ProcessHeap(bool)+160) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)
#6 pc 00000000002f4f4c /apex/com.android.art/lib64/libart.so (art::hprof::Hprof::Dump()+3376) (BuildId: c6d9dc4984da0c13b6a556d8eb203f5a)

[alhah]

是Android 11么？Android 11的虚拟机目前适配的还不是特别完善，偶现会崩溃。
不过崩溃的是fork出来的子进程，不影响用户体验，会降低dump成功率

[daichen]

是11

[alhah]

已知问题，早期版本Android 11上的fork dump实现有缺陷，请用2.0