Closed Bug 530282 Opened 15 years ago Closed 14 years ago

QA Companion (in Tools->Options [Testing] Tab) takes long time to load simple info

Categories

(Firefox :: Settings UI, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rob1weld, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4pre) Gecko/20091119 Namoroka/3.6b4pre (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4pre) Gecko/20091119 Namoroka/3.6b4pre (.NET CLR 3.5.30729)

The "QA companion Info Page", produced by clicking on Tools->Options in the " [Testing] Tab" area, takes a very long time to load such simple info.

The first time this info is determined it can takes over 20 seconds and repeat attempts to get the info still take 2 or 3 seconds (on a fast computer).

The "Platform", "Operating System", "Product", and "Branch" info are determined much too slowly.


Reproducible: Always

Steps to Reproduce:
1. Start Namaroka and install "QA Companion".
2. Click on "Tools->Options" and click the "QA Companion" pane.
3. View the "[Testing]" Tab (default).
4. See the "Platform", "Operating System", "Product", and "Branch" areas load very slowly (and ONE at a time, no multi-tasking?).

Actual Results:  
Slow loading of trivial info.

Expected Results:  
This information _could_ be determined and displayed almost instantly, one second waiting would be slow but half a minute is much too slow.

I can visit a Website like BrowserSpy and get some of this info about my Browser _faster_ than the "Browser's Info Page" can tell me information about my own computer. 

Is something blocking these subroutines from determining this simple info in a reasonable amount of time (less than a 1/10 of a second).
That info loads quickly in 3.6.12 so I'll close this old BR.
Rob
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
please use WORKSFORME rather than FIXED when it's not known what patch or other bug fixed the issue.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.