You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Yishay Weiss <yi...@hotmail.com> on 2019/02/21 14:29:15 UTC
VSCode Build Taking Really Long
Hi Guys,
We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
Any help appreciated.
Re: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
While investigating this issue I accidentally filed a bin folder (which
contains a build) within the source path.
This throws an error like "...not found on source path, using parent
file..." and delayed the build process for a significant couple of seconds.
After removing this accidentally created bin folder, the build time was back
to normal.
I would just like to mention this, maybe it is helpful for others.
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: VSCode Build Taking Really Long
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I found that hard to read, but I think I see on line 657 that js-output is set to "." and that makes me wonder if the compiler will then choose whatever the working directory is at the time it is launched. If that working directory is changed by VSCode to be the last output directory (maybe to launch the results in a browser), that might cause the compiler to nest the next output in that output directory and cause the observed results.
HTH,
-Alex
On 2/27/19, 12:04 AM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
Hi Alex,
>Right. The goal was to see what output options were actually being received
by the compiler in order to understand how those options could be causing
the compiler to generate nested output folders. I'm curious to know if the
js options are in the dump file. Can't tell since you cut them out.
Sorry, I misunderstood this.
But I am still not sure what do you mean with "js options".
I've created a gist which contains the entire dump [1].
Maybe you can find some time to look at it?
Thanks!
Olaf
[1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Folafkrueger%2F8e045b33cae493deb56b38f9430afa14&data=02%7C01%7Caharui%40adobe.com%7C114a62222a504a5999b408d69c8a271a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636868514618842104&sdata=c8MjMvPC747ooXKaXZ9Pp0%2BhZZBtZwOUnbeT6HeP1n0%3D&reserved=0
--
Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C114a62222a504a5999b408d69c8a271a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636868514618842104&sdata=D0xylr0g6bUUVGpbUYFnwL%2BNe0I4oAM57FpmlowEuS0%3D&reserved=0
Re: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
Hi Alex,
>Right. The goal was to see what output options were actually being received
by the compiler in order to understand how those options could be causing
the compiler to generate nested output folders. I'm curious to know if the
js options are in the dump file. Can't tell since you cut them out.
Sorry, I misunderstood this.
But I am still not sure what do you mean with "js options".
I've created a gist which contains the entire dump [1].
Maybe you can find some time to look at it?
Thanks!
Olaf
[1] https://gist.github.com/olafkrueger/8e045b33cae493deb56b38f9430afa14
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: VSCode Build Taking Really Long
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Right. The goal was to see what output options were actually being received by the compiler in order to understand how those options could be causing the compiler to generate nested output folders. I'm curious to know if the js options are in the dump file. Can't tell since you cut them out.
-Alex
On 2/26/19, 1:27 AM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
> See if the -dump-config=<path to a file that will contain the dump> works
for JS. Not sure if it does, but it might help.
Creating a dump file works, but it seems to me that it rather contains a
config than errors which occur during the build [1].
[1]
<royale-config>
<compiler>
<accessible>true</accessible>
<allow-source-path-overlap>false</allow-source-path-overlap>
<allow-subclass-overrides>true</allow-subclass-overrides>
<as3>true</as3>
...
...
...
</royale-config>
--
Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cd663286bc8674d64a8a708d69bcc9076%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636867700241421148&sdata=5ndAmUl48UbGlUxf8XjATSeD102Z6hqBwKoPNezHi6c%3D&reserved=0
Re: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
> See if the -dump-config=<path to a file that will contain the dump> works
for JS. Not sure if it does, but it might help.
Creating a dump file works, but it seems to me that it rather contains a
config than errors which occur during the build [1].
[1]
<royale-config>
<compiler>
<accessible>true</accessible>
<allow-source-path-overlap>false</allow-source-path-overlap>
<allow-subclass-overrides>true</allow-subclass-overrides>
<as3>true</as3>
...
...
...
</royale-config>
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: VSCode Build Taking Really Long
Posted by Alex Harui <ah...@adobe.com.INVALID>.
See if the -dump-config=<path to a file that will contain the dump> works for JS. Not sure if it does, but it might help.
HTH,
-Alex
On 2/25/19, 1:28 AM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
> What happen if you put in js-output - real path instead "." - one dot ?
Same behavior!
Does that mean that you can't reproduce this issue at your side?
Olaf
--
Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C4c1ba8674d6f4de6fe9808d69b0393c9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636866837023602359&sdata=pjWV8chaPOczELCorn6rg32IO4zQCvWu2TfwYjELRgY%3D&reserved=0
Re: VSCode Build Taking Really Long
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Olaf,
Exactly. I have in Moonshine exact path:
-js-output=D:\Work\projects\client\myapp
And it doesn't occur.
Thanks,
Piotr
pon., 25 lut 2019 o 10:28 Olaf Krueger <ma...@olafkrueger.net> napisał(a):
> > What happen if you put in js-output - real path instead "." - one dot ?
>
> Same behavior!
>
> Does that mean that you can't reproduce this issue at your side?
>
> Olaf
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
> What happen if you put in js-output - real path instead "." - one dot ?
Same behavior!
Does that mean that you can't reproduce this issue at your side?
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: VSCode Build Taking Really Long
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Guys,
What happen if you put in js-output - real path instead "." - one dot ?
Thanks,
Piotr
pon., 25 lut 2019 o 09:57 Olaf Krueger <ma...@olafkrueger.net> napisał(a):
> Good catch Yishay, I found a similar issue at my side [1].
> But it seems to me that in my case just "bin/js-debug/bin/js-debug/..." is
> affected and created recursively.
>
> Olaf
>
> [1]
> https://snag.gy/q8y4G2.jpg
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
Good catch Yishay, I found a similar issue at my side [1].
But it seems to me that in my case just "bin/js-debug/bin/js-debug/..." is
affected and created recursively.
Olaf
[1]
https://snag.gy/q8y4G2.jpg
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
But it still created nested folders n deep.
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Monday, February 25, 2019 10:40:54 AM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
It looks that way. I manually removed all bin folders from the old repo clone and it’s now much faster.
________________________________
From: Olaf Krueger <ma...@olafkrueger.net>
Sent: Monday, February 25, 2019 10:28:03 AM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
That means that cleaning the build folder would have been enough in your
case, instead of re-cloning the repo, right?
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
It looks that way. I manually removed all bin folders from the old repo clone and it’s now much faster.
________________________________
From: Olaf Krueger <ma...@olafkrueger.net>
Sent: Monday, February 25, 2019 10:28:03 AM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
That means that cleaning the build folder would have been enough in your
case, instead of re-cloning the repo, right?
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
RE: VSCode Build Taking Really Long
Posted by Olaf Krueger <ma...@olafkrueger.net>.
That means that cleaning the build folder would have been enough in your
case, instead of re-cloning the repo, right?
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
I think what’s causing the problem is js-output folder is recursively created deeper and deeper [1]. Any idea why? This is our asconfig.json
{
"config": "royale",
"compilerOptions": {
"debug": true,
"targets": ["JSRoyale"],
"source-map": true,
"html-template": "src/resources/forms-index-template.html",
"theme": "${royalelib}/themes/JewelTheme/src/main/resources/defaults.css",
"output": ".",
"source-path": [
"src",
"../../libs/vendor/puremvc-as3-multicore-framework/src"
]
},
"copySourcePathAssets": true,
"additionalOptions": "-js-dynamic-access-unknown-members=true",
"files":
[
"src/com/edscha/ebaseforms/shell/view/royale/Shell.mxml"
]
[1] https://paste.apache.org/sdgg
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Sunday, February 24, 2019 9:00:15 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
Re-cloning the repository reduces it to 30 seconds, then 14.
I guess some cached files were messing things up but I’m not sure when I’m going to have time to investigate this.
Anyway, thanks to everyone who chipped in.
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Saturday, February 23, 2019 11:18:57 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
Is there a verbose mode for running asconfigc?
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Saturday, February 23, 2019 10:56:16 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
CPU rarely goes over 20% and never over 57%. Turning real-time protection off didn’t make a big difference.
________________________________
From: Josh Tynjala <jo...@apache.org>
Sent: Friday, February 22, 2019 7:40:45 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
The fact that you're all on Windows and are using the same versions of all of the development tools makes me think that it might be something else in your environment. Like maybe a malware scanner or something else that might be watching the file system?
It might be worth opening up the task manager and watching if anything else on your system starts using a lot of CPU while you are compiling. The process might not start immediately when the compiler starts, but maybe later as the compiler starts writing files (and then re-writing many of them for the remove-circulars phase).
- Josh
On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
>
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
Re-cloning the repository reduces it to 30 seconds, then 14.
I guess some cached files were messing things up but I’m not sure when I’m going to have time to investigate this.
Anyway, thanks to everyone who chipped in.
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Saturday, February 23, 2019 11:18:57 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
Is there a verbose mode for running asconfigc?
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Saturday, February 23, 2019 10:56:16 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
CPU rarely goes over 20% and never over 57%. Turning real-time protection off didn’t make a big difference.
________________________________
From: Josh Tynjala <jo...@apache.org>
Sent: Friday, February 22, 2019 7:40:45 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
The fact that you're all on Windows and are using the same versions of all of the development tools makes me think that it might be something else in your environment. Like maybe a malware scanner or something else that might be watching the file system?
It might be worth opening up the task manager and watching if anything else on your system starts using a lot of CPU while you are compiling. The process might not start immediately when the compiler starts, but maybe later as the compiler starts writing files (and then re-writing many of them for the remove-circulars phase).
- Josh
On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
>
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
Is there a verbose mode for running asconfigc?
________________________________
From: Yishay Weiss <yi...@hotmail.com>
Sent: Saturday, February 23, 2019 10:56:16 PM
To: dev@royale.apache.org
Subject: RE: VSCode Build Taking Really Long
CPU rarely goes over 20% and never over 57%. Turning real-time protection off didn’t make a big difference.
________________________________
From: Josh Tynjala <jo...@apache.org>
Sent: Friday, February 22, 2019 7:40:45 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
The fact that you're all on Windows and are using the same versions of all of the development tools makes me think that it might be something else in your environment. Like maybe a malware scanner or something else that might be watching the file system?
It might be worth opening up the task manager and watching if anything else on your system starts using a lot of CPU while you are compiling. The process might not start immediately when the compiler starts, but maybe later as the compiler starts writing files (and then re-writing many of them for the remove-circulars phase).
- Josh
On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
>
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
CPU rarely goes over 20% and never over 57%. Turning real-time protection off didn’t make a big difference.
________________________________
From: Josh Tynjala <jo...@apache.org>
Sent: Friday, February 22, 2019 7:40:45 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
The fact that you're all on Windows and are using the same versions of all of the development tools makes me think that it might be something else in your environment. Like maybe a malware scanner or something else that might be watching the file system?
It might be worth opening up the task manager and watching if anything else on your system starts using a lot of CPU while you are compiling. The process might not start immediately when the compiler starts, but maybe later as the compiler starts writing files (and then re-writing many of them for the remove-circulars phase).
- Josh
On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
>
Re: VSCode Build Taking Really Long
Posted by Josh Tynjala <jo...@apache.org>.
Hey Piotr,
I'm moving this VSCode discussion about the ConcurrentModificationException here:
https://github.com/BowlerHatLLC/vscode-as3mxml/issues/332
- Josh
On 2019/02/23 09:39:27, Piotr Zarzycki <pi...@gmail.com> wrote:
> Hi Josh,
>
> This is what I'm getting having Win Antivirus ON [1]. Once it's occurs
> usage of extension is pointless. Everything is freezing, any rollover on
> component or as3 mxml is causing output in console. - Maybe it's related to
> the slowness in case of Yishay.
>
> Yishay did you try switch OFF real time protection [2] ?
>
> [1] https://paste.apache.org/nBnH
> [2] https://imgur.com/a/qgewGHT
>
> Thanks,
> Piotr
>
> pt., 22 lut 2019 o 23:19 Josh Tynjala <jo...@apache.org> napisał(a):
>
> > Piotr,
> >
> > What happens when it crashes? Are there specific errors or stack traces
> > that I could possibly investigate?
> >
> > - Josh
> >
> > On 2019/02/22 18:01:05, Piotr Zarzycki <pi...@gmail.com> wrote:
> > > Josh,
> > >
> > > In that case I need to say that internal Antivirus in Windows is making
> > my
> > > life harder in case Moonshine usage for a long time.
> > > Maybe problems which Yishay experiencing is connecting to that.
> > >
> > > Basically when antivirus/firewall is On Windows I'm getting constant
> > > crashes of extension after sometimes couple of minutes of work or half an
> > > hour. Once crashes are starting to happen I'm basically cannot work
> > farther
> > > - I need to restart Moonshine.
> > >
> > > I have to check whether being in that state I have problems with build as
> > > well. For quite some time when I'm starting work with your extension
> > > regardless it's Moonshine or VSCode first thing is switching OFF
> > > firewall/antivirus live scanning, so I could work without the problems.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > >
> > > On Fri, Feb 22, 2019, 6:40 PM Josh Tynjala <jo...@apache.org>
> > wrote:
> > >
> > > > The fact that you're all on Windows and are using the same versions of
> > all
> > > > of the development tools makes me think that it might be something
> > else in
> > > > your environment. Like maybe a malware scanner or something else that
> > might
> > > > be watching the file system?
> > > >
> > > > It might be worth opening up the task manager and watching if anything
> > > > else on your system starts using a lot of CPU while you are compiling.
> > The
> > > > process might not start immediately when the compiler starts, but maybe
> > > > later as the compiler starts writing files (and then re-writing many of
> > > > them for the remove-circulars phase).
> > > >
> > > > - Josh
> > > >
> > > > On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> > > > > Hi Guys,
> > > > >
> > > > > We have a really simple app which takes Piotr and Olaf less than
> > half a
> > > > minute to compile using VSCode. The same app takes me somewhere
> > between 2.5
> > > > and 5 minutes.
> > > > >
> > > > > Can you round up the usual suspects? My computer isn’t slower than
> > > > theirs and until recently we’ve been using the same java version.
> > We’re all
> > > > using windows.
> > > > >
> > > > > Any help appreciated.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
Re: VSCode Build Taking Really Long
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Josh,
This is what I'm getting having Win Antivirus ON [1]. Once it's occurs
usage of extension is pointless. Everything is freezing, any rollover on
component or as3 mxml is causing output in console. - Maybe it's related to
the slowness in case of Yishay.
Yishay did you try switch OFF real time protection [2] ?
[1] https://paste.apache.org/nBnH
[2] https://imgur.com/a/qgewGHT
Thanks,
Piotr
pt., 22 lut 2019 o 23:19 Josh Tynjala <jo...@apache.org> napisał(a):
> Piotr,
>
> What happens when it crashes? Are there specific errors or stack traces
> that I could possibly investigate?
>
> - Josh
>
> On 2019/02/22 18:01:05, Piotr Zarzycki <pi...@gmail.com> wrote:
> > Josh,
> >
> > In that case I need to say that internal Antivirus in Windows is making
> my
> > life harder in case Moonshine usage for a long time.
> > Maybe problems which Yishay experiencing is connecting to that.
> >
> > Basically when antivirus/firewall is On Windows I'm getting constant
> > crashes of extension after sometimes couple of minutes of work or half an
> > hour. Once crashes are starting to happen I'm basically cannot work
> farther
> > - I need to restart Moonshine.
> >
> > I have to check whether being in that state I have problems with build as
> > well. For quite some time when I'm starting work with your extension
> > regardless it's Moonshine or VSCode first thing is switching OFF
> > firewall/antivirus live scanning, so I could work without the problems.
> >
> > Thanks,
> > Piotr
> >
> >
> >
> > On Fri, Feb 22, 2019, 6:40 PM Josh Tynjala <jo...@apache.org>
> wrote:
> >
> > > The fact that you're all on Windows and are using the same versions of
> all
> > > of the development tools makes me think that it might be something
> else in
> > > your environment. Like maybe a malware scanner or something else that
> might
> > > be watching the file system?
> > >
> > > It might be worth opening up the task manager and watching if anything
> > > else on your system starts using a lot of CPU while you are compiling.
> The
> > > process might not start immediately when the compiler starts, but maybe
> > > later as the compiler starts writing files (and then re-writing many of
> > > them for the remove-circulars phase).
> > >
> > > - Josh
> > >
> > > On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> > > > Hi Guys,
> > > >
> > > > We have a really simple app which takes Piotr and Olaf less than
> half a
> > > minute to compile using VSCode. The same app takes me somewhere
> between 2.5
> > > and 5 minutes.
> > > >
> > > > Can you round up the usual suspects? My computer isn’t slower than
> > > theirs and until recently we’ve been using the same java version.
> We’re all
> > > using windows.
> > > >
> > > > Any help appreciated.
> > > >
> > > >
> > > >
> > >
> >
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: VSCode Build Taking Really Long
Posted by Josh Tynjala <jo...@apache.org>.
Piotr,
What happens when it crashes? Are there specific errors or stack traces that I could possibly investigate?
- Josh
On 2019/02/22 18:01:05, Piotr Zarzycki <pi...@gmail.com> wrote:
> Josh,
>
> In that case I need to say that internal Antivirus in Windows is making my
> life harder in case Moonshine usage for a long time.
> Maybe problems which Yishay experiencing is connecting to that.
>
> Basically when antivirus/firewall is On Windows I'm getting constant
> crashes of extension after sometimes couple of minutes of work or half an
> hour. Once crashes are starting to happen I'm basically cannot work farther
> - I need to restart Moonshine.
>
> I have to check whether being in that state I have problems with build as
> well. For quite some time when I'm starting work with your extension
> regardless it's Moonshine or VSCode first thing is switching OFF
> firewall/antivirus live scanning, so I could work without the problems.
>
> Thanks,
> Piotr
>
>
>
> On Fri, Feb 22, 2019, 6:40 PM Josh Tynjala <jo...@apache.org> wrote:
>
> > The fact that you're all on Windows and are using the same versions of all
> > of the development tools makes me think that it might be something else in
> > your environment. Like maybe a malware scanner or something else that might
> > be watching the file system?
> >
> > It might be worth opening up the task manager and watching if anything
> > else on your system starts using a lot of CPU while you are compiling. The
> > process might not start immediately when the compiler starts, but maybe
> > later as the compiler starts writing files (and then re-writing many of
> > them for the remove-circulars phase).
> >
> > - Josh
> >
> > On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> > > Hi Guys,
> > >
> > > We have a really simple app which takes Piotr and Olaf less than half a
> > minute to compile using VSCode. The same app takes me somewhere between 2.5
> > and 5 minutes.
> > >
> > > Can you round up the usual suspects? My computer isn’t slower than
> > theirs and until recently we’ve been using the same java version. We’re all
> > using windows.
> > >
> > > Any help appreciated.
> > >
> > >
> > >
> >
>
Re: VSCode Build Taking Really Long
Posted by Piotr Zarzycki <pi...@gmail.com>.
Josh,
In that case I need to say that internal Antivirus in Windows is making my
life harder in case Moonshine usage for a long time.
Maybe problems which Yishay experiencing is connecting to that.
Basically when antivirus/firewall is On Windows I'm getting constant
crashes of extension after sometimes couple of minutes of work or half an
hour. Once crashes are starting to happen I'm basically cannot work farther
- I need to restart Moonshine.
I have to check whether being in that state I have problems with build as
well. For quite some time when I'm starting work with your extension
regardless it's Moonshine or VSCode first thing is switching OFF
firewall/antivirus live scanning, so I could work without the problems.
Thanks,
Piotr
On Fri, Feb 22, 2019, 6:40 PM Josh Tynjala <jo...@apache.org> wrote:
> The fact that you're all on Windows and are using the same versions of all
> of the development tools makes me think that it might be something else in
> your environment. Like maybe a malware scanner or something else that might
> be watching the file system?
>
> It might be worth opening up the task manager and watching if anything
> else on your system starts using a lot of CPU while you are compiling. The
> process might not start immediately when the compiler starts, but maybe
> later as the compiler starts writing files (and then re-writing many of
> them for the remove-circulars phase).
>
> - Josh
>
> On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> > Hi Guys,
> >
> > We have a really simple app which takes Piotr and Olaf less than half a
> minute to compile using VSCode. The same app takes me somewhere between 2.5
> and 5 minutes.
> >
> > Can you round up the usual suspects? My computer isn’t slower than
> theirs and until recently we’ve been using the same java version. We’re all
> using windows.
> >
> > Any help appreciated.
> >
> >
> >
>
Re: VSCode Build Taking Really Long
Posted by Josh Tynjala <jo...@apache.org>.
The fact that you're all on Windows and are using the same versions of all of the development tools makes me think that it might be something else in your environment. Like maybe a malware scanner or something else that might be watching the file system?
It might be worth opening up the task manager and watching if anything else on your system starts using a lot of CPU while you are compiling. The process might not start immediately when the compiler starts, but maybe later as the compiler starts writing files (and then re-writing many of them for the remove-circulars phase).
- Josh
On 2019/02/21 14:29:15, Yishay Weiss <yi...@hotmail.com> wrote:
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
>
Re: VSCode Build Taking Really Long
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Yishay,
Try exercise with running build trough Windows CMD to see what's the timing.
Thanks,
Piotr
pt., 22 lut 2019 o 09:03 Yishay Weiss <yi...@hotmail.com> napisał(a):
> I installed asconfigc separately and ran it from the command line with
> VSCode closed, but still no joy. Attaching console output [1]
>
>
>
> [1] https://paste.apache.org/wXhr
>
>
>
> ________________________________
> From: Harbs <ha...@gmail.com>
> Sent: Thursday, February 21, 2019 5:44:22 PM
> To: dev@royale.apache.org
> Subject: Re: VSCode Build Taking Really Long
>
> What are you using to compile?
>
> If you’re compiling using the VS Code extension, try installing asconfigc
> separately.
>
> > On Feb 21, 2019, at 4:29 PM, Yishay Weiss <yi...@hotmail.com>
> wrote:
> >
> > Hi Guys,
> >
> > We have a really simple app which takes Piotr and Olaf less than half a
> minute to compile using VSCode. The same app takes me somewhere between 2.5
> and 5 minutes.
> >
> > Can you round up the usual suspects? My computer isn’t slower than
> theirs and until recently we’ve been using the same java version. We’re all
> using windows.
> >
> > Any help appreciated.
> >
> >
>
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
RE: VSCode Build Taking Really Long
Posted by Yishay Weiss <yi...@hotmail.com>.
I installed asconfigc separately and ran it from the command line with VSCode closed, but still no joy. Attaching console output [1]
[1] https://paste.apache.org/wXhr
________________________________
From: Harbs <ha...@gmail.com>
Sent: Thursday, February 21, 2019 5:44:22 PM
To: dev@royale.apache.org
Subject: Re: VSCode Build Taking Really Long
What are you using to compile?
If you’re compiling using the VS Code extension, try installing asconfigc separately.
> On Feb 21, 2019, at 4:29 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>
Re: VSCode Build Taking Really Long
Posted by Harbs <ha...@gmail.com>.
What are you using to compile?
If you’re compiling using the VS Code extension, try installing asconfigc separately.
> On Feb 21, 2019, at 4:29 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Hi Guys,
>
> We have a really simple app which takes Piotr and Olaf less than half a minute to compile using VSCode. The same app takes me somewhere between 2.5 and 5 minutes.
>
> Can you round up the usual suspects? My computer isn’t slower than theirs and until recently we’ve been using the same java version. We’re all using windows.
>
> Any help appreciated.
>
>