Building Trichrome Libary in order to investigate remote crash

[Arseniy Maryin]

I have an Android crashlog from Play Console with Trichrome Library:

  #00  pc 000000000248251c  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d19475  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002f91fd5  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  ...
 
  I want to build trichromelibrary of appropriate version from sources. Chrome version seems to be 96.0.4664.45
  Can I figure out build arguments I need to build this binary?

[Torne (Richard Coles)]

What are you trying to accomplish by building it? You will not be able to reproduce the exact same build as ours no matter what build options you use, so you won't be able to symbolize these address offsets.

If you just want to understand what the crash is then you should file an issue with as much information as you have through https://bugs.chromium.org/p/chromium/issues/entry?template=Webview+Bugs and we can help you understand what's happening and whether it's an issue in our code or your app or something else.

 

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Torne (Richard Coles)]

This symbolizes to:

0x0248251c: logging::LogMessage::~LogMessage()::$_2::operator()() const at ./../../base/logging.cc:879 (discriminator 2)
 (inlined by) logging::LogMessage::~LogMessage() at ./../../base/logging.cc:879 (discriminator 2)
0x00d19475: android_webview::(anonymous namespace)::OnContextLost(std::__1::unique_ptr<bool, std::__1::default_delete<bool> >, bool) at ./../../android_webview/browser/gfx/output_surface_provider_webview.cc:78 (discriminator 8)
0x02f91fd5: base::OnceCallback<void (bool)>::Run(bool) && at ./../../base/callback.h:142 (discriminator 4)
 (inlined by) gpu::SharedContextState::MarkContextLost(gpu::error::ContextLostReason) at ./../../gpu/command_buffer/service/shared_context_state.cc:571 (discriminator 4)

So this is a LOG(FATAL) being hit. The log message should be shown in the crash, but I'm not sure whether that's included in what you can see in the Play Console. Given the calling code though, this is the GPU context being lost. Usually this means the GPU driver ran out of memory or otherwise malfunctioned, and it's not likely to be actionable :(

[Arseniy Maryin]

Could you symbolize full stack trace?

  #00  pc 000000000248251c  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d19475  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002f91fd5  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)

  #00  pc 0000000002b42131  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002b41f23  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002b8417b  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002b82cd3  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002b82c91  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000002b82c53  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000001b6b5f7  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d1fd9b  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d1fedd  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000001b6b5f7  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d2008d  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d204fb  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d18889  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d17beb  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d1d4cd  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)
  #00  pc 0000000000d13217  /data/app/com.google.android.trichromelibrary_466404530-Ueviwh5UOpgACSOFhmnXcg==/base.apk!libmonochrome.so (offset 0x664000)

пятница, 25 февраля 2022 г. в 19:30:30 UTC+3, to...@chromium.org:

[Torne (Richard Coles)]

I don't have the data handy any more and I'm not sure it's going to be that useful. If you think there's a problem that needs investigating then you should file a bug as I said, but we're unlikely to be able to do much about a random GPU context loss without a repro case, so unless you have a lot more information then it's probably not going to be actionable.