The workaround mentioned here
https://github.com/google/sanitizers/issues/1716
sudo sysctl vm.mmap_rnd_bits=28
made the problem go away for me.
** Bug watch added: github.com/google/sanitizers/issues #1716
https://github.com/google/sanitizers/issues/1716
--
You received this bug notificat
64-bit Kubuntu Natty. Killing pppd while having kded4 running makes
kded4 go wild. Attached with gdb and got the stack trace in
StackTrace.txt. Further inspection revealed that the process was stuck
looping within frame #1.
** Attachment added: "StackTrace.txt"
https://bugs.launchpad.net/ubunt
I can reproduce this in the following way:
- Connect to network using wvdial to control hspda modem and make sure that
kded4 is running
- Interrupting wvdial makes that process exit, but network connection is still
on (pppd does not exit)
- Kill pppd
As a result of this, kded4 goes wild eating 10
