javascript - Adobe AIR, memory leaks -
We all know that web browsers (like Firefox) are certain to meet memory consumption because we consistently execute javascript code (From the websites) that the memory is prone to leakage
I am debating in developing the desktop app, and I have given my experience with JavaScript / CSS / HTML, Give me a try Like I do not have to use Java (for example) and all of its GUI swing content is dealing with learning.
The problem is that I worry about the memory leak in AIR, because the Air Bus is a web browser with an API layer to interact with the operating system.
Is there a worry about memory leak in Air India? What should I do about this?
My name is Rob Kristensen and I am a product manager on Adobe Air First of all, let me say that Regardless of the underlying technology, it is quite easy to create a desktop application, which does not release large amounts of memory and / or memory.
In the next release of All India Radio, we will use Java-based applications AIR Runta to make memory leaks easier to identify The are looking to provide some additional capabilities. Developers who are building Flash or Flex based applications can take advantage of the memory profiler included in Flex Builder to track down. We are expecting JavaScript developers to do something similar.
In my experience while talking to developers, the memory leaks often occur when the objects in the memory are never cleaned. For example, imagine a Twitter client, which is based on a search keyword Lists Tweets from Overtime shows more results and the list grows, if there is no limit on the maximum number of tweets appearing, then surely, the memory will increase over time. Instead, the application should apply the appropriate limit on the number of items appearing in that list.
Some talks are available that describe the best practices for handling memory in AIR. Although the examples of this article are mostly written in action script, the same concepts also apply to javascript.
Display-Tuning Air App
If the runtime has leakage, then we should go as soon as we can. We encourage developers to know about such issues so that they send us back to our team using the following feedback form (www.adobe.com/go/wish).
If you are using an Ajax framework, you can know the known issues with Memory Leaks for that particular framework.
So, in a nutshell, yes, when you create a desktop application, you should always be concerned about memory - whether with AIR or C ++. As you are developing your application, you should monitor the memory usage of your application so that you can identify any issues later. One way to do this is to run longevity tests - to see if you have crawling the memory, keep it open overnight.
In general, the tools available for browser are very limited, I hope this will change soon because browser vendors have started providing more hooks in their browser to identify memory usage. . Hope this will help.
Thank you!
- Rob
Product Manager, Adobe Air
Comments
Post a Comment