I'm reluctant to think that we should continue to let his happen to our users while we figure out a perfect solution, if an imperfect solution can solve most and maybe all of the user-visible manifestation of the problem. To my knowledge we've never managed to capture an example of on-disk file corruption in-situ on machines where this has manifested itself, and that plus the fact that a restart _always seems to fix it_ suggests whatever the multiplicity of causes here might be, the overwhelming majority of them don't live on disk.
Bug 1773504 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm reluctant to think that we should continue to let his happen to our users while we figure out a perfect solution, if an imperfect solution can can be deployed quickly that solves most and maybe all of the user-visible manifestation of the problem. To my knowledge we've never managed to capture an example of on-disk file corruption in-situ on machines where this has manifested itself, and that plus the fact that a restart _always seems to fix it_ suggests whatever the multiplicity of causes here might be, the overwhelming majority of them don't live on disk.
I'm reluctant to think that we should continue to let his happen to our users while we figure out a perfect solution, if an imperfect solution that can be deployed quickly solves most and maybe all of the user-visible manifestation of the problem. To my knowledge we've never managed to capture an example of on-disk file corruption in-situ on machines where this has manifested itself, and that plus the fact that a restart _always seems to fix it_ suggests whatever the multiplicity of causes here might be, the overwhelming majority of them don't live on disk.