>>>We are testing Mozilla in our Win 32 application which run "unattended >>>24 hours a day" and have found a memory leak. Even a few bytes leak will >>>cause an application crash and this is not acceptable in our >>>environment.
Much as I am fond of Moz, I doubt it's going to be able to run unattended 24/7 for long periods just yet. >>>We would like to know if somebody is dealing with the same memory leak >>>problem and if a fix is available or coming soon. Without a little more detail than "there's a memory leak", no-one is going to be able to answer that question with any degree of confidence. >>If you are running on Windows, you should be automatically rebooting >>every few days for stability reasons anyway. > > Uh, yeah, maybe if you're still running Win98. Windows 2000 and XP are > rock-solid, I can't even tell you the last time I rebooted my machine > here. Which if you have any idea what's going on under the hood is > nothing short of miraculous. They're good, yes. They're better than Win98. But they're not bulletproof. I've seen win2k web servers go belly-up several times a day. The OS in this instance remains undisclosed beyond "win32" > Don't try to blame Mozilla's defects on Windows Gerv. I didn't see Gerv make any such accusation. He _implied_ that using win32 in a 24/7 environment was unwise. That's a point that can be argued to death over in alt.windows.sucks.no.linux.is.overrated.is.not.is.too.etc.etc.etc by those who wish to do so, but isn't really on topic here. > Don't try to blame Mozilla's defects on Windows Gerv. Why do you always use people's first names when criticising/patronising them, Gary? -- gav
