Bug 1403492 - Logging in using wayland leads to frequent unnecessary applications by gnome-shell of oom-killer
Summary: Logging in using wayland leads to frequent unnecessary applications by gnome-...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-10 15:41 UTC by Walter Neumann
Modified: 2017-12-12 10:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:45:31 UTC
Type: Bug


Attachments (Terms of Use)
I've attached a typical piece of the log. which shows among other things that plenty of memory is available (4.72 KB, text/plain)
2016-12-10 15:41 UTC, Walter Neumann
no flags Details

Description Walter Neumann 2016-12-10 15:41:25 UTC
Created attachment 1230328 [details]
I've attached a typical piece of the log. which shows among other things that plenty of memory is available

Description of problem:

When logged in to a gnome session using wayland I get frequent events of gnome-shell invoking oom-killer to kill firefox, gnome-session, ssh, etc. 

Version-Release number of selected component (if applicable):


How reproducible: always reproducible

Steps to Reproduce:
1. Log in to a gnome session using wayland
2.
3.

Actual results: After a few hours gnome-shell invokes oom-killer to kill an existing process such as firefox, gnome-session, ssh, etc.  even though there is plenty of free memory available. 


Expected results:  processes should not be killed. The problem does not arise if Xorg is used instead of wayland


Additional info:

Comment 1 Walter Neumann 2016-12-10 15:50:04 UTC
Further in the log one sees that the kernel thinks that it is out of memory even though the earlier part of the log shows plenty of free memory:

Dec  1 07:30:35 neumann kernel: Out of memory: Kill process 3638 (firefox) score 64 or sacrifice child
Dec  1 07:30:35 neumann kernel: Killed process 3638 (firefox) total-vm:1548872kB, anon-rss:721428kB, file-rss:31616kB, shmem-rss:10176kB
Dec  1 07:30:35 neumann kernel: oom_reaper: reaped process 3638 (firefox), now anon-rss:12kB, file-rss:96kB, shmem-rss:10180kB

Comment 2 Fedora End Of Life 2017-11-16 19:42:28 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:45:31 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.