This repository was archived by the owner on Jan 25, 2025. It is now read-only.
Open
Conversation
Member
|
@4f77616973 It seems to work fine up to 15 min. I had a crash between 20-25 min. Trying to recreate it again to get a more accurate time. |
Member
Author
|
Any updates on this? |
Member
I'm still getting a crash around the 20 min mark. If 15 min is an acceptable window then we can go ahead with this, but it doesn't seem to be addressing the root cause of the crash. Also weirdly, I don't get the crash log dialog when it crashes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
♻️ Current situation
The network call timer thread executed too frequently, causing Volley to suffer from a memory leak from inconclusive requests.
💡 Proposed solution
Increase the timer interval to 5500ms.
📷 Screenshots
NA
📚 Release Notes
📝 Testing