"Building workspace..." slow, sometimes unresponsive.

[Rich Henry]

I've been using ScalaIDE for awhile now, and like it a lot. But recently I've been having some issues with the automatic compilation behavior.

Specifically, when I use compiler/type heavy libraries like Scalaz and Shapeless, I find that the quick compiles the IDE tries to do (to syntax check my stuff?) get quite long, and sometimes even crash/hang. 

The result is that after i've been typing for a bit in such a file, the responsiveness of editing goes way down, causing me to look down at the status bar to see a slow/hung "Building workspace" message. Sometimes I even have to kill the IDE to recover -- it never comes back.

1) Is this normal/expected?

2) Are the some options I can turn off to alleviate this overload when using type-heavy, type-generating code like this?

Thanks,

Rich

[Simon Schäfer]

On 17.02.2015 14:59, Rich Henry wrote:

I've been using ScalaIDE for awhile now, and like it a lot. But recently I've been having some issues with the automatic compilation behavior.

Specifically, when I use compiler/type heavy libraries like Scalaz and Shapeless, I find that the quick compiles the IDE tries to do (to syntax check my stuff?) get quite long, and sometimes even crash/hang. 

The result is that after i've been typing for a bit in such a file, the responsiveness of editing goes way down, causing me to look down at the status bar to see a slow/hung "Building workspace" message. Sometimes I even have to kill the IDE to recover -- it never comes back.

1) Is this normal/expected?

Yes.

2) Are the some options I can turn off to alleviate this overload when using type-heavy, type-generating code like this?

You can disable semantic highlighting, mark occurrences and implicit highlighting. But you can't disable the presentation compiler completely. This is a feature that still needs to be added to the IDE. The compiler can't be canceled when it typechecks a file and the IDE doesn't provide enough logic around it to keep the UI responsive in cases the compiler is too slow.

What I do in such situations is to rely on external editors. This is not what should be done, but that is the situation right now.

Thanks,

Rich

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/eb9fdaec-4ddd-49c1-b18f-b81fd5e205eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rich Henry]

Thanks Simon. I will experiment with those options and see where I end up.

Just trying to make sure that my installation isn't defective.

[iulian dragos]

Well, if it's "Building Workspace", you might want to disable "Build automatically"... I don't miss it at all.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/9f02e341-3ef7-45c6-9ecd-c08593e52d5b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

« Je déteste la montagne, ça cache le paysage »
Alphonse Allais

[Clint Gilbert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've disabled this, and when I did, I missed it a lot. What do you
recommend instead?

>> scala-ide-use...@__googlegroups.com. To view this discussion on
>> the web visit
>> https://groups.google.com/d/__msgid/scala-ide-user/eb9fdaec-__4ddd-49c1-b18f-b81fd5e205eb%__40googlegroups.com
>>
>>
<https://groups.google.com/d/msgid/scala-ide-user/eb9fdaec-4ddd-49c1-b18f-b81fd5e205eb%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/__optout
>> <https://groups.google.com/d/optout>.

>
> -- You received this message because you are subscribed to the
> Google Groups "Scala IDE User" group. To unsubscribe from this
> group and stop receiving emails from it, send an email to
> scala-ide-use...@googlegroups.com

> <mailto:scala-ide-use...@googlegroups.com>. To view this

> discussion on the web visit

> https://groups.google.com/d/msgid/scala-ide-user/9f02e341-3ef7-45c6-9ecd-c08593e52d5b%40googlegroups.com
>
>
<https://groups.google.com/d/msgid/scala-ide-user/9f02e341-3ef7-45c6-9ecd-c08593e52d5b%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> -- « Je déteste la montagne, ça cache le paysage » Alphonse Allais
>

> -- You received this message because you are subscribed to the
> Google Groups "Scala IDE User" group. To unsubscribe from this
> group and stop receiving emails from it, send an email to
> scala-ide-use...@googlegroups.com

> <mailto:scala-ide-use...@googlegroups.com>. To view this

> discussion on the web visit

> https://groups.google.com/d/msgid/scala-ide-user/CAOwe9fbdVpFH1EmN%3DLCQA%3Dwib9VPQvyg2XtuJqN_euUq055GbQ%40mail.gmail.com
>
>
<https://groups.google.com/d/msgid/scala-ide-user/CAOwe9fbdVpFH1EmN%3DLCQA%3Dwib9VPQvyg2XtuJqN_euUq055GbQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlTjxc8ACgkQ0GFaTS4nYxsMjACfQRIY1lsiPfQoJQez54c1XwVG
mGIAoJmdAZT2b0gjjNx6Va3ZihJdj9tG
=SyOX
-----END PGP SIGNATURE-----

[iulian dragos]

On Tue, Feb 17, 2015 at 11:50 PM, Clint Gilbert <clint_...@hms.harvard.edu> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've disabled this, and when I did, I missed it a lot.  What do you
recommend instead?

I usually build manually (Ctrl-B), but I also have the following options on the Run/Debug -> Launching page (in case I forget and just try to launch):

- Build (if required) before launching

- Wait for ongoing builds: Always

- Save required dirty editors before launching: Ask

iulian

 

To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/54E3C5CF.1050809%40hms.harvard.edu.

For more options, visit https://groups.google.com/d/optout.

[Ed Maphis]

Meh, I'm surprised type checking doesn't run on a separate thread.

[iulian dragos]

Ed, welcome to the scala-ide-user mailing list!

The type-checker *does* run on a separate thread. So does the builder. There's a lot of concurrency in Eclipse :) What made you think otherwise?

On Fri, Feb 20, 2015 at 8:13 PM, Ed Maphis <emap...@gmail.com> wrote:

Meh, I'm surprised type checking doesn't run on a separate thread.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/618123b3-1f15-408f-8924-6acc76477d46%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Colin Bester]

