Problem scanning huge source (mem leak)?
Just for the record (and meditation purposes) here is a plot of the memory log from above (MySQL and RPi)
Image

After overlapping calls, there is some phased recovery, but never back to the beginning levels. In my testing I have tried waiting, but "natural healing" does not happen.

Here fetching fewer albums takes less memory, but the leak still happens. In my testing (on win32 and SQLite) I seem to need to fetch large amounts of data to see this issue.

Thread safety has been discussed as a possible cause, but every JSON call in effect initiates its own connection to the db so this does not seem to be the issue.
Reply


Messages In This Thread
RE: Problem scanning source - by DaveBlake - 2017-02-12, 13:00
RE: Problem scanning source - by Uatschitchun - 2017-02-12, 21:51
RE: Problem scanning huge source (mem leak)? - by DaveBlake - 2017-03-11, 17:20
Logout Mark Read Team Forum Stats Members Help
Problem scanning huge source (mem leak)?0