https://bugs.kde.org/show_bug.cgi?id=435294
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #5 from tagwer...@innerjoin.org ---
For what it's worth, I have now seen this....
It happens in certain situations; running the test code "wasn't sufficient" to
trigger the assertion.
For me, it did not seem necessary to force a race condition, that is to create
the folder tree quickly. Once baloo_file had crashed and was restarted, a
single "mkdir" was enough to cause it to crash again. Didn't need to recreate
the same folder with a mkdir, creating a different folder also caused a crash.
It seemed deterministic enough that a 'balooctl purge' and rebuild gets you to
back to a situation where you could trigger the assertion again with a "mkdir"
It was however not reproduceable to the extent that you could cause a crash (by
following the same sequence of commands) in a different user/home directory.
Not sure how much this helps, but I think it's enough to flag a CONFIRM.
--
You are receiving this mail because:
You are watching all bug changes.
