Closed Bug 204098 Opened 21 years ago Closed 21 years ago

Phoenix 0.6 Launches Slowly

Categories

(Firefox :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: beta-tests, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030428 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030428 Mozilla Firebird/0.6

Mozilla Firebird 0.6 seems to take longer to launch than 0.5.  On average,
Firebird's launch-time is around twelve seconds.

Mozilla Firebird 0.6 is the best browser for Windows, but its launch-time could
be improved.

Reproducible: Always

Steps to Reproduce:
1.  Launch Mozilla Firebird 0.6
2.
3.

Actual Results:  
The browser took around twelve seconds to launch.

Expected Results:  
Launched faster.

I'm using the default theme.
This bug report is almost useless. There is no Phoenix 0.6 and Mozilla Firebird
0.6 hasn't been released yet. 

Here the latest nightly build of Mozilla Firebird launches as fast as Phoenix 0.5. 
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
Well, I didn't think Phoenix 0.6 had been released, but that's what my build 
identifier says.  If you don't believe me, look at my original post.

As to this being a useless bug report...  If this <i>were</i> a bug report, it 
would be useless--I agree.  If you look, I filed this post as an 
enhancement.  As an enhancement, it isn't useless.  I realize this is a very 
small issue, but I think it needs to be addressed.  I also realize there are 
more important bugs that need to be addressed before smaller issues 
like launch-times, but I decided to go ahead and post it.
Your UA string doesn't say Phoenix 0.6. Period.

This bug report would have been better if you could provide some exact
measurements to compare the 0.5 milestone with the latest nightlies, such as
memory usage, startup time, etc.

You need to log in before you can comment on or make changes to this bug.