Re: windows standalone performance

> My user who initially reported the bug to me has acquired a new PC on which > the bug does not seem to happen I spoke too soon … my user's whiz-bang PC still takes 3 seconds to save my app's 9 MB data stack, when his older PC takes 10 seconds. Both should be saving in a very small fraction of

Re: windows standalone performance

> Sean wrote: From what I can tell from QC is that it has not been confirmed > and been marked as pending due to not being able to reproduce. The bug is clearly marked as status CONFIRMED. There was a stage when QC could not reproduce the bug on their machines, but Panos did confirm it “on olde

Re: windows standalone performance

From what I can tell from QC is that it has not been confirmed and been marked as pending due to not being able to reproduce. Therefore the report is in limbo until further evidence or successful, consistent reproduction can be displayed. Hence, if you make a video of your findings it makes it

Re: windows standalone performance

Hi Sean The slow saving of stacks under LC9 occurs in Windows 10, native and using Parallels Desktop. https://quality.livecode.com/show_bug.cgi?id=21305 Mac, Linux and previous versions of Windows are not affected. The bug was confirmed by Q

Re: Windows Standalone Performance

Hi Neville From my stance I have never seen this behaviour for any version of LC from any stack ide or standalone on Mac, Windows XP/7/8/10 native or via ParallelsDesktop. Perhaps you could do a few screen recordings using an external device like your phone and show the task manager reporting d

Re: Windows Standalone Performance

This bug was reported some time ago https://quality.livecode.com/show_bug.cgi?id=21305 Saving a 9 megabyte stack in Windows 10 can take 10 seconds or more. It is not caused by Windows Defender or anti-virus software. _

Re: Windows Standalone Performance

I like that. Looking on the bright side. :-) And of course you are right, saving multiple times is not a good thing, but I did this back when we had that bug where saving scripts actually didn't for whatever reason, and I had some crash to desktop issues as well, prompting me to insert an auto s

Re: Windows Standalone Performance

> No one is going to turn off their file AV LOL - yes, but that would be entirely your idea, not mine. As I said, yet another reason to code with care. Saving a stack multiple times while launching is not a good habit. Bad habits add up to hurt Mac apps too. The AV did you a favor with exa

Re: Windows Standalone Performance

Easy enough to test. I'll do that later and get back with results. It's definitely worth exploring, but I can short cut that a bit by saying that since virtually everyone with any sense has some kind of protection, even if it's Windows Defender, but also other protection on top of that, the exer

Re: Windows Standalone Performance

Bob Sneidar wrote: > Just wanted to give a heads up on what I think is the greatest Windows > Standalone performance killer. .. > On a Mac, for whatever reason, the performance hit was insignificant. > On WINDOWS however, it became painfully clear to me that the > performance penalty was VERY sub

Re: Windows Standalone Performance

Bob: > Since I do a lot of setup, I was saving the stack(s) multiple > times just launching the app! And it was killing the performance. Behold the antivirus. One more reason to code with care This time it did you a favor; these habits add up to hurt Mac apps too. Best wishes, Curry Ken