Comment 1 for bug 1209485

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>