i.e. I just connect to the WiFi in London's office, after a few minutes the device stays connected to the AP but cannot actually access the internet (ipv6 kernel problems, afaik), so calendar sync starts failing.
At that point, I see dbus-monitor being spammed with events, and the memory taken by indicator-datetime-service increases until settling at 40-50% of the total memory in "ps", once the spamming ends.
Stacktrace without dbg symbols shows a malloc (as expected), need to try with more dbg syms
Thread 1 (Thread 0xb3ed9000 (LWP 2978)):
#0 0xb6897dea in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb689995e in malloc () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0xb6930000 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I managed to reproduce the problem by triggering /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1580146
https:/
i.e. I just connect to the WiFi in London's office, after a few minutes the device stays connected to the AP but cannot actually access the internet (ipv6 kernel problems, afaik), so calendar sync starts failing.
At that point, I see dbus-monitor being spammed with events, and the memory taken by indicator- datetime- service increases until settling at 40-50% of the total memory in "ps", once the spamming ends.
Stacktrace without dbg symbols shows a malloc (as expected), need to try with more dbg syms linux-gnueabihf /libc.so. 6 linux-gnueabihf /libc.so. 6 linux-gnueabihf /libc.so. 6
Thread 1 (Thread 0xb3ed9000 (LWP 2978)):
#0 0xb6897dea in ?? () from /lib/arm-
#1 0xb689995e in malloc () from /lib/arm-
#2 0xb6930000 in ?? () from /lib/arm-
Backtrace stopped: previous frame identical to this frame (corrupt stack?)