memory spike running unity with -testability

Bug #1209485 reported by Paul Larson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot Qt Support
New
Undecided
Unassigned

Bug Description

We started running unity with -testability today in order to use a new automatic screen unlocking method. The result of doing that before some memory usage tests seems to be that it caused a spike in memory usage for unity. Details can be found at: http://reports.qa.ubuntu.com/memory/memevent/image/10/machine/mako/event/Browser%20started/detail/

Tags: qa-touch
Revision history for this message
Thomi Richards (thomir-deactivatedaccount) wrote : Re: [Bug 1209485] [NEW] memory spike running unity with -testability

Looks to me like a 2MB memory spike when the Greeter is introspected. This
is probably caused by the tree traversal done to find the greeter in the
first place.

We should:

1) make sure autopilot is generating absolute queries only, so we don't
load the entire tree into memory at any point.

2) Look at autopilot-qt for places where we can reduce the class memory
footprint. I suspect we can make a few improvements there.

On Thu, Aug 8, 2013 at 4:38 PM, Paul Larson <email address hidden>wrote:

> Public bug reported:
>
> We started running unity with -testability today in order to use a new
> automatic screen unlocking method. The result of doing that before some
> memory usage tests seems to be that it caused a spike in memory usage
> for unity. Details can be found at:
>
> http://reports.qa.ubuntu.com/memory/memevent/image/10/machine/mako/event/Browser%20started/detail/
>
> ** Affects: autopilot-qt
> Importance: Undecided
> Status: New
>
>
> ** Tags: qa-touch
>
> --
> You received this bug notification because you are a member of Autopilot
> Hackers, which is subscribed to Autopilot Qt Support.
> https://bugs.launchpad.net/bugs/1209485
>
> Title:
> memory spike running unity with -testability
>
> Status in Autopilot Qt support:
> New
>
> Bug description:
> We started running unity with -testability today in order to use a new
> automatic screen unlocking method. The result of doing that before
> some memory usage tests seems to be that it caused a spike in memory
> usage for unity. Details can be found at:
>
> http://reports.qa.ubuntu.com/memory/memevent/image/10/machine/mako/event/Browser%20started/detail/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/autopilot-qt/+bug/1209485/+subscriptions
>

--
Thomi Richards
<email address hidden>

Revision history for this message
Andy Doan (doanac) wrote :

On 08/08/2013 02:54 AM, Thomi Richards wrote:
> 1) make sure autopilot is generating absolute queries only, so we don't
> load the entire tree into memory at any point.

Does this mean its related in part to:

  https://blueprints.launchpad.net/bugs/1194763

Revision history for this message
Thomi Richards (thomir-deactivatedaccount) wrote :

Hi,

On Fri, Aug 9, 2013 at 3:42 AM, Andy Doan <email address hidden>wrote:

> On 08/08/2013 02:54 AM, Thomi Richards wrote:
> > 1) make sure autopilot is generating absolute queries only, so we don't
> > load the entire tree into memory at any point.
>
> Does this mean its related in part to:
>
> https://blueprints.launchpad.net/bugs/1194763

No, not really. Autopilot should be generating absolute queries in most
cases anyway, depending on which methods you call. We just need to make
sure that's still the case.

--
Thomi Richards
<email address hidden>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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