Thanks for the feedback. Glad that it works (though I think that MMA should fix the problem retroactively).

-Rusty

I've removed the data already, my phone was thankful. Haven't gotten to a video sync yet.

I'll say this is fixed in build 355. The fast conversion resulted in a nice, low 1.70MB of app data while the slow conversion gave an even better 1.29MB of data.

Any high data usage from the previous builds will still be there, of course, so Lowlander and anyone else will need to clear the app data manually but at least it shouldn't keep increasing now.

Thanks for fixing this issue.

Please give build 353 a try as soon as it's available (should be within 24hrs), and let us know...

Thanks.

-Rusty

No change in build 352. I followed the same procedure as the last test. After the fast conversion MMA was using 3.91MB, and after the slow conversion it was using 8.77MB. Again, this persisted after reboot.

Can you confirm whether the fix in build 352 solves the problem for you?

Thanks.

-Rusty

Yes, this persists after reboot.

The 444KB is correct, but that is after clearing the data so the database is empty at that point. That's measured by Android's app settings. I've done it again to create a screenshot and this time it came out at 440KB.

Yes, reboots don't lower MMA data usage.

And the higher memory utilization remains even after the device is rebooted. Correct?

Also, is 444KB utilization correct? I've never seen MMA use that little. How are you measuring utilization?

Thanks.

-Rusty

I have tested this by clearing the data then syncing a single video twice; once with 0% conversion quality for a fast sync and one with 100% conversion quality for a slow sync. The slow sync resulted in double the app data storage.

The process I used was:
1. Set 0% conversion quality in MMW.
2. Clear app data, delete MediaMonkey folder, and delete all media.
3. Open MMA and select the sync server, but do not sync yet.
4. Read app data usage, which was 444KB.
5. Sync.
6. Read app data usage, now at 4.43MB.

7. Set 100% conversion quality in MMW.
8. Clear app data, delete MediaMonkey folder, and delete all media.
9. Open MMA and select the sync server, but do not sync yet.
10. Read app data usage, which was again 444KB.
11. Sync.
12. Read app data usage, now at 8.69MB.

I forgot to check the size of the converted file, but since the source file and target bitrate was the same for both tests I assume they would be a similar output size. It looks like MMA's app data usage increases with time spent syncing with MMW, regardless of the content of the sync.

I've rebooted both devices. The tablet that I use for video increased from 522MB to 529MB while the phone barely changed from 65.43MB to 65.44MB.

I then tried running a sync on the tablet to see how it affected the amount of app data. The videos take about an hour to convert so there was a long period with MMA just waiting, but I noticed that the amount of data was gradually increasing during this period. Over the hour it went from 532MB to 534MB even though there was no active transfer. I am vaguely aware that MMW sends the sync progress to MMA as XML data, so could it be that MMA is logging every status update and storing the logs indefinitely? This could explain why the data storage increases over time on both devices, why converting video results in drastic increase in data storage compared to audio, and why the usage stops at 2GB assuming the log file is trimmed at that point.

I also monitored the app data storage while the video file was being transferred, and disconnected the WiFi a little after half way through the transfer to force a failure. Neither of these activities noticeably increased the data storage.

Would it be possible to get a rough idea of what MMA's memory utilization is on your devices after a reboot?

Then what it changes to after a sync?

Is it device-specific?

I've tried cancelling syncs, and syncing large amounts of data, but am not seeing the problems you're observing.

Thanks.

-Rusty

Canceled syncs and video happen here too. Perhaps MMA fails to clean temporary/cached data if things go wrong (canceled sync) or stores excessive data for video files.

I also see this excessive data storage. I have two devices; one has about 1200 audio tracks and the other has the same audio tracks plus 15 videos. The device with only audio currently has 66MB of data stored for the app while the video device has 522MB of data stored. In the past I've seen the video device get up to 2GB of data stored for MMA, and it stays at 2GB until I clear the data.

I can't say with certainty but I have noticed a correlation between cancelled/failed syncs and increased app data storage. My guess is that MMA is creating temporary files during sync that aren't cleared when the sync fails.

It's around that total among both memories. Not that much files. I do do regular syncs changing out the files (most are random AutoPlaylists). Still 250MB seems excessive and is causing memory issues.