sheraff

Untitled

Apr 28th, 2024
49
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.39 KB | None | 0 0
  1. Apr 28 12:58:12 aXBook kernel: [ 9520] 1000 9520 17433058 3233229 3233098 99 32 26812416 0 0 telegram-deskto
  2. Apr 28 12:58:12 aXBook kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=docker-0bb1b6f7a293d03a1295ae7881c0ebdcb35e7744bc2919ea71ab7c6296d5054c.scope,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-3.scope,task=telegram-deskto,pid=9520,uid=1000
  3. Apr 28 12:58:12 aXBook kernel: Out of memory: Killed process 9520 (telegram-deskto) total-vm:69732232kB, anon-rss:12932392kB, file-rss:396kB, shmem-rss:128kB, UID:1000 pgtables:26184kB oom_score_adj:0
  4. Apr 28 12:58:12 aXBook systemd[1]: session-3.scope: A process of this unit has been killed by the OOM killer.
  5. ░░ Subject: A process of session-3.scope unit has been killed by the OOM killer.
  6. ░░ Defined-By: systemd
  7. ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  8. ░░
  9. ░░ A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
  10. ░░ killer logic. This usually indicates that the system is low on memory and that
  11. ░░ memory needed to be freed. A process associated with session-3.scope has been determined
  12. ░░ as the best process to terminate and has been forcibly terminated by the
  13. ░░ kernel.
  14. ░░
  15. ░░ Note that the memory pressure might or might not have been caused by session-3.scope.
  16.  
Advertisement
Add Comment
Please, Sign In to add comment