> >>>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 already noticed this (and IE does not work better !!!). So should we expect good results in a reasonable delays if we work on tracking down memory leaks in Mozilla ??? > > > >>>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. > Some bytes are Leaked every time a new page is rendered. The number of bytes leaked is very probably dependant of the content of the page itself. Calling the NavigateToURI function every 1 second can cause a system crash in 24hours. > > >>If you are running on Windows, you should be automatically rebooting > >>every few days for stability reasons anyway. Our application (without the Mozilla option) can run continuously (on Windows NT) without any need to reboot even for a few moths. Sure, we don't use the same system resources than Mozilla, but this is not the reason to challenge Windows.
