906824 - "System JS : ERROR chrome://global/content/BrowserElementChildPreload.js:697 TypeError: content is null" in green Gaia UI test runs

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Ryan VanderMeulen [:RyanVM]]

Occurs in all Gaia UI test runs.

https://tbpl.mozilla.org/php/getParsedLog.php?id=26725231&tree=B2g-Inbound

b2g_ubuntu64_vm b2g-inbound opt test gaia-ui-test on 2013-08-19 10:20:06 PDT for push 5f27368e3159
slave: tst-linux64-ec2-433

10:22:43     INFO -  System JS : ERROR chrome://global/content/BrowserElementChildPreload.js:697
10:22:43     INFO -                       TypeError: content is null

Comment 1

[[:fabrice] Fabrice Desré]

We fail in _getScreenShot. We can guard against a null |content|, but unless the UI tests are running in a very different way than normal apps, I'd like to understand why we fail here.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

Jonathan, do you have any insight on comment 1?

Comment 3

[Jonathan Griffin (:jgriffin)]

(In reply to Fabrice Desré [:fabrice] from comment #1)
> We fail in _getScreenShot. We can guard against a null |content|, but unless
> the UI tests are running in a very different way than normal apps, I'd like
> to understand why we fail here.

We use Gaia API's to launch apps, rather than clicking icons on the homescreen...see https://github.com/mozilla/gaia-ui-tests/blob/master/gaiatest/atoms/gaia_apps.js.  But otherwise, we don't run apps differently.

These tests are all run on b2g desktop builds, so they're not OOP, if that makes any difference here.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Any updates here?

Comment 5

[[:fabrice] Fabrice Desré]

Attachment: patch

I can see the same error, along with one in Keyboard.jsm on my b2g desktop builds. This patch let us get rid of these.

Comment 6

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/integration/b2g-inbound/rev/cf0548c2a0dd

Comment 7

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/cf0548c2a0dd