From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.0rc3) Gecko/20020523 BuildID: 2002052306 I did not find such a bug in the database, but it must be there... Ok, it is with Mozilla 1.0 RC3: After some browsing (using tabs) and opening and reading mail, getting new mail, etc. (i.e. just using Mozilla) something seems to hog the CPU completely. I can stop Mozilla, but that does not help. In task manager, I observe a process "news upd" which does not respond. This must be from Mozilla, I assume. Memory leaking is quite heavy as well. What have you done with RC3??? Sorry, but I´m just disappointed. My system: OS: Windows 98SE 512 MB RAM Athlon XP 1600+ Reproducible: It just happens after heavy usage, sorry...
Mozilla has no child processes listed in the Task Manager, to my knowledge. The only process we list is mozilla.exe/netscape.exe (commercial build) As far as memory leaking - are you sure it's a memory leak, or just a lot of allocations? If you wish to file a memory leak bug, please first search bugs listed with 'mlk' in their keywords field. Memory leaks are very specific and can't just be filed as 'I surfed and it leaked'. As I have no process 'news upd' and nothing has hung with build 6-7-2002 on Windows 2000 lately, I'm marking this worksforme.
Sorry, the news upd thing was a fault from my side. Just some spyware by creative (Soundblaster driver installs it). Incredibly... I have removed it. But still, without that spyware I get the behaviour which I described. The whole maching slows down and finally my internet connection does not work. I can stop Mozilla. When a want to shut down windows and perform a re-start, windows hangs. Ctrl-Alt-Del is the only way then. I don´t know where it comes from, but I think it startet when I installed RC3... Leaving it as worksforme. If I get more information, I may edit the bug.
Thorsten - have you reduced the set of steps to reproduce the problems you are describing? Without an easy, 100% reproducible testcase (or a leak log of some sort), this bug isn't going to be very helpful (sorry).
okay, verified (for now).