Open ReneSci opened 4 years ago
In theory wxMaxima should try delete the .png files as soon as it has loaded them into the worksheet - and should delete the .gnuplot and .data files as soon as the cell that displays this image is destroyed. The only way I know to make the images persist is a virus scanner that prevents deletion of the files because it still scans them (in which case I told wxMaxima to silently ignore this problem). Will have a look if the reality differs from theory on my computer, too.
Wow... ...in german one would say: "Da hast Du in ein Wespennest gestochen". Which means: This time you have found many important bugs.
:-)
Seems you found a bug in a 3rd party library, too => I advise you not to try today's Nightly Build but to wait for tomorrow one's again that contains the fix I've just pushed...
ok
Den fre. 28. feb. 2020 kl. 09.58 skrev Gunter Königsman < notifications@github.com>:
Seems you found a bug in a 3rd party library, too => I advise you not to try today's Nightly Build but to wait for tomorrow one's again that contains the fix I've just pushed...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wxMaxima-developers/wxmaxima/issues/1211?email_source=notifications&email_token=AAUEG6K7MXNKH4NAHXFDHATRFDGZ5A5CNFSM4KZCMDS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENHY3PA#issuecomment-592416188, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUEG6MSDRHO42B7L5X66I3RFDGZ5ANCNFSM4KZCMDSQ .
While running two wxMaxima/Maxima, this one came up:
Update: The above message also appears after having shutting down the other (first) wxMaxima session.
Update - it keeps comming up even after restarting wxMaxima
(%i1) build_info(); (%o1) build_info(version="branch_5_43_base_379_g7c2e2d932",timestamp="2020-03-01 00:04:38",host="x86_64-w64-mingw32",lisp_name= "SBCL",lisp_version="2.0.0",maxima_userdir="C:/Users/xxxxx/maxima",maxima_tempdir="C:/Users/xxxxx/AppData/Local/Temp",maxima_objdir= "C:/Users/xxxxx/maxima/binary/branch_5_43_base_379_g7c2e2d932/sbcl/2_0_0",maxima_frontend="wxMaxima",maxima_frontend_version= "20.02.4_MSW_OpenMP201511+Locks")
And later on when trying to save the whorksheet:
That looks like another instance of #1219 No idea why moving and deleting files on Windows always causes problems - and why these never come with a meaningful error message, though.
Ok... ...with a bit of luck tomorrow's nightly build finally resolves this issue.
This is an ongoing problem and wxMaxima has real trouble deleting temporary files. I consider it a blocker. This has nothing to do with virus checkers, at least not with the one built into Windows 10. It's some other issue, and it really needs to be fixed, but that requires working on a Windows machine.
This is way too much winapi for me to stomach right now. Not too fun. I'm removing the milestone, it's up in the air for now.
Just for interest: Which kind of data files are left on closing wxMaxima on windows? The .png files from gnuplot? Or the .gnuplot files?
It looks like sometimes all of them and sometimes few. But it’s not related to the normal Windows-bundled antivirus because all other applications do the same thing and they have no such problems. So it’s either something wxWidgets related or there are some processes (again - not antivirus) that keep these handles open.
13 juli 2020 kl. 2:44 fm skrev Gunter Königsman notifications@github.com:
Just for interest: Which kind of data files are left on closing wxMaxima on windows? The .png files from gnuplot? Or the .gnuplot files?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.
If the normal windows-bundled antivirus causes this problem I cannot tell. But I already had to debug problems Excel, PowerPoint, Word and Visio have with antivirus programs that are both triggered on both writing and on reading files as that (depending on the timing) can hinder them from moving or overwriting temp files. Also many compilers show sporadic problems if temp cannot be moved, overwritten or deleted directly after having been closed. Typical symptom in this case: You change the code, even get new compiler warnings that match the change, - but the resulting binary is byte-to-byte identical to the last compiler run, except of the build number.
Since wxMaxima ran into the same problem frequently the .wxmx writer makes (and on the computer I sometimes can borrow) often actually needs several attempts before it can overwrite the .wxmx file. Name this system completely broken, if you want to.
So much for why I am biassed in this point. On the other hand there are two places that might need looking at (additionally to you often having access to magic that finds errors where I don't expect them to reside:
wxMaxima/Maxima places a huge amount of files in: C:\Users\USERNAME\AppData\Local\Temp