New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 779145 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

couldn't lock 16384 bytes of memory (secret_session): Não foi possível alocar memória

Reported by wtds.tra...@gmail.com, Oct 27 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/62.0.3202.62 Chrome/62.0.3202.62 Safari/537.36

Steps to reproduce the problem:
1. Just Open Browser
2. See in the terminal
3. couldn't lock 16384 bytes of memory (secret_session): Não foi possível alocar memória

What is the expected behavior?
Not error

What went wrong?
Error: couldn't lock 16384 bytes of memory (secret_session): Não foi possível alocar memória

Did this work before? N/A 

Chrome version: 62.0.3202.62  Channel: stable
OS Version: Ubuntu 17.10 (Artful Aardvark)
Flash Version:
 

Comment 1 by md628...@gmail.com, Oct 27 2017

1-11-2017
Cc: brajkumar@chromium.org
Labels: Needs-Triage-M62 Needs-Feedback
Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable #62.0.3202.62. Observed less memory usage in task manager.

reporter@ Could you please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser. If issue still persists please do a restart and check for it.

Thanks!
Labels: Performance
Labels: -Performance Performance-Memory
Status: WontFix (was: Unconfirmed)
As there is no response from the reporter for more than a month, marking this as Wontfix.
Please feel free to raise a new bug if the issue still exists on the latest Chrome builds.

Thanks...

Sign in to add a comment