Closed Bug 30926 Opened 25 years ago Closed 25 years ago

poll loop, gettimeofday, FIONREAD, colossal CPU activity in account wizard

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: hobbit, Assigned: alecf)

Details

Symptoms first spotted whilst browsing generally, but this is the first time I found a way to trigger it. Has been occurring whilst browsing with M14, but this incident was with the nightly, mozilla-i686-pc-linux-gnu.tar.gz from - er - I forget the filename, but the dates for the tarball files are all March 4th. BuildID: 2000030316. I also got the crypto stuff and applied that (psm-M14-pre1) (in case that's relevant, but I don't see how.) Clicked on mailto link and was told I needed to set up account. My mail server is neither POP3 nor IMAP, so left that as POP3, filled in my usual address, and clicked next. The barber's pole started whizzing round, the CPU monitor I have was doing overtime, but nothing was happening. (This may actually have happened before clicking anything: it's when I first noticed it. My partner thinks it started as soon as I opened the wizard/druid/whatever thing.) Tried strace. I think this is the important bit: huge huge huge amounts of this: poll([{fd=12, events=POLLIN}, {fd=6, events=POLLIN, revents=POLLIN}, {fd=14, eve nts=POLLIN}], 3, 0) = 1 gettimeofday({952468622, 346071}, NULL) = 0 ioctl(12, FIONREAD, [0]) = 0 poll([{fd=12, events=POLLIN}, {fd=6, events=POLLIN, revents=POLLIN}, {fd=14, events=POLLIN}], 3, 0) = 1 gettimeofday({952468622, 346438}, NULL) = 0 ioctl(12, FIONREAD, [0]) = 0 Killed the little box, and the CPU load dropped right back down. I've seen the CPU activity and the barbers pole whizzing round whilst Mozilla tells me the document is done a lot, usually whilst browsing, so I don't think this is a specifically mail thing. But how to reproduce it is :) Machine is a K6 with 32megs RAM running RH 6.1 Linux. The strace is from the one PID from 'top' which was registering very high CPU stuff: the others were all fine. If there is more information you need, let me know. (PS: I missed M13, but was enjoying M12. m14 is wonderful. Kudos!)
this was fixed in the last day or two.. just tried it, not causing me any extra CPU usage (I remember when it was causing 100% cpu usage, but it's not now)
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.