https://bugs.kde.org/show_bug.cgi?id=437774
--- Comment #5 from pbs3...@googlemail.com --- Maybe you couldn't reproduce it because you need a spinning disk and low ram to cause enough latency to trigger the bug, and your computer is too good. There's also another (mostly theoretical) race condition: if the document is updated between saving and re-enabling the file watcher, the modification will be missed. Both race conditions (and therefore probably also the bug) can be fixed by recording the timestamp when the document was saved, and ignoring modifications with the same timestamp. If you foresee no problems with this, I can write up a patch and test it out over the next week, then report back whether the bug has disappeared or not. -- You are receiving this mail because: You are watching all bug changes.
