On 1/8/19 3:36 PM, Monte Goulding via use-livecode wrote:
On 9 Jan 2019, at 6:56 am, Richard Gaskin via use-livecode
<use-livecode@lists.runrev.com> wrote:
Even more interesting IMO is all the attempts to access
revapplicationoverview.mc
Thanks - I've added a note on that detail in my report:
https://quality.livecode.com/show_bug.cgi?id=21782
<https://quality.livecode.com/show_bug.cgi?id=21782>
This would be the engine trying lots of paths when trying to resolve
revApplicationOverview. See `MCDispatch::findstackname`. Clearly it is being
referenced somewhere and it is not in the stackFiles of home as it should be.
Whether this is the cause or not of the issues being discussed I’m not sure. It
could be that windows defender gets stressed when it sees an application
stabbing around in the dark trying to find a file.
Still begs the question as to why the engine is doing this. Now that
I've sheepishly done a non-case-sensitive search for it, I see
revApplicationOverview referenced a lot in the main backscript and I see
that findstackname will take a stack short name as an argument and then
try to find the stack file.
So is all that thrashing just the result of "is there is a stack..."? Or
possibly "if the mode of stack..."? That could seriously be impacting
the speed of lots of system messages.
--
Mark Wieder
ahsoftw...@gmail.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
