Bug 389128 - When full physical memory - Process (kactivitymanage) of user 1000 dumped core.
Summary: When full physical memory - Process (kactivitymanage) of user 1000 dumped core.
Status: RESOLVED NOT A BUG
Alias: None
Product: kactivitymanagerd
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.11.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-17 19:53 UTC by kolorafa
Modified: 2018-01-19 21:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
journalctl (145.46 KB, text/plain)
2018-01-17 19:53 UTC, kolorafa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kolorafa 2018-01-17 19:53:17 UTC
Created attachment 109949 [details]
journalctl

It happens every time i reach 100% of my physical ram, the swap is like between 0%-0,5%, there is no OOM in the log, but kactivitymanager crashes and I'm getting logged out.

Especially strange as I have 16GB of ram.
Nvidia GTX 960, i7-5930K, kernel 4.14.13-1-ARCH, Arch Linux

It might be something related to my swap not getting filled much, on one test "on 100%" the heavy-memory-test-app did crash rather than kactivitymanager, but most of the time i'm greeted with black screen and logging screen with the log about kactivitymanagerd coredump.long

(I could get more ram ;) but still ... 16GB :/)
Comment 1 Ivan Čukić 2018-01-19 19:46:25 UTC
Now, first things first - you are not getting logged out because kamd crashes, kamd crashes because your session crashed. (kamd is quite nice in that regard - it, and most apps that use it are designed to continue working normally on 'connection-to-kamd-loss')

I'm not sure what can be the problem why the session gets killed when ram is full. Are you using proprietary nvidia drivers?

Have you tried to set the swappiness to allow swap to be used more?
Comment 2 kolorafa 2018-01-19 21:11:12 UTC
Short version:
Thanks for the tip, going over Xorg to fail a bug report.

Long version:
Yes, I'm using nvidia proprietary drivers.

I was misleaded because the failure doesn't produce any dmesg or journal log.

The real culprit was xorg, i did do next test and this time the screen just freezed, i did log into pc using ssh and found this:


[178630.668] (EE) 
[178630.668] (EE) Backtrace:
[178630.692] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x55adf3472169]
[178630.693] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7fceae3d0dff]
[178630.694] (EE) 2: /usr/lib/libc.so.6 (_int_malloc+0xb99) [0x7fceae088ef9]
[178630.694] (EE) 3: /usr/lib/libc.so.6 (_int_realloc+0x145) [0x7fceae089ab5]
[178630.695] (EE) 4: /usr/lib/libc.so.6 (realloc+0x2eb) [0x7fceae08acdb]
[178630.695] (EE) 5: /usr/lib/xorg-server/Xorg (ReadRequestFromClient+0x40c) [0x55adf3470efc]
[178630.695] (EE) 6: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x305) [0x55adf330c235]
[178630.695] (EE) 7: /usr/lib/xorg-server/Xorg (InitFonts+0x420) [0x55adf33102c0]
[178630.695] (EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xea) [0x7fceae028f4a]
[178630.695] (EE) 9: /usr/lib/xorg-server/Xorg (_start+0x2a) [0x55adf32f9f2a]
[178630.695] (EE) 
[178630.695] (EE) Segmentation fault at address 0x0
[178630.695] (EE) 
Fatal server error:
[178630.695] (EE) Caught signal 11 (Segmentation fault). Server aborting


[   854.815] (EE) 
[   854.815] (EE) Backtrace:
[   854.817] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x558984987169]
[   854.817] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7f3a94714dff]
[   854.821] (EE) 2: ? (?+0x50) [0xffffffcb0000001a]
[   854.821] (EE) 
[   854.821] (EE) Segmentation fault at address 0xffffffcaffffffca
[   854.821] (EE) 
Fatal server error:
[   854.821] (EE) Caught signal 11 (Segmentation fault). Server aborting