Closed Bug 460583 Opened 16 years ago Closed 16 years ago

Fennec: startup time, especially on 1st startup is too slow on N800. No feedback provided.

Categories

(Firefox for Android Graveyard :: General, defect)

Other
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 431824

People

(Reporter: t3st3r, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3 Build Identifier: Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.1b2pre) Gecko/20081015 Fennec/1.0a1 I'd installed Fennec 1.0a1 on my Nokia N800. Then I'd started it. Then, Nokia displays loading popup but is timeouts soon. Then no any feedback within minute or so. I was actually not sure that Fennec going to start at all. At least, provide some feedback that you're starting and not died. Or, better, improve startup time. First startup time is really horrible. It takes nearly minute to start Fennec on N800. MicroB starts slightly faster. Subsequent start times are not so horrible but still slightly worse than MicroB's startup times. They SHOULD be improved. And until this is not true at least provide feedback that app is really starting. Waiting without indication is not what users like. Really. Reproducible: Always Steps to Reproduce: 1.Launch Fennec 2.Measure startup time 3.Ensure that Nokia's startup popup disappears slightly before app window created. This causes long gap without progress indication.User may think application failed to start. Actual Results: Very slow startup time. No progress indication given - nothing on screen and only CPU and RAM usage changes a bit (you can only see this if you'll install extra cpu monitoring applet). Expected Results: 1. Faster startup times 2. If startup time slightly longer than OS's indication of app loading, you have to at least display something so user is aware that app is not died and willing to start.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
verfied as duplicate of bug 431824
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.