The attached a message that, when displayed, causes N6 to enter a hard CPU loop (as indicated by the Windows task manager). N6 stops responding to user input, such as the delete button.
Esther could you have someone try this out and see if they can reproduce this?
Update: I tested this message with 6.2.1 and sure enough CPU usage was looping and I ended up having to end the task because NS6 was not responding. However, when I tested this same message with the nightly build 2002020703, I only see the CPU process looping, I no longer see NS6 diabled. I can delete the message, move to other messages and so forth. I only tried this on WinXP at this time.
Discussed in Mail News bug meeting with QA, PjM, and Engineering. Decision was to minus this bug and move to 1.2.
Keywords: nsbeta1+ → nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
per request by triage team, I checked to see if selecting another message or switching folders or other actions to take focus away from the message in question would stop the cpu usage loop, the answer is yes. The CPU usage loops only while that message is opened and again no crash or inability to use the app. Minus stands!
*** This bug has been marked as a duplicate of 98626 ***
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.