Hi, I ran in the same problem and it is not really a memory leak. The bug is more, that kscreenlocker_greet tries to allocate 2 GB of RAM:
mmap(NULL, 2147483648, PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) And it doesn't care about the return value. More worse, I did disable overcommit_memory. With overcommit_memory=0 you won't see the problem. So the memory is not really needed. But why does kscreenlocker_greeter try mmap so much memory? Best regards Dirk -- +----------------------------------------------------------------------+ | Dr. Dirk Geschke / Plankensteinweg 61 / 85435 Erding | | Telefon: 08122-559448 / Mobil: 0176-96906350 / Fax: 08122-9818106 | | d...@geschke-online.de / d...@lug-erding.de / kont...@lug-erding.de | +----------------------------------------------------------------------+
