Closed Bug 61537 Opened 25 years ago Closed 25 years ago

second time slower to launch subscribe

Categories

(SeaMonkey :: MailNews: Message Display, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
Future

People

(Reporter: sspitzer, Assigned: sspitzer)

Details

(Keywords: perf, Whiteboard: [nsbeta1+ 1/25])

I thought my fix to remove the nsCStringArray hack would fix this, but it's still there. on a recent release build, putterman showed me that subscribe on news.mcom.com is fast the first time, but gets slower the second time he launches the subscribe dialog. 2 seconds first time 10 seconds the second time. a new bug for this, since I don't want to reopen the nsCStringArray bug, since I fixed that bug when I removed the nsCStringArray hack. I guess they weren't related, like I thought. damn.
QA Contact: esther → stephend
adding keywords.
Keywords: mail2, perf
I'm seeing this again also on NT, build 2000120804, and performance again is bad, althought not quite as bad as bug 61670.
This feels like XP stuff, happens on Linux 2000120808. Setting to ALL.
OS: Windows NT → All
Hardware: PC → All
marking nsbeta1+ and moving to mozilla0.8
Keywords: nsbeta1
Priority: P3 → P2
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.8
Keywords: mail2mail1
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9
marking nsbeta1-
Keywords: nsbeta1nsbeta1-
Whiteboard: [nsbeta1+] → [nsbeta1+ 1/25]
Target Milestone: mozilla0.9 → Future
This bug is working for me using 2001022805 on Windows 2000, and build 2001022808 on Linux (Mandrake 7.2, KDE) I'm going to check bonsai/tinderbox to see what was checked in to make this noticeably faster. It's almost immediate from the time you do any of the methods: File | Subscribe and using the context menu.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search
You need to log in before you can comment on or make changes to this bug.