I forgot about this, but I was reminded by a recent discussion on another issue.
A while ago it happened to me to have a 100% full Windows system drive.
That resulted in constant NVDA errors. I used a snapshot back then, so NVDA became unusable. I'm not sure if that would be the case with a stable version, where we don't have the error sound.
I don't keep a log, and I'm not sure there was one, but I'm almost sure it would have been a result of NVDA been unable to write it's log - I can't thing of another place, which could have such effect (not that there could not be one).
I can't look at NVDA code right now, but if it doesn't guard against this, I suggest adding such a check.
I forgot about this, but I was reminded by a recent discussion on another issue.
A while ago it happened to me to have a 100% full Windows system drive.
That resulted in constant NVDA errors. I used a snapshot back then, so NVDA became unusable. I'm not sure if that would be the case with a stable version, where we don't have the error sound.
I don't keep a log, and I'm not sure there was one, but I'm almost sure it would have been a result of NVDA been unable to write it's log - I can't thing of another place, which could have such effect (not that there could not be one).
I can't look at NVDA code right now, but if it doesn't guard against this, I suggest adding such a check.