Has anyone noticed that the FileTransfer, Messaging and FileSystem API's appear to be significant memory hogs?
I can understand FileSystem being demanding, iterating through files and is best done in chunks with breaks in between to allow the garage collector to work.
I thought that the functions provided by the built in API's are supposed to use the "native" memory rather then the very limited "JS" memory, but it seems that sending and receiving messages and files results in disproportionate JS memory usage (in relation to what is being sent or received) which does not appear to be garbage collected even after many seconds have passed.
In general the garbage collection seems to be on the lazy on whole.
My observations are based on SDK4.2.2
What are your experiences with these API's?