Seems that this is an ongoing issue in one way or another. My system (exact same project) will crunch along just fine and then it will slow down and take 10 maybe 15 minutes to build the workspace. Due to this issue I consistently shutdown and restart scala-ide every day, have only one or two projects open in my workspace at a time. Have 4GB assigned to eclipse, 2GB set for MAVEN_OPTS (not sure this is needed). I am running on latest OSX on a MacBook Pro (2.8GHz) so system resources should not be an issue.

I will change one line of code in one file ( I admit there are many dependencies) and the 10 minute wait will begin - it will sit on currying, then on mixin and so on until I go get a cup of coffee (yeah, I like that part).

Rebooting, starting eclipse with -clean option doesn't help. 

I can't replicate, quote a fix or predict when it will happen.

[Simon Schäfer]

On 28.12.2015 15:12, Colin Bester wrote:

Seems that this is an ongoing issue in one way or another. My system (exact same project) will crunch along just fine and then it will slow down and take 10 maybe 15 minutes to build the workspace. Due to this issue I consistently shutdown and restart scala-ide every day, have only one or two projects open in my workspace at a time. Have 4GB assigned to eclipse, 2GB set for MAVEN_OPTS (not sure this is needed). I am running on latest OSX on a MacBook Pro (2.8GHz) so system resources should not be an issue.

I will change one line of code in one file ( I admit there are many dependencies) and the 10 minute wait will begin - it will sit on currying, then on mixin and so on until I go get a cup of coffee (yeah, I like that part).

How long does a full build with maven take? When you watch the progress bar, can you see that the compilation takes a very long time for only single files or is this the behavior throughout all existing files?

Rebooting, starting eclipse with -clean option doesn't help. 

I can't replicate, quote a fix or predict when it will happen.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/bda9672a-d23c-43fa-8364-51999960b332%40googlegroups.com.

[Colin Bester]

See below.

On Monday, December 28, 2015 at 11:15:18 AM UTC-6, Simon Schäfer wrote:

On 28.12.2015 15:12, Colin Bester wrote:

Seems that this is an ongoing issue in one way or another. My system (exact same project) will crunch along just fine and then it will slow down and take 10 maybe 15 minutes to build the workspace. Due to this issue I consistently shutdown and restart scala-ide every day, have only one or two projects open in my workspace at a time. Have 4GB assigned to eclipse, 2GB set for MAVEN_OPTS (not sure this is needed). I am running on latest OSX on a MacBook Pro (2.8GHz) so system resources should not be an issue.

I will change one line of code in one file ( I admit there are many dependencies) and the 10 minute wait will begin - it will sit on currying, then on mixin and so on until I go get a cup of coffee (yeah, I like that part).

How long does a full build with maven take? When you watch the progress bar, can you see that the compilation takes a very long time for only single files or is this the behavior throughout all existing files?

When I compile using maven via command line it goes way quicker, a minute or so for full compile - no noticeable delays as it compiles. When compiling via scala-ide it will get 'stuck' on a single file - view progress bar in progress window it will stay on, for example, currying for 5 minutes or more, then move on to, say, fixing where it will sit for 5 minutes or more.

Seems like (but can't be sure) that every stage of build for some reason takes longer, some of the stages of build are foreign to me.

[Simon Schäfer]

On 28.12.2015 18:43, Colin Bester wrote:

See below.

On Monday, December 28, 2015 at 11:15:18 AM UTC-6, Simon Schäfer wrote:

On 28.12.2015 15:12, Colin Bester wrote:

Seems that this is an ongoing issue in one way or another. My system (exact same project) will crunch along just fine and then it will slow down and take 10 maybe 15 minutes to build the workspace. Due to this issue I consistently shutdown and restart scala-ide every day, have only one or two projects open in my workspace at a time. Have 4GB assigned to eclipse, 2GB set for MAVEN_OPTS (not sure this is needed). I am running on latest OSX on a MacBook Pro (2.8GHz) so system resources should not be an issue.

I will change one line of code in one file ( I admit there are many dependencies) and the 10 minute wait will begin - it will sit on currying, then on mixin and so on until I go get a cup of coffee (yeah, I like that part).

How long does a full build with maven take? When you watch the progress bar, can you see that the compilation takes a very long time for only single files or is this the behavior throughout all existing files?

When I compile using maven via command line it goes way quicker, a minute or so for full compile - no noticeable delays as it compiles. When compiling via scala-ide it will get 'stuck' on a single file - view progress bar in progress window it will stay on, for example, currying for 5 minutes or more, then move on to, say, fixing where it will sit for 5 minutes or more.

Seems like (but can't be sure) that every stage of build for some reason takes longer, some of the stages of build are foreign to me.

It is not the expected behavior that Scala IDE takes longer to compile than a full build. However, I can't say where the problem could come from without getting more information about your project. Would you please enable debug logging in Preferences > Scala > Logging, then clean and build the project afterwards. In Scala > Open Log you should get lots of information. Could you please post what it says there from the moment when you started the build?

Maybe it is a problem in your workspace. If you create a new workspace and then import the project, do you still see the huge slowdowns?

Rebooting, starting eclipse with -clean option doesn't help. 

I can't replicate, quote a fix or predict when it will happen.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/bda9672a-d23c-43fa-8364-51999960b332%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/24df39ab-6236-48e6-99ea-90ec2c26846e%40googlegroups.com.

[Colin Bester]

I haven't tried recreating workspace - this is a dev machine so I tend to not mess around - the strange thing is that at times (same projects, same workspace) it works fine - like right now.

When problem occurs I will enable logging and post results.

Could there be some unexpected issue building workspace if internet connection is not available - to me there seems to be a connection, but could be way off base.

~C

[Simon Schäfer]

scala-ide doesn't require an Internet connection to function - I would be surprised if that is the reason for the huge delays. Do you have some other plugins installed that could intervene with the build?

~C

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/1d7c1d63-767b-4140-8437-88396386fc46%40googlegroups.com.

[Colin Bester]

I agree.

I am running scala-ide straight out the box, no added plugins - only changes I have made is to eclipse.ini to increase heap size.

[Colin Bester]

Not sure it helps or is related but at times when compiling via scala-ide I keep getting out of heap memory - this is run via run confurations with goal of "install".

If I run via command line using mvn install it compiles rapidly and with no heap errors.

[Simon Schäfer]

On 29.12.2015 23:50, Colin Bester wrote:

Not sure it helps or is related but at times when compiling via scala-ide I keep getting out of heap memory - this is run via run confurations with goal of "install".

If I run via command line using mvn install it compiles rapidly and with no heap errors.

Maybe you just didn't configure the heap correctly? What are the JVM arguments that are used for Eclipse?

On Monday, December 28, 2015 at 2:08:54 PM UTC-6, Colin Bester wrote:

I agree.

I am running scala-ide straight out the box, no added plugins - only changes I have made is to eclipse.ini to increase heap size.

On Monday, December 28, 2015 at 2:01:58 PM UTC-6, Simon Schäfer wrote:

On 28.12.2015 19:52, Colin Bester wrote:

I haven't tried recreating workspace - this is a dev machine so I tend to not mess around - the strange thing is that at times (same projects, same workspace) it works fine - like right now.

When problem occurs I will enable logging and post results.

Could there be some unexpected issue building workspace if internet connection is not available - to me there seems to be a connection, but could be way off base.

scala-ide doesn't require an Internet connection to function - I would be surprised if that is the reason for the huge delays. Do you have some other plugins installed that could intervene with the build?

~C

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/1d7c1d63-767b-4140-8437-88396386fc46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/fc05d4e3-3a19-4cd4-b38a-22426ee33a5a%40googlegroups.com.

[Colin Bester]

That would be nice if it's the case :-)

cat eclipse.ini shows

-startup

../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar

--launcher.library

../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20150204-1316

-vmargs

-Xmx2G

-Xms1G

-XX:MaxPermSize=384m

-XstartOnFirstThread

-Dorg.eclipse.swt.internal.carbon.smallFonts

-Declipse.filesystem.useNatives=false

When eclipse starts failing to compile I find shutting down eclipse and firing it back up helps. Heap monitor on tool bar never climbs up above 1.5GB and clicking the trash icon to force GC doesn't help.

System has 16GB available

[iulian dragos]

What version of Java are you using? By far the most likely issue is memory thrashing. Try increasing the heap memory for Eclipse, since it seems you can afford it. There might be some memory leak that you don't always hit.

iulian

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/ef2ff35f-0503-4d36-b0c3-a7e33bb08904%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

[Colin Bester]

Presently I am using Java 1.7.0_25-b15 due to overall project - updating is going to be pretty major.

I have pushed heap up to 6GB but still have this issue from time to time - same code, same amount of 'up time' (time since restarting ide) Overall I would agree that increasing heap time does speed things up but no where near as fast as comping using mvn via command line - note that at times it's a simple change to a comment that can take minutes to build workspace.

[Scott Carey]

A few things I've noted over the years:

   Even one file somewhere that does not line up in the file system with its package can wreck things.   For example, make sure you don't have anything in path com/app/foo/bar but package com.app.bar.foo. 

   Try turning off "build automatically".  This comes with consequences, but can be worth it.  This especially helps the "all I did is change a comment!" sort of delays.

   If you have mixed java/scala projects -- good luck!  It will likely occasionally end up in freaky strange states where it can't find things across the language boundary that it should.  Usually rebuilding, then restarting, then rebuilding (again) helps get it back.  And it usually doesn't re-occur immediately so you've got a couple days to code before fixing your IDE again while browsing reddit.  Usually.

   Some complicated type-level implicit code will simply fail.  SBT will build, but ScalaIDE won't.  This may be better these days, as I last dealt with that about 5 months ago.  The code was isolated enough that I could just disable the project it was in and ignore the issue.  Also, even SBT can take a minute to compile a single method with this sort of code, and that simply leads to unresponsiveness in the IDE, so I would not recommend working on that sort of code in ScalaIDE at all.

   Organize imports is ... often broken.  Don't even think about trying it if everything isn't currently in a clean build state.   Also, for some files it will remove things that are required for it to compile.  I haven't looked into this in detail, I always run into it when I don't have the time to fiddle with it and revert the change instead and organize manually.



Its still nice when it works.  And it works often enough for me to keep using it most of the time.  However I am now investing in learning to use Atom, because I have to hedge my investment against the risk that this never makes it to where I need it to be.

[Colin Bester]

Scott I largely agree with you and have been using eclipse from the early days. I can't afford to make a change at present but am starting to look at alternatives as these quirks have been going on a long time now.

I never use the resolve imports as it messes up more than it helps and can't recall when last I combined java and scala (maybe this is working today but I know it gave issues).

When making non-code changes I always switch of build automatically but it's not right that I should do this but it does help.

Scott, I am not exactly sure what you mean by "For example, make sure you don't have anything in path com/app/foo/bar but package com.app.bar.foo." I assume you mean always make sure package matches path (I see bar.foo is swapped in example which I assume is intention)?

I often run tests and do debugging with my internet disabled (I'm just paranoid) and to me, the build workspace issues seems to raise its head more often when I have switched off my wifi....... could be a red-herring...

~C

[Colin Bester]

Scott, BTW I wasn't implying I didn't agree with anything - just that I haven't seen/experienced all of what you say :-) Bad, choice of words on my part.

[iulian dragos]

On Mon, Jan 11, 2016 at 3:15 PM, Colin Bester <bester...@gmail.com> wrote:

Presently I am using Java 1.7.0_25-b15 due to overall project - updating is going to be pretty major.

I have pushed heap up to 6GB but still have this issue from time to time - same code, same amount of 'up time' (time since restarting ide) Overall I would agree that increasing heap time does speed things up but no where near as fast as comping using mvn via command line - note that at times it's a simple change to a comment that can take minutes to build workspace.

One other thing I noticed was insufficient PermSpace (needed to store classes). This can lead to the JIT compiler being turned off. If you can upgrade to Java 1.8, this would “just work”, but otherwise add -XX:MaxPermSize=256m to your eclipse.ini. I wrote about it on this list a while ago, but I can’t find the email right now.

Any chance you could attach a profiler when this happens, or just take a few thread dumps? VisualVM is quite easy to use, otherwise jstack <pid> could also help.

cheers,
iulian

On Monday, January 11, 2016 at 5:09:09 AM UTC-6, Iulian Dragos wrote:

What version of Java are you using? By far the most likely issue is memory thrashing. Try increasing the heap memory for Eclipse, since it seems you can afford it. There might be some memory leak that you don't always hit.

iulian

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/689f5023-20b7-4ac5-b72a-675dd6ea8abf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

​

[Renato Garcia]

I often run tests and do debugging with my internet disabled (I'm just paranoid) and to me, the build workspace issues seems to raise its head more often when I have switched off my wifi....... could be a red-herring...

Colin,

You could check if you your project is setup as a maven project in Eclipse IDE. If that's the case you could try disabling the Maven Project Builder in the project properties Builders or/and try setting Maven Offline at Preferences -> Maven and see if it helps.

Regards,

Renato 

[Colin Bester]

I have permspace set at 512m (-XX:MaxPermSize=512m).

I do plan to upgrade servers to java 1.8 later this year which will allow me to use 1.8 for this project.

I am in full on testing mode at present, hence not aggressively trying to dig in to this issue, but hope to get back on it in a week or so.

~C

[Colin Bester]

I thought I had set maven offline in global preferences but I hadn't (it was set to offline in run configurations) so will see if this helps at all.

I will try disable the maven builder and see how this helps.

[Scott Carey]

On Tuesday, January 12, 2016 at 6:38:49 AM UTC-8, Colin Bester wrote:

I have permspace set at 512m (-XX:MaxPermSize=512m).

I do plan to upgrade servers to java 1.8 later this year which will allow me to use 1.8 for this project.

The project doesn't have to use Java 8 (it can compile to Java 7 or 6).  Its the JRE that Eclipse/ScalaIDE is using to run inside of that can avoid perm gen issues by using Java 8.

I have run into this issue a while ago, where JIT compilation stopped leading to very very slow scalac compilation.  I've been on Java 8 for a while now though.

[Scott Carey]

On Monday, January 11, 2016 at 12:05:01 PM UTC-8, Colin Bester wrote:

Scott I largely agree with you and have been using eclipse from the early days. I can't afford to make a change at present but am starting to look at alternatives as these quirks have been going on a long time now.

I never use the resolve imports as it messes up more than it helps and can't recall when last I combined java and scala (maybe this is working today but I know it gave issues).

When making non-code changes I always switch of build automatically but it's not right that I should do this but it does help.

Scott, I am not exactly sure what you mean by "For example, make sure you don't have anything in path com/app/foo/bar but package com.app.bar.foo." I assume you mean always make sure package matches path (I see bar.foo is swapped in example which I assume is intention)?

Yes, the intention is to imply that the path must match the package.   We once had something like the above, where the path / package had swapped one part of the path.   This had a huge negative performance impact on all projects that depended on the one with the mismatch.

 

[Colin Bester]

I have installed java 8 for testing and see in Info.plist (I am running on mac) there is entry allowing you to set path for java if different from the system default. I have set this to point to java8 home and eclipse appears to start up fine.

In preferences there is option to set java jre, how does this differ from what's listed in Info.plist - is this what will be used to run my project while eclipse runs on version specified in Info.plist?

Is there a way to validate what java eclipse is running on?

Thanks!

Colin

[Colin Bester]

Found answer to one of my questions - Help -> Installation Details -> Configuration shows the java version used - can't believe I looked without seeing...

[iulian dragos]

On Fri, Jan 15, 2016 at 4:17 PM, Colin Bester <bester...@gmail.com> wrote:

I have installed java 8 for testing and see in Info.plist (I am running on mac) there is entry allowing you to set path for java if different from the system default. I have set this to point to java8 home and eclipse appears to start up fine.

In preferences there is option to set java jre, how does this differ from what's listed in Info.plist - is this what will be used to run my project while eclipse runs on version specified in Info.plist?

That's used for building and running your projects, yes.

 

Is there a way to validate what java eclipse is running on?

Thanks!

Colin

On Thursday, January 14, 2016 at 7:48:33 PM UTC-6, Scott Carey wrote:

On Tuesday, January 12, 2016 at 6:38:49 AM UTC-8, Colin Bester wrote:

I have permspace set at 512m (-XX:MaxPermSize=512m).

I do plan to upgrade servers to java 1.8 later this year which will allow me to use 1.8 for this project.

The project doesn't have to use Java 8 (it can compile to Java 7 or 6).  Its the JRE that Eclipse/ScalaIDE is using to run inside of that can avoid perm gen issues by using Java 8.

I have run into this issue a while ago, where JIT compilation stopped leading to very very slow scalac compilation.  I've been on Java 8 for a while now though.

--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-user/60ae4db2-d9f5-4a22-9469-b5e8b0ae82de%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.