-
-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android transactions lasting for days, TTID halfway in, all spans at the very end. #3329
Comments
Same customer also experiencing #3145 FWIW |
@stefanosiano theorized that this could be something related to content providers and also noticed that there are several starting points (and app start transactions) for the app in which it was reported (see linked Jira). |
@stefanosiano @markushi were you able to reproduce this? in any case, let's prio this next |
Please note, if this is relevant, multiple http requests in this transaction, all showing deadline_exceeded for the body, but headers were ok. I've added conversation with customer to linked Jira issue |
Maybe can be combined with #3084 |
I looked a bit deeper into the activities that are most likely to manifest this bug and I think it may be related to finishing the activity in the override fun onCreate() {
if (someCondition) {
startActivity(intent)
finish()
}
// other code
} |
@devPalacio thanks for this detail, highly appreciated - we'll look into this |
Integration
sentry-android
Build System
Gradle
AGP Version
unknown
Proguard
Enabled
Version
7.2.0
Steps to Reproduce
Customer is observing transactions lasting for multiple days where (馃憠 see linked Jira issue for examples)
About 60-70% of all transactions over 1 hour (about 1% of total transactions) exhibit this pattern:
(this is the main pattern and the one that I we don't have explanation for, there鈥檚 also a second, less common, pattern among extra-long transactions where all spans happen early on, except for one long file.read that delays TTID - this is out of scope of this report, please ignore those).
Below is customer's configuration:
Settings set during application oncreate via dagger/anvil DI
Gradle Plugin
Expected Result
Transaction start coincides with start timestamp of the first span.
Actual Result
Start timestamp of the first span lags days behind start of transaction.
鈹咺ssue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: