Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Learn More

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

Memory leak tracking tools

  • 2 yanıt
  • 10 kişi bu sorunu yaşıyor
  • 5 gösterim
  • Son yanıtı yazan: kobe

988247
988247
more options

Hi, All Mozilla experts:

Firstly, I'd appreciate you for all the excellent softwares and developer guides that published by mozilla and firefox groups.They are do helping the whole human community moving forward.

We have a rich web application which contains probably more than 200,000 lines of javascript code and the product is required to be running 7*24 without closing browsers or refreshing pages.

Of course, There comes memory leak.

The same as trying to find a needle in the sea, It's very hard to track the problem among all the hundreds of thousands lines of code. We tried to find some tools that may help us to detect the javascript codes causing memory leak.

None.sIEve does not work in our scenario, javascript validator requires firefox 4 and make no sense even when we downgraded our browsers to the required version, microsoft's tool works only for IE7 while we are targeting IE8+...

Then we began to dive into browser codes, analyzing Firefox, hoping to solve memory leak problems from the host environment, at least we may know the mechanism of how DOM objects and js objects are orgnized in browser...

Then we found some tools that may help tracking memory leaks, I mean, an awesome lot of tools listed in this page: https://wiki.mozilla.org/Performance:Leak_Tools.

However, the more we read, the more we began to question ourselves: are these tools used to track web application memory leaks, or memory leaks existing in Firefox itself? It's really embarrassing cause we are all Java/Javascript developers and C++ codes are a little bit monsters for us all...

So, could you please give us some suggestions that whether we should proceed on the way to analyze these tools? Will they do us some help to track our problems? And, If we should not, Are there any other tools (Other than sIEve, Javascript Validator, Microsoft's IEMemoryLeakDetector, Chrome Developer Tool cause we are not supporting chrome for now.) you would suggest us to use to hasten our process?

Your help and suggestions are awefully appreciated, really.

Regards, Christian

Hi, All Mozilla experts: Firstly, I'd appreciate you for all the excellent softwares and developer guides that published by mozilla and firefox groups.They are do helping the whole human community moving forward. We have a rich web application which contains probably more than 200,000 lines of javascript code and the product is required to be running 7*24 without closing browsers or refreshing pages. Of course, There comes memory leak. The same as trying to find a needle in the sea, It's very hard to track the problem among all the hundreds of thousands lines of code. We tried to find some tools that may help us to detect the javascript codes causing memory leak. None.sIEve does not work in our scenario, javascript validator requires firefox 4 and make no sense even when we downgraded our browsers to the required version, microsoft's tool works only for IE7 while we are targeting IE8+... Then we began to dive into browser codes, analyzing Firefox, hoping to solve memory leak problems from the host environment, at least we may know the mechanism of how DOM objects and js objects are orgnized in browser... Then we found some tools that may help tracking memory leaks, I mean, an awesome lot of tools listed in this page: https://wiki.mozilla.org/Performance:Leak_Tools. However, the more we read, the more we began to question ourselves: are these tools used to track web application memory leaks, or memory leaks existing in Firefox itself? It's really embarrassing cause we are all Java/Javascript developers and C++ codes are a little bit monsters for us all... So, could you please give us some suggestions that whether we should proceed on the way to analyze these tools? Will they do us some help to track our problems? And, If we should not, Are there any other tools (Other than sIEve, Javascript Validator, Microsoft's IEMemoryLeakDetector, Chrome Developer Tool cause we are not supporting chrome for now.) you would suggest us to use to hasten our process? Your help and suggestions are awefully appreciated, really. Regards, Christian

Tüm Yanıtlar (2)

messagebot
messagebot
more options

Hi,

Unfortunately we had a data base error today and lost some user accounts when we had to go back to our backups. If you have started this thread, your's is one of those. Since we can not recreate your account, please sign-up for a new account here to reply to the forum messages:

https://support.mozilla.org/users/auth

You can use the same username and email address as before. We are very sorry for the inconvenience.

kobe
kobe
more options

I think whats on that page you linked is used to find Firefox memory leaks in its self. I would wait until someone other than me (who knows code) comes to the rescue.

Please disregard messagebot unless your account was affected.