I've tested this by locking up a core using the IDE by putting it in a loop.
But no other process gets locked up, because my OS correctly does not
assign the busy core to any other process. So all other applications and
windows are still responsive.
EXCEPT in a situation when the Livecode IDE is
I’m on a quad-core Intel Xeon E5 (Mac Pro) and LC 8 could definitely lock up
the machine. Only with difficulty could I eventually force LC to quit.
Peter Bogdanoff
> On Dec 26, 2019, at 3:31 PM, Bob Sneidar via use-livecode
> wrote:
>
> I ahould have saif multiple cores not both.
>
>> On D
I ahould have saif multiple cores not both.
> On Dec 26, 2019, at 14:14 , Bob Sneidar via use-livecode
> wrote:
>
> On the machine, or on the core? LC should only be using a single core on
> Multi-core systems. Any other process using that core may be affected, but
> not necessarily processe
On the machine, or on the core? LC should only be using a single core on
Multi-core systems. Any other process using that core may be affected, but not
necessarily processes using the other core. It may be academic though, as most
apps today are probably using both cores simultaneously.
Bob S
It may be the issue with repeat loops that do not yield to the engine
periodically. This was an issue all the way back to MetaCard and I am
not sure if it has been changed since then.
Basicaly, running a lengthy repeat loop locks up the entire CPU until
the loop exits. If this is the problem t
