New issue
Advanced search Search tips

Issue 789082 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

[Chrome][M62][Android 7.1.2] Frequent ANR in ChromeTabbedActivity

Reported by seiyon.p...@gmail.com, Nov 28 2017

Issue description

Steps to reproduce the problem:
1. Open up Chrome
2. Browsing several sites

What is the expected behavior?

What went wrong?
Suddenly Chrome doesn't respond.

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 7.1.2
Flash Version:
 
main.log.22
8.0 MB Download
traces.txt
682 KB View Download
Labels: Needs-triage-Mobile
Cc: pnangunoori@chromium.org
Labels: Triaged-Mobile Needs-Feedback
Upon analyzing the logs provided, ANR would be because of the Low Memory. 

@seiyon.park -- Thanks for providing the logs. Could you please restart your device and let us know if the ANR's are still observed.

Let us know your observations.

Thanks in advance.
@pnangunoori, thanks for your investigation.
And I am wondering which log says that the low memory state makes ANR occur.
FYI, I have not found out any clues about the low memory state.
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
seiyon.park@ -- You can find this from the log provided by you in the original comment:
11-28 01:32:43.959   574   574 E lowmemorykiller: Error writing /proc/8673/oom_score_adj; errno=22

Please verify the behavior by rebooting your device and let us know your observations.

Thanks in advance.
Status: WontFix (was: Unconfirmed)
Closing this issue due to lack of feedback from reporter. 

Please feel free to file a new issue if the issue is still observed in latest Chrome #64.0.3282.123.

Thanks!
Closing this issue due to lack of feedback from reporter. 

Please feel free to file a new issue if the issue is still observed in latest Chrome #64.0.3282.123.

Thanks!

Sign in to add a comment