Closed Bug 30474 Opened 25 years ago Closed 23 years ago

Prefs: category (pane) switching is slow (seconds)

Categories

(SeaMonkey :: Preferences, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: jruderman, Assigned: bugzilla)

References

(Depends on 1 open bug)

Details

(Keywords: perf, Whiteboard: [nsbeta3-] se-radar [nav+perf])

The preferences window takes up to several seconds to switch categories after I click on a new category. If there's no way around the slowness, the right pane should be cleared until the new category can be displayed so the user knows mozilla is trying to do something.
Confirmed with: 2000-03-05-08-M15 on WinNT on a K6-450 and on a P-90. The degree of lag depends largely on the speed of the machine, but it can take seconds, especially to display the Fonts pane if hundreds of fonts are installed, and even on a reasonably fast machine, few panes take less than 1/10 second to display. The usual way to indicate this range of delays is the hourglass cursor, which may be appropriate here if general performance improvements do not get the maximum delay under 1 second on a slow machine.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: perf
Summary: Prefs: category switching is slow → Prefs: category (pane) switching is slow (seconds)
Target Milestone: M16
common to all platforms... even i notice it, and i've some spiff machines: new 450 mhz G3 (macOS 9.0), new pentium IIIs (450-500 mhz, cannot remember) that run winNT (4.0, sp5) and linux (redhat 6.0, 2.2.12-20 kernel, Enlightenment/gnome).
OS: Windows 98 → All
Hardware: PC → All
Target Milestone: M16 → M18
Move to M21 target milestone.
Target Milestone: M18 → M21
*** Bug 44745 has been marked as a duplicate of this bug. ***
nominating for beta3 to fix whatever it takes to speed this process up. * beta3 is supposed to focus on performance and speed * this is one of the biggest areas of noticeable slowdown in the product; many have described the process as overall 'painful' what's the problem here?
Keywords: nsbeta3
Marking [nsbeta3-]. Anything we can do here is likely addressed by general window opening performance bugs.
Whiteboard: [nsbeta3-]
spam: adding mostfreq, not necessarily due to many dups, but because i run into this problem frequently (thus want to get it my queries easily).
Keywords: mostfreq
Removing mostfreq - this bug does not qualify for this keyword under the established criteria. Gerv
Keywords: mostfreq
adding se-radar to status so that i can find this bug more easily. pls don't remove it [yet], thx.
Whiteboard: [nsbeta3-] → [nsbeta3-] se-radar
nav triage team: Not going to happen for beta, but hyatt did some stuff that supposedly sped up switching pref panes. Marking nsbeta1-
Keywords: nsbeta1-
--> me
Assignee: matt → blake
Whiteboard: [nsbeta3-] se-radar → [nsbeta3-] se-radar [nav+perf]
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Target Milestone: mozilla0.9.5 → mozilla1.0
File specific bugs please.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Target Milestone: mozilla1.0 → ---
mass verification of Invalid bugs: to find all bugspam pertaining to this, set your search string to "MagaritaLuisaChascarilloAvoidsInvalidBugs". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. where relevant, do check that it's actually still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear, compelling reasons why this bug should be considered a valid one.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.