Ubuntu
unity-scopes-shell package

Dash startup time can have a large delay

Bug #1579859 reported by Pat McGowan
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Triaged
High
Alejandro J. Cura
Canonical System Image backlog
unity-scopes-shell (Ubuntu)
Confirmed
Undecided
Paweł Stołowski

Bug Description

While testing fixes for bug #1578283 there was a large discrepancy in how long it took to initialize the scope contents from boot to boot. Often a black screen was shown for up to 10 secs followed by the scope icon then the content, total time well over 12 secs.

While there were some crash files at boot that was not consistent with the symptom

MX4 proposed v319

See original description
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Black screen on unlock

description: updated
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
assignee: nobody → Alejandro J. Cura (alecu)
importance: Undecided → High
milestone: none → 12
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-scopes-shell (Ubuntu):
status: New → Confirmed
Pat McGowan (pat-mcgowan)
Changed in unity-scopes-shell (Ubuntu):
assignee: nobody → Pawel Stolowski (stolowski)
Changed in canonical-devices-system-image:
milestone: 12 → 13
Revision history for this message
Paweł Stołowski (stolowski) wrote :

There are two aspects of these symptomps:
1) black screen with Scopes icon is shown before Dash is loaded and started I believe;
2) white screen (blank) is shown when Dash is loaded and is getting initialized (scope-registry is queried for installed scopes, then first two scopes are loaded, queried & prepopulated to show content immediately after unclock).

Both cases are largely affected by the fact that many other processes are started at about the same time and the CPU gets pretty busy. The 2nd case may be impacted if scope uses network (or a slow backend); it's not normally visible unless you unlock really fast (immediately after unity8 start).

Attaching bootchart graph (data was collected on the BQ phone from 9 boot sequences).

I'm not ruling out any possibility for an improvement, but it's unlikely to be a single thing which suddenly improves the situation, but rather a bunch of smaller improvements here and there (such as perhaps re-arranging how things are initialized in unity8 or elsewhere?).

Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
status: Confirmed → Triaged
milestone: 13 → backlog
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.