https://bugs.kde.org/show_bug.cgi?id=430058
--- Comment #3 from Ivan Čukić <ivan.cu...@kde.org> --- Hi Steve, Those files are automatically handled by sqlite. WAL is a write-ahead-log - a technique sqlite uses to avoid updating the database for each sql insert/update command. It writes the updates to WAL and then merges a chunk of them at once. KAMD only tells sqlite to flush WAL every 400k instead of the default 4M. Now, sqlite is free to ignore this request - it flushes only if the flush can be fast enough. So, the WAL file can grow more than that. This code (in KAMD) hasn't really been changed in 5 years. Did freebsd get a new version of sqlite recently? Now, Inkscape and KAMD have nothing in common - if KAMD manages to slow down Inkscape, my guess is that the OS doesn't handle file writes as it should. Maybe Inkscape is also trying to write something to the hard drive. Can you watch whe process IO with iotop to see what KAMD and Inkscape do when you experience the slowdown. Also, can you track the RAM usage while this happens? -- You are receiving this mail because: You are watching all bug changes.