Problem scanning huge source (mem leak)?
Ha, ha. I'm pretty good at breaking things myself. :p
I consider it a useful skill, no fears. As I have said, I appreciate users that test rigorously, report clearly and persist!

For Krypton I fear it will be a matter of not using LDP with a very large library, or maybe an addon fix to space out the requests. Not sure we can get a full fix into the 17.1 deadline, given it seems to be a db wrapper issue (and I haven't found the exact problem yet). Despite how it shows up for your vast library on a RPi, it is not easy to reproduce generally. I've had to really push my win32/SQLite version to show it.

But testing with a large (fake) lib has brought home the difficulties that a large library presents. Will see what improvements I can make for v18 for sure.
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-10, 20:43
Logout Mark Read Team Forum Stats Members Help
Problem scanning huge source (mem leak)?0