Start NT's task manager CPU graph so it's visible. Load the testcase. Now reload the test case and watch the CPU go up to 100% for quite a while, much longer than it took on the first load.
Assignee: trudelle → beppe
Component: XP Toolkit/Widgets → Editor
QA Contact: jrgm → sujay
I would suspect that this has to do with incremental reflow issues -- Anthony, can you verify that, and if that is the case, please reassign to layout for resolution
Assignee: beppe → anthonyd
adding perf and moving to m19
Target Milestone: --- → M19
Status: UNCONFIRMED → NEW
Ever confirmed: true
reviewed by Bijal and beppe, setting to nsbeta3+, p2
Severity: normal → major
Priority: P3 → P2
okay, on my machine, whether i do a reload, or a shift+reload, the CPU does spike to 100% for split second, but then its business as normal. The funny thing is, if I change focus and then change back I get the same spike. anthony continuing investigation
Status: NEW → ASSIGNED
Okay, I need mroe information on this bug. Blake, you were able to repro this on 9-3-2000, is there anymore infor you can give me, how long does it peg the cpu? Without a test case that demonstrates this to me i will have to invalidate this bug. anthony
I just tried this again and it doesn't seem to be doing the same thing it was before. Looks like the problem has gone away. There is something weird now though. Everytime you reload the page, according to the Task Manager, memory drops by a few k.
*** Bug 47452 has been marked as a duplicate of this bug. ***
okay, there must be some sort of misunderstanding, I know very well how to use task manager, so I will try again: 1. Do you still see the problem? 2. If yes, how long does it peg the cpu to 100? Thanks, Anthony
As currently described, PDT thinks this is an nsbeta3-. We're not signing up to prevent CPU spikes during program execution. Hangs, yes, but not brief spikes.
Whiteboard: [nsbeta3+][p:2] → [nsbeta3-][p:2]
Marking this bug as WORKSFORME. anthonyd
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Bug 48211 (duped to this through 47647 -> 47452 -> this) appears to be fixed now also. Typing in textareas seems to be fine now. Problem went away sometime late last week.
verified in 9/29 branch build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.