Status Update
Comments
cl...@google.com <cl...@google.com> #2
P1 as this is causing crashes in production
cl...@google.com <cl...@google.com> #3
Can we have someone assigned to look at this please?
ha...@google.com <ha...@google.com> #4
I spent some time on this to understand how the final values in the crash report could come to be. Honestly I'm drawing a blank. All the leading code paths are guarded against any configuration that can produce these values. I'm thinking that there's a somewhat complex AnnotatedString calculation with a couple of ParagraphStyles but I can't think of any particular scenario that leads to this crash.
ha...@google.com <ha...@google.com> #5
We need the reporter to provide more information about the screen or any kind of complex AnnotatedString construction that they are doing.
se...@google.com <se...@google.com> #7
Tracked P1
gr...@google.com <gr...@google.com> #8
Any updates here?
ha...@google.com <ha...@google.com> #10
Meta's last response was "we didn't have much information on this issue, after the 1.7 stable version, the crash number is very very small". So I'm lowering the priority on this bug to P2 as long as we don't get more information.
ap...@google.com <ap...@google.com> #11
Project: platform/frameworks/support
Branch: androidx-main
Author: Anastasia Soboleva <
Link:
Add more debug info into findParagraphByIndex
Expand for full commit details
Add more debug info into findParagraphByIndex
Bug: 356080063, 374115892
Test: N/A
Change-Id: I9d7eef189bb5e8aa5a9b56e8fc2642a2634a2a45
Files:
- M
compose/ui/ui-text/src/commonMain/kotlin/androidx/compose/ui/text/MultiParagraph.kt
Hash: d24dad0b0db0cc7bf4c6062f40fadd38c04d4d43
Date: Tue Oct 22 14:28:01 2024
so...@google.com <so...@google.com> #12
This might be the same root cause as in
Description
This issue was originally reported by Meta. The stackrace is the only information we have on the crash.