> It seems one must ensure no 'prepared' statements are used after
> finalize, otherwise a segfault can ensue.
Yeah, that's what I was after when I investigated this last time.
> I've just run a full scan and memory got to over 90% (and plenty of swap
> available), but didn't exceed that.
How much memory would the scanner take? How large is your library?
> I also noticed it did a database
> optimize twice, repeating it after the artwork pre-cache - is that
> normal? The first optimize was not reported in the scanner log
> (attached).
Hmm... how did you see it was run the first time?
> For the overnight scan I also do a Custom Scan. I haven't done that now
> since the Custom Scan takes 4 hours or so.
Thanks. Asking to disable 3rd paryt extensions would have been next ;-).
Could you please disable the Fulltext plugin and try again?
--
Michael
> finalize, otherwise a segfault can ensue.
Yeah, that's what I was after when I investigated this last time.
> I've just run a full scan and memory got to over 90% (and plenty of swap
> available), but didn't exceed that.
How much memory would the scanner take? How large is your library?
> I also noticed it did a database
> optimize twice, repeating it after the artwork pre-cache - is that
> normal? The first optimize was not reported in the scanner log
> (attached).
Hmm... how did you see it was run the first time?
> For the overnight scan I also do a Custom Scan. I haven't done that now
> since the Custom Scan takes 4 hours or so.
Thanks. Asking to disable 3rd paryt extensions would have been next ;-).
Could you please disable the Fulltext plugin and try again?
--
Michael