"Broken pipe" exception when running macrobenchmark tests on 1.2.0-alpha09 [269949822]

Fixed

Bug

Status Update

No update yet.

Description

sc...@gmail.com

created issue #1

Feb 20, 2023 07:02PM

Hi!

For the following setup:

Component used: androidx.benchmark:benchmark-macro-junit4

Version used: 1.2.0-alpha09

Devices/Android versions reproduced on: Zenfone 9 (Android 13) / Pixel 3A (Android 12)

IDE: Android Studio Giraffe + AGP 7.4.1

Gradle 7.6

  private fun startup(
    compilationMode: CompilationMode,
    startupMode: StartupMode
  ) = benchmarkRule.measureRepeated(
    packageName = PROD_PACKAGE_NAME,
    metrics = listOf(
      StartupTimingMetric(),
      FrameTimingMetric()
    ),
    iterations = 5,
    compilationMode = compilationMode,
    startupMode = startupMode,
    setupBlock = {
      startActivityAndWait()
      device.signIn()
      pressHome()
    },
  ) {
    startActivityAndWait()

    device.swipeFeed()

    device.waitForIdle()
  }

I keep getting the following exception randomly during test execution:

java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
at java.net.SocketOutputStream.write(SocketOutputStream.java:156)
at com.android.okhttp.okio.Okio$1.write(Okio.java:78)
at com.android.okhttp.okio.AsyncTimeout$1.write(AsyncTimeout.java:157)
at com.android.okhttp.okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.java:177)
at com.android.okhttp.okio.RealBufferedSink.write(RealBufferedSink.java:47)
at com.android.okhttp.internal.http.RetryableSink.writeToSocket(RetryableSink.java:80)
at com.android.okhttp.internal.http.Http1xStream.writeRequestBody(Http1xStream.java:234)
at com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:618)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:475)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:411)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:248)
at androidx.benchmark.macro.perfetto.server.PerfettoHttpServer.httpRequest(PerfettoHttpServer.kt:276)
at androidx.benchmark.macro.perfetto.server.PerfettoHttpServer.httpRequest$default(PerfettoHttpServer.kt:257)
at androidx.benchmark.macro.perfetto.server.PerfettoHttpServer.parse(PerfettoHttpServer.kt:217)
at androidx.benchmark.macro.perfetto.PerfettoTraceProcessor.loadTrace(PerfettoTraceProcessor.kt:111)
at androidx.benchmark.macro.MacrobenchmarkKt$macrobenchmark$measurements$1.invoke(Macrobenchmark.kt:255)
at androidx.benchmark.macro.MacrobenchmarkKt$macrobenchmark$measurements$1.invoke(Macrobenchmark.kt:201)
at androidx.benchmark.macro.perfetto.PerfettoTraceProcessor$Companion.runServer(PerfettoTraceProcessor.kt:70)
at androidx.benchmark.macro.perfetto.PerfettoTraceProcessor$Companion.runServer$default(PerfettoTraceProcessor.kt:53)
at androidx.benchmark.macro.MacrobenchmarkKt.macrobenchmark(Macrobenchmark.kt:201)
at androidx.benchmark.macro.MacrobenchmarkKt.macrobenchmarkWithStartupMode(Macrobenchmark.kt:367)
at androidx.benchmark.macro.junit4.MacrobenchmarkRule.measureRepeated(MacrobenchmarkRule.kt:107)
at my.company.benchmark.FeedScrollingBenchmark.startup(FeedScrollingBenchmark.kt:65)

Happens on both of my devices. It was also present in 1.2.0-alpha07 which I tested some time ago.

It seems that this occurs at a random time - sometime just at the beginning of a test or in the middle of it. Happens for both builds with and without baseline profile.

Going back to version 1.1.1 resolves the issue.

Comments

ra...@google.com <ra...@google.com> Feb 21, 2023 05:32PM

Reassigned to ma...@google.com.

ma...@google.com <ma...@google.com> #2Feb 21, 2023 05:50PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

sc...@gmail.com <sc...@gmail.com> #3Feb 21, 2023 06:10PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

ma...@google.com <ma...@google.com> #4Feb 21, 2023 06:11PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

af...@gmail.com <af...@gmail.com> #5Apr 6, 2023 03:01AM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

la...@team.bumble.com <la...@team.bumble.com> #6Apr 19, 2023 10:42AM

Comment has been deleted.

Message last modified on Apr 19, 2023 10:42AM

ma...@google.com <ma...@google.com> #7Apr 19, 2023 10:53PM

Accepted by ma...@google.com.

FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model. https://developers.google.com/ml-kit/release-notes#august_11_2021

Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!

ma...@google.com <ma...@google.com> #8Apr 25, 2023 03:22PM

Marked as fixed.

Thank you, I'll try it and check.

ap...@google.com <ap...@google.com> #9Apr 25, 2023 03:23PM

Hello. I have similar experience.

I'm using mlkit-language 16.1.1
I didnot meet this error until using AGP 4.2
I can get this error since using AGP 7.0
This error raised on Release build only(minimized by R8)
This error raised without obfuscation.

na...@google.com <na...@google.com> #10May 3, 2023 06:24PM

Also I found there is a post which presents same issue on stackoverflow.

https://stackoverflow.com/questions/68832304/mlkit-translate-sdk-crashes-in-release-build