Nope..its not sharing any resources, each one runs isolated in its own
folder. Yep... you can set affinity manually using the task manager.
The only thing shared between them is the name of the stack window...I
guess I'll test that first.
This is weird and I don't like it . but it only
That's a thought. Also, there used to be a way to set the affinity of an
application to prefer or only run on one core. This was in the early days of
multi-cores where apps might not be multicore aware. Not sure if this is a
thing anymore.
Bob S
> On Dec 26, 2019, at 16:15 , Peter Bogdanoff
: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Tom Glod via use-livecode
Sent: Thursday, December 26, 2019 8:41 PM
To: How to use LiveCode
Cc: Tom Glod
Subject: Re: A Windows 10 WTF
I've tested this by locking up a core using the IDE by putting it in a loop
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
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
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
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
Hi Peter, thanks, you are right the wait command does eliminate the window
lock up but my question was more so about why the Livecode IDE (with
open file A)...seems forced to share the same cpu core with Standalone of
file A and if anyone else has come across that beforethey lock up
in
Hi Tom
I'm not sure about Windows 10 behaviour but I had a similar problem with
Windows 7. It seemed that my LC app was not releasing the processor long enough
to handle basic user I/O. The solution was to add the following to all my tight
loops:
wait 0 milliseconds with messages
The
Hi Jacqueline...nope...I don't even see that on the list of inclusions.
*scratch head*
On Mon, Dec 23, 2019 at 11:47 AM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Just a wild guess, did you include the remote debugger in the standalone?
>
> --
> Jacqueline Landman
Just a wild guess, did you include the remote debugger in the standalone?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 23, 2019 9:44:49 AM Tom Glod via use-livecode
wrote:
Hi Peeeps,
So I have a standalone running 24/7
12 matches
Mail list logo
