Alec Flett Reporter
	Description • 24 years ago

Jud's issues with string bundles, and a discussion with Bill yesterday, made me
realize that we're spending some of our startup time opening and parsing the
bookmarks file.. in reality, this should be an async operation that goes on in
the background, hopefully on another thread, and does not stop the main thread
from proceding forward.

What we should do is kick off a URL load at startup, and as data arrives from
the load, we parse it, and build up the in-memory datasource. This means that
the first window can appear before bookmarks are even loaded!

(this might confuse the personal toolbar if we're still having problems building
up toolbar content on-the-fly but that's the subject of another bug)

	Cathleen
	Comment 1 • 24 years ago

alec, can you take a look at this for moz 0.9 or 1.0?  We're reading entire 
bookmark file before we diaplay the first window.   It would be great if we can 
load bookmark asynchronously, or delay loading the book mark till after first 
window shows.

	Paul Chen
	Comment 2 • 24 years ago

nav triage team:

Reassigning to pchen for investigation. Marking nsbeta1+ and mozilla0.9.1

	Paul Chen
	Comment 3 • 24 years ago

Along the way of doing startup analysis, I can't see where this is eating too
many cycles. Certainly on my admittitly small amount of bookmarks, loading
doesn't take very long, ~50ms. Also, bookmarks load during loading of
navigator.xul, so I think it's instantiated at the correct place also.

Marking nsbeta1- and future

	Viswanath Ramachandran
	Comment 4 • 24 years ago

renominating. 

	Paul Chen
	Comment 5 • 24 years ago

nav triage team:

Marking nsbeta1+ and mozilla0.9.4

	Daniel Bratell
	Comment 6 • 24 years ago

I've seen bookmarks being high up on profiles with really big bookmark files.
There are people out there with thousands of bookmarks and I would expect that
to be many seconds of startup time.

	Paul Chen
	Comment 7 • 23 years ago

nav triage team:

This isn't going to make the mozilla0.9.4 train. Pushing out to mozilla1.0.1

	Paul Chen
	Comment 8 • 23 years ago

Pulling back in to mozilla0.9.7

	Paul Chen
	Comment 9 • 23 years ago

Ok, I don't think this is as important since we got delayed loading bookmarks.
Also, async loading will make loading bookmarks take even longer. Marking
mozilla1.0.1 and adding helpwanted

	Judson Valeski
	Comment 10 • 23 years ago

how would async loading take "longer"?

	Peter Trudelle
	Comment 11 • 23 years ago

mass-reassign bookmarks & open pref perf bugs from pchen to ben

	Samir Gehani
	Comment 12 • 22 years ago

Nav triage team: nsbeta1-

	Robert Kaiser
	Comment 13 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 14 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 15 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 16 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 17 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 18 • 16 years ago

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

	Robert Kaiser
	Comment 19 • 15 years ago

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420