High level of crash on Android Emulator M1 when moving cursor focus in and out of the emulator repeatedly (std::__1::basic_ostream<char, std::__1::char_traits<char>>::sentry::~sentry()) [275397905]

Fixed

Bug

Status Update

No update yet.

Description

jp...@google.com

created issue #1

Mar 27, 2023 08:00PM

High level of crash on Android Emulator M1 with std::__1::basic_ostream<char, std::__1::char_traits<char>>::sentry::~sentry()

We do not (yet) have a way to reproduce the problem, but we can see on go/crash an high level of report with `EXC_BAD_ACCESS` issue with

`std::__1::basic_ostream<char, std::__1::char_traits<char>>::sentry::~sentry()`

The stack doesn't see much, except that this is on M1 ( qemu-arch-aarch64, using Qt6)

```
Stack Quality26%Show frame trust levels
0x00000001aba1d40c (libc++.1.dylib + 0x0001f40c) std::__1::basic_ostream<char, std::__1::char_traits<char>>::sentry::~sentry()
0x000000010103d768 (qemu-system-aarch64 + 0x001b1768)
0x000000010103d768 (qemu-system-aarch64 + 0x001b1768)
0x0000000101447224 (qemu-system-aarch64 + 0x005bb224)
0x000000010143c138 (qemu-system-aarch64 + 0x005b0138)
0x00000001069ccc48 (libQt6CoreAndroidEmu.6.2.1.dylib + 0x00010c48)
0x00000001069ccb10 (libQt6CoreAndroidEmu.6.2.1.dylib + 0x00010b10)
0x00000001069d319c (libQt6CoreAndroidEmu.6.2.1.dylib + 0x0001719c)
0x0000000107c2ea90 (libQt6GuiAndroidEmu.6.2.1.dylib + 0x0008aa90)
0x0000000107c75c8c (libQt6GuiAndroidEmu.6.2.1.dylib + 0x000d1c8c)
0x00000001066c8a4c (libqcocoaAndroidEmu.dylib + 0x00014a4c)
0x00000001abb9da04 (CoreFoundation + 0x00081a04) __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
0x00000001abb9d998 (CoreFoundation + 0x00081998) __CFRunLoopDoSource0
0x00000001abb9d708 (CoreFoundation + 0x00081708) __CFRunLoopDoSources0
0x00000001abb9c30c (CoreFoundation + 0x0008030c) __CFRunLoopRun
0x00000001abb9b874 (CoreFoundation + 0x0007f874) CFRunLoopRunSpecific
0x00000001b527bf9c (HIToolbox + 0x00031f9c) RunCurrentEventLoopInMode
0x00000001b527bc2c (HIToolbox + 0x00031c2c) ReceiveNextEventCommon
0x00000001b527bb28 (HIToolbox + 0x00031b28) _BlockUntilNextEventMatchingListInModeWithFilter
0x00000001aee21848 (AppKit + 0x00039848) _DPSNextEvent
0x00000001aee209d8 (AppKit + 0x000389d8) -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
0x00000001aee14e08 (AppKit + 0x0002ce08) -[NSApplication run]
0x00000001066c792c (libqcocoaAndroidEmu.dylib + 0x0001392c)
0x0000000106a547f0 (libQt6CoreAndroidEmu.6.2.1.dylib + 0x000987f0)
0x0000000106a4bb44 (libQt6CoreAndroidEmu.6.2.1.dylib + 0x0008fb44)
0x000000010143a3f8 (qemu-system-aarch64 + 0x005ae3f8)
0x000000010103caf0 (qemu-system-aarch64 + 0x001b0af0)
0x00000001ab793e4c (dyld + 0x00005e4c) start
```

This is seen with stable 32.1.12 , after 1 week we have 2035 sample reports from 745 unique users

https://crash.corp.google.com/browse?q=product_name%3D%22AndroidEmulator%22+AND+STRPOS%28product.Version%2C+%2732.1%27%29+%3E+0+AND+product.Version%3D%2732.1.12-9751036%27+AND+stable_signature%3D%27std%3A%3A__1%3A%3Abasic_ostream%3Cchar%2C+std%3A%3A__1%3A%3Achar_traits%3Cchar%3E%3E%3A%3Asentry%3A%3A%7Esentry-948c2baf%27

Comments

jp...@google.com <jp...@google.com> Mar 27, 2023 08:00PM

Reassigned to jo...@google.com.

jo...@google.com <jo...@google.com> #2Mar 28, 2023 04:38PM

https://bit.ly/3UxSQmb

jo...@google.com <jo...@google.com> #3Mar 28, 2023 05:15PM

Here is what I found: On API 31+, time was not updated after the host was waken up. While on API 30 and under, time was updated after host was waken up. The main difference is caused by switching the modem simulator. In API 30 and under, time will be updated whenever signal strength query is received. Reference

Looking at the code in API 31+ for time update when signal strength query is received, I think it is possible that timeUpdate is not invoked

void NetworkService::HandleSignalStrength(const Client& client) {
  std::vector<std::string> responses;
  std::stringstream ss;

  if (WakeupFromSleep()) {
    misc_service_->TimeUpdate();
  } else if (first_signal_strength_request_) {
    first_signal_strength_request_ = false;
    misc_service_->TimeUpdate();
  }

  android_last_signal_time_ = time(0);

  auto response = BuildCSQCommandResponse(GetCurrentSignalStrength());

  responses.push_back(response);
  responses.push_back("OK");
  client.SendCommandResponse(responses);
}

jo...@google.com <jo...@google.com> #4Mar 28, 2023 05:37PM

CL is merged. We plan to release it to the next canary and stable.

ap...@google.com <ap...@google.com> #5Mar 28, 2023 09:17PM

Ranjit, can you please help verify this on 32.1.8 Canary and 31.3.14 Stable?

jo...@google.com <jo...@google.com> Mar 29, 2023 04:00PM

Marked as fixed.

an...@google.com <an...@google.com> #6Mar 30, 2023 06:29PM

Still seeing this issue with Emulator 31.3.14 Stable. Refer to the screenshot.

an...@google.com <an...@google.com> #7Apr 8, 2023 12:36AM

@devki How do I know if the fix is in 31.3.14 stable? Any tool for checking if a CL went into the specified version?

de...@google.com <de...@google.com> #8Apr 24, 2023 10:45PM

hi! we can check in "where is my cl" to see if it was added into the branch:

https://android-build.googleplex.com/builds/where-is-my-cl/search/I098de6ea8fe90c64bfc72a11adc13c6e13a06cdd

It doesn't look like it was cp'ed into aosp-emu-31-release

Does it need to be cp'ed?

se...@gmail.com <se...@gmail.com> #9Jun 11, 2023 02:03PM

RE#9 Thanks Devki. Actually the fix is included in aosp-emu-31-release branch. https://android-build.googleplex.com/builds/branch-dashboard/aosp-emu-31-release?build_id=9296499 There is probably still something missing in the stable release and I will take another look.