desktop-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

I just tried Tony's lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals branch and did the same thing I've done before to
trigger this bug: walk around my neighborhood with Terminal open,
running top.

To be fair, I was testing rc-proposed tip + Tony's branch, whereas I
previously tested with OTA6.  So there's more than one change here.  But
I haven't heard of related changes in this area, so I will attribute all
improvements to Tony's branch.

Before this patch, I was seeing NM spike to 30-50% CPU while scanning
and causing a matching spike in dbus-daemon to 100% for a while (at
least 3s, sometimes a fair bit longer).

With this patch, NM stayed at ~15% when scanning, and dbus-daemon never
went above 7% (usually at 4%).  A massive improvement.

>From a UX perspective, I still saw UI stuttering.  Seemingly without the
CPU-load justification to warrant it.  But I subjectively don't think it
was as bad or long-lasting as before.  And top doesn't lie.  The CPU was
way less loaded with this patch than without it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu RTM:
  In Progress

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions