535779 - [Regression] Talos slowdowns due to bug 500280

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Mark Finkle (:mfinkle) (use needinfo?)]

Attachment: patch

Bug 500280 uses a 1 second timeout to delay initialize some XUL and JS. I tested that on the N900 and it did not slowdown startup.

On the N810, 1 second is not enough. See the Ts graph for example:
http://tinyurl.com/yf8fksr

After testing on the N810, I found a 2 second timeout does not affect startup.

I wish we had a better way of doing this.

Comment 1

[Mark Finkle (:mfinkle) (use needinfo?)]

2 seconds does not adversely affect the UX on the N900 either. I'd like to recover the Ts on the N810.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

This seems to me like we're just gaming the Ts test. I'm not sure there's much value in doing that, given that AFAICT it arbitrarily increases the risk that someone will fail to interact with the UI shortly after the window appears (I was already a big afraid of that happening with the original 1 second delay). If it has no effect on the n900 either way (why is that the case?), then why not just leave this as is?

Comment 3

[BMO Automation]

Closing all opened bug in a graveyard component