Windows: "not responding"

[Richard Gaskin]

IIRC, earlier discussions here about this do recognize that it's about a 
certain finickiness with Windows, but also acknowledged that this seems 
to happen more frequently in LC apps than others.  Personally, I see 
this very rarely in anything other than LC, and in LC apps quite often. 
Customers find it very disturbing, and have expressed a temptation to 
force-quit the app based on the (apparently erroneous) guidance provided 
to them by the OS.

In those earlier discussions there was talk of the method Windows 
expects for an app to effectively tell it, "I'm still alive, just 
working", which is apparently not being done as frequently as the OS 
needs to get the message.

This all seemed so fresh in that earlier discussion that I somehow 
(perhaps mistakenly) got the impression it was under active development. 
  But I can't find anything in the bug DB suggesting that's the case.

I don't mind opening a new issue for this, just wanted to see if doing 
so would create a duplicate of something that's already there.

-- 
  Richard Gaskin
  Fourth World Systems


Brian Milby wrote:
> I don’t think this is an issue exclusive to LC. My main Access DB has code that will do the same thing. Sometimes things come back fine because it was just busy (SharePoint issues do cause it to get totally hung sometimes as well though).
> 
> Thanks,
> Brian
> On Aug 7, 2018, 1:07 PM -0500, Paul Dupuis via use-livecode <use-livecode at lists.runrev.com>, wrote:
>> On 8/7/2018 1:58 PM, Richard Gaskin via use-livecode wrote:
>> > We've discussed many times here the anomaly in which an LC process on
>> > Windows is running quite fine, but when it's working really hard the
>> > OS starts monkeying with the window appearance, adding the string
>> > "application is not responding" in the title bar.
>> >
>> > In all cases I've see thus far, the app itself is fine, but apparently
>> > it's not yielding enough cycles to the OS for the OS to feel
>> > comfortable about the relationship.
>> >
>> > Based on early conversations here, I had thought that a solution
>> > addressing this was in progress, but checking the bug DB I can't find
>> > even a report for this at all, let alone one noting "In Progress".
>> >
>> > Anyone here know the status of this issue?  Should I file a new report
>> > on it?
>> >
>> I run into to this symptom more often than I would like to see as well.
>>