151185 - Korean Characters in bookmarks require a lot of CPU

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, defect)

Description

[Erich 'Ricky' Iseli]

Ways to reproduce:

1) go to http://yahoo.co.kr/
2) create a folder in your personal toolbar folder
3) file bookmark of the page in that folder
4) close Mozilla
5) start it again
6) click on the folder where you have yahoo.co.kr bookmarked and watch your CPU
monitor

=> Result: for 1 or 2 seconds, nothing happens, the CPU goes to 100%, then only
the bookmark folder pops up.

Expected result: should go without delay, without using as much CPU

By the way, I used pre-1.1a (june 11) build as well as Mozilla 1.0. Did this
with a fresh profile, so this is not the issue.

Comment 1

[Erich 'Ricky' Iseli]

I'm still using Mozilla 1.0, but after adding EasySearch (
http://easysearch.mozdev.org ) - which adds itself into the personal toolbar now
- I can't see the problem any more. I have no idea why it changes behavior.
Anyone can look into this?

Comment 2

[Robert Kaiser]

MASS-CHANGE:
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

Comment 3

[Robert Kaiser]

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