Re: A Windows 10 WTF
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 affects me I guess. :) Thanks everyone for trying. On Fri, Dec 27, 2019 at 11:17 AM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > 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 < > use-livecode@lists.runrev.com> wrote: > >> > >> I ahould have saif multiple cores not both. > >> > >>> On Dec 26, 2019, at 14:14 , Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> 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 processes using the other core. It may be academic > though, as most apps today are probably using both cores simultaneously. > >>> > >>> Bob S > >>> > >>> > On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > > 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 then it isn't just your standalone > that comes to a halt, it's everything currently running on the machine. > >>> > >>> > >>> ___ > >>> 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 > >> > >> > >> ___ > >> 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 > > > > > > ___ > > 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 > > ___ > 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 > -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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
Re: A Windows 10 WTF
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 via use-livecode > wrote: > > 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 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 processes using the other core. It may be academic though, >>> as most apps today are probably using both cores simultaneously. >>> >>> Bob S >>> >>> On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode wrote: 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 then it isn't just your standalone that comes to a halt, it's everything currently running on the machine. >>> >>> >>> ___ >>> 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 >> >> >> ___ >> 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 > > > ___ > 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 ___ 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
RE: A Windows 10 WTF
Is there a common resource that both processes are using? Maybe there on 2 different cores but a file locking, database or some similar issue is causing the standalone to lock up. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: 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. 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 running a particular stack AND there is a Standalone version of that stack running at the same time. (these 2 are seperate processes BUT..) In that case the system is assigning both the standalone and the IDE (and its running stack) to the same core.and both of them become unresponsive. My question is why there is a correlation between the two, and why the standalone isn't being assigned one of the other 3 available coresbut always the same core as the IDE. If its a different stack open in the IDE... the standalone is correctly assigned to another core. I don't know how else to explain the problem. Forgive me if I am not clearly explaining it. On Thu, Dec 26, 2019 at 7:15 PM Peter Bogdanoff via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 < > use-livecode@lists.runrev.com> wrote: > > > > I ahould have saif multiple cores not both. > > > >> On Dec 26, 2019, at 14:14 , Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> 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 processes using the other core. It may > be academic though, as most apps today are probably using both cores > simultaneously. > >> > >> Bob S > >> > >> > >>> On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > >>> > >>> 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 then it isn't just your > standalone that comes to a halt, it's everything currently running on the > machine. > >> > >> > >> ___ > >> 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 > > > > > > ___ > > 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 > > > ___ > 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 > -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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 ___ 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
Re: A Windows 10 WTF
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 running a particular stack AND there is a Standalone version of that stack running at the same time. (these 2 are seperate processes BUT..) In that case the system is assigning both the standalone and the IDE (and its running stack) to the same core.and both of them become unresponsive. My question is why there is a correlation between the two, and why the standalone isn't being assigned one of the other 3 available coresbut always the same core as the IDE. If its a different stack open in the IDE... the standalone is correctly assigned to another core. I don't know how else to explain the problem. Forgive me if I am not clearly explaining it. On Thu, Dec 26, 2019 at 7:15 PM Peter Bogdanoff via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 < > use-livecode@lists.runrev.com> wrote: > > > > I ahould have saif multiple cores not both. > > > >> On Dec 26, 2019, at 14:14 , Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> 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 processes using the other core. It may be academic > though, as most apps today are probably using both cores simultaneously. > >> > >> Bob S > >> > >> > >>> On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > >>> > >>> 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 then it isn't just your standalone > that comes to a halt, it's everything currently running on the machine. > >> > >> > >> ___ > >> 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 > > > > > > ___ > > 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 > > > ___ > 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 > -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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
Re: A Windows 10 WTF
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 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 processes using the other core. It may be academic though, >> as most apps today are probably using both cores simultaneously. >> >> Bob S >> >> >>> On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode >>> wrote: >>> >>> 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 then it isn't just your standalone that >>> comes to a halt, it's everything currently running on the machine. >> >> >> ___ >> 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 > > > ___ > 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 ___ 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
Re: A Windows 10 WTF
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 processes using the other core. It may be academic though, as > most apps today are probably using both cores simultaneously. > > Bob S > > >> On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode >> wrote: >> >> 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 then it isn't just your standalone that >> comes to a halt, it's everything currently running on the machine. > > > ___ > 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 ___ 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
Re: A Windows 10 WTF
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 > On Dec 26, 2019, at 11:16 , J. Landman Gay via use-livecode > wrote: > > 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 then it isn't just your standalone that > comes to a halt, it's everything currently running on the machine. ___ 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
Re: A Windows 10 WTF
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 then it isn't just your standalone that comes to a halt, it's everything currently running on the machine. The first couple of paragraphs here describe the problem: <http://www.hyperactivesw.com/resources_polling.html> On 12/24/19 1:04 PM, Tom Glod via use-livecode wrote: 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 tandem...when the OS should be designating cores more intelligently than that. *shrug* On Tue, Dec 24, 2019 at 5:51 AM Peter Reid via use-livecode < use-livecode@lists.runrev.com> wrote: 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 'with messages' is the key element, this made the LC app hand back control to Windows to handle other system activities. I add this line to all my loops when running under Windows. Give this a try and let me know whether this helps. Peter -- Peter Reid Loughborough, UK On 23 Dec 2019, at 5:00pm, use-livecode-requ...@lists.runrev.com wrote: Date: Mon, 23 Dec 2019 10:42:31 -0500 From: Tom Glod mailto:t...@makeshyft.com>> To: How to use LiveCode use-livecode@lists.runrev.com>> Subject: a windows 10 wtf Message-ID: < capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com <mailto:capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com Content-Type: text/plain; charset="UTF-8" Hi Peeeps, So I have a standalone running 24/7 that was built with LiveCode. When I use Livecode the IDE to work on the application (that I am also running as a standalone), and the IDE locks up for whatever reason...being busy or whatever. my standalone application also locks up (window become unresponsive). As soon as the IDE is responsive again, so is my standalone window. I have a 4 core machine...and nothing else seems to be locking up just the IDE and the standalone. Why is the OS insisting on the 2 processes sharing a core? Has anyone come across this before? Happy Holidays and Merry Christmas to all those who celebrate it. -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com <http://www.makeshyft.com/>) Office:226-706-9339 Mobile:226-706-9793 ___ 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 -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.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
Re: A Windows 10 WTF
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 tandem...when the OS should be designating cores more intelligently than that. *shrug* On Tue, Dec 24, 2019 at 5:51 AM Peter Reid via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 'with messages' is the key element, this made the LC app hand back > control to Windows to handle other system activities. I add this line to > all my loops when running under Windows. Give this a try and let me know > whether this helps. > > Peter > -- > Peter Reid > Loughborough, UK > > > On 23 Dec 2019, at 5:00pm, use-livecode-requ...@lists.runrev.com wrote: > > > > Date: Mon, 23 Dec 2019 10:42:31 -0500 > > From: Tom Glod mailto:t...@makeshyft.com>> > > To: How to use LiveCode use-livecode@lists.runrev.com>> > > Subject: a windows 10 wtf > > Message-ID: > > < > capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com > <mailto:capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com > >> > > Content-Type: text/plain; charset="UTF-8" > > > > Hi Peeeps, > > > > So I have a standalone running 24/7 that was built with LiveCode. > > > > When I use Livecode the IDE to work on the application (that I am also > > running as a standalone), and the IDE locks up for whatever > reason...being > > busy or whatever. my standalone application also locks up (window > > become unresponsive). As soon as the IDE is responsive again, so is my > > standalone window. > > > > I have a 4 core machine...and nothing else seems to be locking up > just > > the IDE and the standalone. > > > > Why is the OS insisting on the 2 processes sharing a core? > > > > Has anyone come across this before? > > > > Happy Holidays and Merry Christmas to all those who celebrate it. > > > > -- > > Tom Glod > > Founder & Developer > > MakeShyft R.D.A (www.makeshyft.com <http://www.makeshyft.com/>) > > Office:226-706-9339 > > Mobile:226-706-9793 > > ___ > 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 > -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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
Re: A Windows 10 WTF
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 'with messages' is the key element, this made the LC app hand back control to Windows to handle other system activities. I add this line to all my loops when running under Windows. Give this a try and let me know whether this helps. Peter -- Peter Reid Loughborough, UK > On 23 Dec 2019, at 5:00pm, use-livecode-requ...@lists.runrev.com wrote: > > Date: Mon, 23 Dec 2019 10:42:31 -0500 > From: Tom Glod mailto:t...@makeshyft.com>> > To: How to use LiveCode <mailto:use-livecode@lists.runrev.com>> > Subject: a windows 10 wtf > Message-ID: ><mailto:capzqjl+5oej4steqr702aw2lyx-qth25oc8phkn_smm94jf...@mail.gmail.com>> > Content-Type: text/plain; charset="UTF-8" > > Hi Peeeps, > > So I have a standalone running 24/7 that was built with LiveCode. > > When I use Livecode the IDE to work on the application (that I am also > running as a standalone), and the IDE locks up for whatever reason...being > busy or whatever. my standalone application also locks up (window > become unresponsive). As soon as the IDE is responsive again, so is my > standalone window. > > I have a 4 core machine...and nothing else seems to be locking up just > the IDE and the standalone. > > Why is the OS insisting on the 2 processes sharing a core? > > Has anyone come across this before? > > Happy Holidays and Merry Christmas to all those who celebrate it. > > -- > Tom Glod > Founder & Developer > MakeShyft R.D.A (www.makeshyft.com <http://www.makeshyft.com/>) > Office:226-706-9339 > Mobile:226-706-9793 ___ 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
Re: a windows 10 wtf
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 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 that was built with LiveCode. > > > > When I use Livecode the IDE to work on the application (that I am also > > running as a standalone), and the IDE locks up for whatever > reason...being > > busy or whatever. my standalone application also locks up (window > > become unresponsive). As soon as the IDE is responsive again, so is my > > standalone window. > > > > I have a 4 core machine...and nothing else seems to be locking up > just > > the IDE and the standalone. > > > > Why is the OS insisting on the 2 processes sharing a core? > > > > Has anyone come across this before? > > > > Happy Holidays and Merry Christmas to all those who celebrate it. > > > > -- > > Tom Glod > > Founder & Developer > > MakeShyft R.D.A (www.makeshyft.com) > > Office:226-706-9339 > > Mobile:226-706-9793 > > ___ > > 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 > > > > > ___ > 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 > -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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
Re: a windows 10 wtf
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 that was built with LiveCode. When I use Livecode the IDE to work on the application (that I am also running as a standalone), and the IDE locks up for whatever reason...being busy or whatever. my standalone application also locks up (window become unresponsive). As soon as the IDE is responsive again, so is my standalone window. I have a 4 core machine...and nothing else seems to be locking up just the IDE and the standalone. Why is the OS insisting on the 2 processes sharing a core? Has anyone come across this before? Happy Holidays and Merry Christmas to all those who celebrate it. -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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 ___ 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
a windows 10 wtf
Hi Peeeps, So I have a standalone running 24/7 that was built with LiveCode. When I use Livecode the IDE to work on the application (that I am also running as a standalone), and the IDE locks up for whatever reason...being busy or whatever. my standalone application also locks up (window become unresponsive). As soon as the IDE is responsive again, so is my standalone window. I have a 4 core machine...and nothing else seems to be locking up just the IDE and the standalone. Why is the OS insisting on the 2 processes sharing a core? Has anyone come across this before? Happy Holidays and Merry Christmas to all those who celebrate it. -- Tom Glod Founder & Developer MakeShyft R.D.A (www.makeshyft.com) Office:226-706-9339 Mobile:226-706-9793 ___ 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
