[Octave-bug-tracker] [bug #64193] Octave 8.2.0: massive problems with file change notifications under WIN10

[Siegbert Steinlechner]

Follow-up Comment #12, bug #64193 (project octave):

[comment #9 comment#9:]
>Do you use any antivirus or other "security" software? If yes, which? Does it
make a difference if you (temporarily?) disable that software?

No, only the WIN10 built-in antivirus software.

The time between file save and run-command definitely matters on my system. I
guess, after the run-command, Octave checks whether the file in memory has
been changed on harddisk. But the true status of the file is available only
after ~3 seconds. If I run the file within 1 second after saving it, the old
content in memory is used.

[comment #11 comment #11:]
>> canonicalize_file_name('D:/Userdaten/Octave/Euler/Euler800_899/Euler833')
ans = D:\Userdaten\Octave\Euler\Euler800_899\Euler833

>>
canonicalize_file_name('D:/Userdaten/Octave/Euler/Euler800_899/Euler833/Test.m')
ans = D:\Userdaten\Octave\Euler\Euler800_899\Euler833\Test.m

[comment #8 comment #8:]
> Now I made a strange observation: when the WIN10 file explorer is opened,
showing the parent folder of the m-File, I can't reproduce the error. If I
close the file explorer, the error happens again if there is less than ~1
second between file save and running the file.

I guess, when the file explorer is running, the update rate of the file status
increases. Any comments to this behavior?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64193>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/