Control: tag -1 -unreproducible -moreinfo Control: severity -1 important Hi Norbert, Norbert Preining <norbert@preining.info> writes: > Hi Nicholas, > > On Wed, 09 Oct 2019, Nicholas D Steeves wrote: >> Version: 5.54.0-1 >> Severity: serious >> Justification: poor experience will cause user to give up on baloo; worse than GNOME > > Can you reproduce this with current frameworks 5.77 in unstable? > > Does it always crash at the same file (jack_capture_90.mp3) or always in > different files? > The crash is not specific to jack_capture_90.mp3; except for a period of time a couple of weeks long leading up to the original bug. Thank you for following up in this bug (finally someone did!) It's still too early in the freeze for me to upgrade this system to bullseye. Has anyone on the team tried testing baloo with a large $HOME? Mine is 131GB, in 142460 mixed files and directories. At the moment my baloo_file process is consuming over a terabyte (!) of memory. After resetting baloo and forcing a full reindex it takes a couple of weeks before it gets out of control again and crashes. Please don't sweep baloo bugs under the rug by tagging bugs containing crashes with obvious misbehaviour as severity "normal", eg: > id seems to have changed. Perhaps baloo was > not running, and this file was deleted + re-created > mdb.c:3124: Assertion 'pglast <= env->me_pglast' failed in > mdb_freelist_save() which is somewhere between important and serious https://www.debian.org/Bugs/Developer#severities Regards, Nicholas
Attachment:
signature.asc
Description: PGP signature