[kactivitymanagerd] [Bug 389128] When full physical memory - Process (kactivitymanage) of user 1000 dumped core.

[kolorafa]

https://bugs.kde.org/show_bug.cgi?id=389128

kolorafa  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from kolorafa  ---
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) [0xffcb001a]
[   854.821] (EE) 
[   854.821] (EE) Segmentation fault at address 0xffcaffca
[   854.821] (EE) 
Fatal server error:
[   854.821] (EE) Caught signal 11 (Segmentation fault). Server aborting

-- 
You are receiving this mail because:
You are watching all bug changes.

[kactivitymanagerd] [Bug 389128] When full physical memory - Process (kactivitymanage) of user 1000 dumped core.

[Ivan Čukić]

https://bugs.kde.org/show_bug.cgi?id=389128

--- Comment #1 from Ivan Čukić  ---
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?

-- 
You are receiving this mail because:
You are watching all bug changes.