After updating to the last nightly build, I get some internal build
errors.
They are extremely problematic because they can block the UI-Thread for
about 5 to 10 seconds. First I thought it is related to the bug that
lets semantic highlighting running forever but after deactivating
semantic highlighting the errors still occur. It seems that the errors
are unproblematic on simple save actions but when I want to use
hyperlinking for example the UI-Thread is blocked for several seconds.
I've seen similar, it's a binary incompatibility between different
versions of 2.10 nightlies. It looks like your system has an older
scala-refactoring build, that is incompatible with the compiler
bundle. Can you paste here the version of the scala.library/compiler
bundle, and also scala-refactoring? (the first 2 can easily be
copy-pasted from the Scala/Report A Bug dialog).
The second is not an exception per se, it's not thrown: it's a timeout
in ask-option, and we print the stack trace for debugging purposes.
On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
> After updating to the last nightly build, I get some internal build
> errors.
> They are extremely problematic because they can block the UI-Thread for
> about 5 to 10 seconds. First I thought it is related to the bug that
> lets semantic highlighting running forever but after deactivating
> semantic highlighting the errors still occur. It seems that the errors
> are unproblematic on simple save actions but when I want to use
> hyperlinking for example the UI-Thread is blocked for several seconds.
> I've seen similar, it's a binary incompatibility between different
> versions of 2.10 nightlies. It looks like your system has an older
> scala-refactoring build, that is incompatible with the compiler
> bundle. Can you paste here the version of the scala.library/compiler
> bundle, and also scala-refactoring? (the first 2 can easily be
> copy-pasted from the Scala/Report A Bug dialog).
> The second is not an exception per se, it's not thrown: it's a timeout
> in ask-option, and we print the stack trace for debugging purposes.
> It would be great to get to the bottom of this..
> thanks,
> iulian
> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>> After updating to the last nightly build, I get some internal build
>> errors.
>> They are extremely problematic because they can block the UI-Thread for
>> about 5 to 10 seconds. First I thought it is related to the bug that
>> lets semantic highlighting running forever but after deactivating
>> semantic highlighting the errors still occur. It seems that the errors
>> are unproblematic on simple save actions but when I want to use
>> hyperlinking for example the UI-Thread is blocked for several seconds.
> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>> Hi Simon,
>> I've seen similar, it's a binary incompatibility between different
>> versions of 2.10 nightlies. It looks like your system has an older
>> scala-refactoring build, that is incompatible with the compiler
>> bundle. Can you paste here the version of the scala.library/compiler
>> bundle, and also scala-refactoring? (the first 2 can easily be
>> copy-pasted from the Scala/Report A Bug dialog).
>> The second is not an exception per se, it's not thrown: it's a timeout
>> in ask-option, and we print the stack trace for debugging purposes.
>> It would be great to get to the bottom of this..
>> thanks,
>> iulian
>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>>> After updating to the last nightly build, I get some internal build
>>> errors.
>>> They are extremely problematic because they can block the UI-Thread for
>>> about 5 to 10 seconds. First I thought it is related to the bug that
>>> lets semantic highlighting running forever but after deactivating
>>> semantic highlighting the errors still occur. It seems that the errors
>>> are unproblematic on simple save actions but when I want to use
>>> hyperlinking for example the UI-Thread is blocked for several seconds.
> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>> Hi Simon,
>> I've seen similar, it's a binary incompatibility between different
>> versions of 2.10 nightlies. It looks like your system has an older
>> scala-refactoring build, that is incompatible with the compiler
>> bundle. Can you paste here the version of the scala.library/compiler
>> bundle, and also scala-refactoring? (the first 2 can easily be
>> copy-pasted from the Scala/Report A Bug dialog).
>> The second is not an exception per se, it's not thrown: it's a timeout
>> in ask-option, and we print the stack trace for debugging purposes.
>> It would be great to get to the bottom of this..
>> thanks,
>> iulian
>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>>> After updating to the last nightly build, I get some internal build
>>> errors.
>>> They are extremely problematic because they can block the UI-Thread for
>>> about 5 to 10 seconds. First I thought it is related to the bug that
>>> lets semantic highlighting running forever but after deactivating
>>> semantic highlighting the errors still occur. It seems that the errors
>>> are unproblematic on simple save actions but when I want to use
>>> hyperlinking for example the UI-Thread is blocked for several seconds.
and this has nothing to do with sematic highlighting forever issue?
A nightly from a couple of days ago made progress in the sense that after a few minutes the hung thread is resolved (interestingly, only when I shift focus away from the IDE and do something else like check email).
> Oh, the null at the end was supposed to be the git hash. Fixing this now, > thanks Simon!
> > On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote: > >> Hi Simon,
> >> I've seen similar, it's a binary incompatibility between different > >> versions of 2.10 nightlies. It looks like your system has an older > >> scala-refactoring build, that is incompatible with the compiler > >> bundle. Can you paste here the version of the scala.library/compiler > >> bundle, and also scala-refactoring? (the first 2 can easily be > >> copy-pasted from the Scala/Report A Bug dialog).
> >> The second is not an exception per se, it's not thrown: it's a timeout > >> in ask-option, and we print the stack trace for debugging purposes.
> >> It would be great to get to the bottom of this..
> >> thanks, > >> iulian
> >> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <ma...@antoras.de<javascript:>> > wrote: > >>> After updating to the last nightly build, I get some internal build > >>> errors.
> >>> They are extremely problematic because they can block the UI-Thread > for > >>> about 5 to 10 seconds. First I thought it is related to the bug that > >>> lets semantic highlighting running forever but after deactivating > >>> semantic highlighting the errors still occur. It seems that the errors > >>> are unproblematic on simple save actions but when I want to use > >>> hyperlinking for example the UI-Thread is blocked for several seconds.
I guess the fix is to add a `scala.reflect.io;resolution:=optional` in the scala-refactoring MANIFEST. I'm already working on a small patch for fixing the `null` git-hash suffix, I could also push this little fix together.
>> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>>> Hi Simon,
>>> I've seen similar, it's a binary incompatibility between different
>>> versions of 2.10 nightlies. It looks like your system has an older
>>> scala-refactoring build, that is incompatible with the compiler
>>> bundle. Can you paste here the version of the scala.library/compiler
>>> bundle, and also scala-refactoring? (the first 2 can easily be
>>> copy-pasted from the Scala/Report A Bug dialog).
>>> The second is not an exception per se, it's not thrown: it's a timeout
>>> in ask-option, and we print the stack trace for debugging purposes.
>>> It would be great to get to the bottom of this..
>>> thanks,
>>> iulian
>>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>>>> After updating to the last nightly build, I get some internal build
>>>> errors.
>>>> They are extremely problematic because they can block the UI-Thread for
>>>> about 5 to 10 seconds. First I thought it is related to the bug that
>>>> lets semantic highlighting running forever but after deactivating
>>>> semantic highlighting the errors still occur. It seems that the errors
>>>> are unproblematic on simple save actions but when I want to use
>>>> hyperlinking for example the UI-Thread is blocked for several seconds.
On Sun, Oct 7, 2012 at 2:41 PM, virtualeyes <sit1...@gmail.com> wrote:
> and this has nothing to do with sematic highlighting forever issue?
> A nightly from a couple of days ago made progress in the sense that after a
> few minutes the hung thread is resolved (interestingly, only when I shift
> focus away from the IDE and do something else like check email).
The timeout is 10 seconds. I don't think it has anything to do with the focus.
>> Oh, the null at the end was supposed to be the git hash. Fixing this now,
>> thanks Simon!
>> > On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>> >> Hi Simon,
>> >> I've seen similar, it's a binary incompatibility between different
>> >> versions of 2.10 nightlies. It looks like your system has an older
>> >> scala-refactoring build, that is incompatible with the compiler
>> >> bundle. Can you paste here the version of the scala.library/compiler
>> >> bundle, and also scala-refactoring? (the first 2 can easily be
>> >> copy-pasted from the Scala/Report A Bug dialog).
>> >> The second is not an exception per se, it's not thrown: it's a timeout
>> >> in ask-option, and we print the stack trace for debugging purposes.
>> >> It would be great to get to the bottom of this..
>> >> thanks,
>> >> iulian
>> >> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <ma...@antoras.de>
>> >> wrote:
>> >>> After updating to the last nightly build, I get some internal build
>> >>> errors.
>> >>> They are extremely problematic because they can block the UI-Thread
>> >>> for
>> >>> about 5 to 10 seconds. First I thought it is related to the bug that
>> >>> lets semantic highlighting running forever but after deactivating
>> >>> semantic highlighting the errors still occur. It seems that the errors
>> >>> are unproblematic on simple save actions but when I want to use
>> >>> hyperlinking for example the UI-Thread is blocked for several seconds.
> I guess the fix is to add a `scala.reflect.io;resolution:=optional` in
> the scala-refactoring MANIFEST. I'm already
> working on a small patch for fixing the `null` git-hash suffix, I could
> also push this little fix together.
> > iulian
> > On Sun, Oct 7, 2012 at 11:32 AM, Simon Schäfer <m...@antoras.de> wrote:
> >> The information from scala-ide:
> >> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
> >>> Hi Simon,
> >>> I've seen similar, it's a binary incompatibility between different
> >>> versions of 2.10 nightlies. It looks like your system has an older
> >>> scala-refactoring build, that is incompatible with the compiler
> >>> bundle. Can you paste here the version of the scala.library/compiler
> >>> bundle, and also scala-refactoring? (the first 2 can easily be
> >>> copy-pasted from the Scala/Report A Bug dialog).
> >>> The second is not an exception per se, it's not thrown: it's a timeout
> >>> in ask-option, and we print the stack trace for debugging purposes.
> >>> It would be great to get to the bottom of this..
> >>> thanks,
> >>> iulian
> >>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de>
> wrote:
> >>>> After updating to the last nightly build, I get some internal build
> >>>> errors.
> >>>> They are extremely problematic because they can block the UI-Thread
> for
> >>>> about 5 to 10 seconds. First I thought it is related to the bug that
> >>>> lets semantic highlighting running forever but after deactivating
> >>>> semantic highlighting the errors still occur. It seems that the errors
> >>>> are unproblematic on simple save actions but when I want to use
> >>>> hyperlinking for example the UI-Thread is blocked for several seconds.
> I guess the fix is to add a `scala.reflect.io;resolution:=optional` in the scala-refactoring MANIFEST. I'm already
> working on a small patch for fixing the `null` git-hash suffix, I could also push this little fix together.
>> iulian
>> On Sun, Oct 7, 2012 at 11:32 AM, Simon Schäfer <m...@antoras.de> wrote:
>>> The information from scala-ide:
>>> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>>>> Hi Simon,
>>>> I've seen similar, it's a binary incompatibility between different
>>>> versions of 2.10 nightlies. It looks like your system has an older
>>>> scala-refactoring build, that is incompatible with the compiler
>>>> bundle. Can you paste here the version of the scala.library/compiler
>>>> bundle, and also scala-refactoring? (the first 2 can easily be
>>>> copy-pasted from the Scala/Report A Bug dialog).
>>>> The second is not an exception per se, it's not thrown: it's a timeout
>>>> in ask-option, and we print the stack trace for debugging purposes.
>>>> It would be great to get to the bottom of this..
>>>> thanks,
>>>> iulian
>>>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>>>>> After updating to the last nightly build, I get some internal build
>>>>> errors.
>>>>> They are extremely problematic because they can block the UI-Thread for
>>>>> about 5 to 10 seconds. First I thought it is related to the bug that
>>>>> lets semantic highlighting running forever but after deactivating
>>>>> semantic highlighting the errors still occur. It seems that the errors
>>>>> are unproblematic on simple save actions but when I want to use
>>>>> hyperlinking for example the UI-Thread is blocked for several seconds.
>> I guess the fix is to add a `scala.reflect.io;resolution:=optional` in the scala-refactoring MANIFEST. I'm already
>> working on a small patch for fixing the `null` git-hash suffix, I could also push this little fix together.
>>> iulian
>>> On Sun, Oct 7, 2012 at 11:32 AM, Simon Schäfer <m...@antoras.de> wrote:
>>>> The information from scala-ide:
>>>> On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>>>>> Hi Simon,
>>>>> I've seen similar, it's a binary incompatibility between different
>>>>> versions of 2.10 nightlies. It looks like your system has an older
>>>>> scala-refactoring build, that is incompatible with the compiler
>>>>> bundle. Can you paste here the version of the scala.library/compiler
>>>>> bundle, and also scala-refactoring? (the first 2 can easily be
>>>>> copy-pasted from the Scala/Report A Bug dialog).
>>>>> The second is not an exception per se, it's not thrown: it's a timeout
>>>>> in ask-option, and we print the stack trace for debugging purposes.
>>>>> It would be great to get to the bottom of this..
>>>>> thanks,
>>>>> iulian
>>>>> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <m...@antoras.de> wrote:
>>>>>> After updating to the last nightly build, I get some internal build
>>>>>> errors.
>>>>>> They are extremely problematic because they can block the UI-Thread for
>>>>>> about 5 to 10 seconds. First I thought it is related to the bug that
>>>>>> lets semantic highlighting running forever but after deactivating
>>>>>> semantic highlighting the errors still occur. It seems that the errors
>>>>>> are unproblematic on simple save actions but when I want to use
>>>>>> hyperlinking for example the UI-Thread is blocked for several seconds.
On Sun, Oct 7, 2012 at 5:23 PM, Simon Schäfer <m...@antoras.de> wrote:
> Thanks, works well!
> The remaining problem now is that `askOption` can have a timeout. Any
> ideas on how to fix that?
The timeout is needed because we couldn't track down and fix a race
condition that is plaguing the IDE for months now: some `ask` calls are
never answered by the compiler, usually when the compiler is shutdown and
restarted. In order not to have freezes or threads that hang, we added the
timeout. I recently had a little breakthrough and been able to reproduce it
in the debugger, but we don't have a fix yet.
Regardless of when this is fixed, I think the timeout is necessary for all
operations that end up blocking the UI thread. Most users would gladly
trade-off some precision for snappiness.
I don't critisize the timeouts in general - my problem is only that they occur now for some days on nearly each save action, which is extremely annoying.
Is the timeout a simple constant that can be edited? If yes, where can I find it? Maybe a change can be useful on my local build (or at least in the debugger).
On Mon 08 Oct 2012 12:21:37 PM CEST, iulian dragos wrote:
> On Sun, Oct 7, 2012 at 5:23 PM, Simon Schäfer <m...@antoras.de
> <mailto:m...@antoras.de>> wrote:
> Thanks, works well!
> The remaining problem now is that `askOption` can have a timeout.
> Any ideas on how to fix that?
> The timeout is needed because we couldn't track down and fix a race
> condition that is plaguing the IDE for months now: some `ask` calls
> are never answered by the compiler, usually when the compiler is
> shutdown and restarted. In order not to have freezes or threads that
> hang, we added the timeout. I recently had a little breakthrough and
> been able to reproduce it in the debugger, but we don't have a fix yet.
> Regardless of when this is fixed, I think the timeout is necessary for
> all operations that end up blocking the UI thread. Most users would
> gladly trade-off some precision for snappiness.
> iulian
> On Sun 07 Oct 2012 03:36:53 PM CEST, iulian dragos wrote:
> On Sun, Oct 7, 2012 at 3:02 PM, Eugene Burmako
> <eugene.burm...@epfl.ch <mailto:eugene.burm...@epfl.ch>> wrote:
> Is this an OSGI problem then?
> Yes. It's fixed now, upgrade your nightlies, gentlemen!
> iulian
> --
> « Je déteste la montagne, ça cache le paysage »
> Alphonse Allais
> I don't critisize the timeouts in general - my problem is only that they occur now for some days on nearly each save action, which is extremely annoying.
Simon, I share your pain, and we need to fix it.
> Is the timeout a simple constant that can be edited? If yes, where can I find it? Maybe a change can be useful on my local build (or at least in the debugger).
No, it isn't a user-editable constant. The default value is hardcoded in `ScalaPresentationCompiler.askOption`, and it is currently set to 10s, which is probably not a good default in many cases.
I think we need to tune the timeout value on a case-by-case need. For instance, askOption calls in semantic highlighting should give back an answer almost instantaneously, as this calls should operate on an already type checked tree. Hence, I'd say that a good default for them should be 100/200ms.
Also, it would be much better to log timeouts in the scala-ide.log file alone (all those `Timeout in askOption` entries in the Error Log View are madness :))
> On Mon 08 Oct 2012 12:21:37 PM CEST, iulian dragos wrote:
>> On Sun, Oct 7, 2012 at 5:23 PM, Simon Schäfer <m...@antoras.de
>> <mailto:m...@antoras.de>> wrote:
>> Thanks, works well!
>> The remaining problem now is that `askOption` can have a timeout.
>> Any ideas on how to fix that?
>> The timeout is needed because we couldn't track down and fix a race
>> condition that is plaguing the IDE for months now: some `ask` calls
>> are never answered by the compiler, usually when the compiler is
>> shutdown and restarted. In order not to have freezes or threads that
>> hang, we added the timeout. I recently had a little breakthrough and
>> been able to reproduce it in the debugger, but we don't have a fix yet.
>> Regardless of when this is fixed, I think the timeout is necessary for
>> all operations that end up blocking the UI thread. Most users would
>> gladly trade-off some precision for snappiness.
>> iulian
>> On Sun 07 Oct 2012 03:36:53 PM CEST, iulian dragos wrote:
>> On Sun, Oct 7, 2012 at 3:02 PM, Eugene Burmako
>> <eugene.burm...@epfl.ch <mailto:eugene.burm...@epfl.ch>> wrote:
>> Is this an OSGI problem then?
>> Yes. It's fixed now, upgrade your nightlies, gentlemen!
>> iulian
>> --
>> « Je déteste la montagne, ça cache le paysage »
>> Alphonse Allais
---------------
Mirco Dotta
Typesafe - The software stack for applications that scale
PSE-D, 1015 Lausanne, Switzerland
Work: +41 (0)21 691 49 65
Twitter: @mircodotta
>> I don't critisize the timeouts in general - my problem is only that
>> they occur now for some days on nearly each save action, which is
>> extremely annoying.
> Simon, I share your pain, and we need to fix it.
>> Is the timeout a simple constant that can be edited? If yes, where
>> can I find it? Maybe a change can be useful on my local build (or at
>> least in the debugger).
> No, it isn't a user-editable constant. The default value is hardcoded
> in `ScalaPresentationCompiler.askOption`, and it is currently set to
> 10s, which is probably
> not a good default in many cases.
> I think we need to tune the timeout value on a case-by-case need. For
> instance, askOption calls in semantic highlighting should give back an
> answer almost
> instantaneously, as this calls should operate on an already
> type checked tree. Hence, I'd say that a good default for them should
> be 100/200ms.
> Also, it would be much better to log timeouts in the scala-ide.log
> file alone (all those `Timeout in askOption` entries in the Error Log
> View are madness :))
>> On Mon 08 Oct 2012 12:21:37 PM CEST, iulian dragos wrote:
>>> On Sun, Oct 7, 2012 at 5:23 PM, Simon Schäfer <m...@antoras.de
>>> <mailto:m...@antoras.de>
>>> <mailto:m...@antoras.de>> wrote:
>>> Thanks, works well!
>>> The remaining problem now is that `askOption` can have a timeout.
>>> Any ideas on how to fix that?
>>> The timeout is needed because we couldn't track down and fix a race
>>> condition that is plaguing the IDE for months now: some `ask` calls
>>> are never answered by the compiler, usually when the compiler is
>>> shutdown and restarted. In order not to have freezes or threads that
>>> hang, we added the timeout. I recently had a little breakthrough and
>>> been able to reproduce it in the debugger, but we don't have a fix yet.
>>> Regardless of when this is fixed, I think the timeout is necessary for
>>> all operations that end up blocking the UI thread. Most users would
>>> gladly trade-off some precision for snappiness.
>>> iulian
>>> On Sun 07 Oct 2012 03:36:53 PM CEST, iulian dragos wrote:
>>> On Sun, Oct 7, 2012 at 3:02 PM, Eugene Burmako
>>> <eugene.burm...@epfl.ch <mailto:eugene.burm...@epfl.ch>
>>> <mailto:eugene.burm...@epfl.ch>> wrote:
>>> Is this an OSGI problem then?
>>> Yes. It's fixed now, upgrade your nightlies, gentlemen!
>>> iulian
>>> --
>>> « Je déteste la montagne, ça cache le paysage »
>>> Alphonse Allais
On Sun, Oct 7, 2012 at 6:56 PM, virtualeyes <sit1...@gmail.com> wrote:
> k, can't get anything done with semantic highlighting enabled, hung thread
> issue just drags IDE performance to a crawl.
This issue has been fixed in recent nightlies. Can you please give it
another try?
> Have semantic highlighting disabled, pretty snappy, even with incremental
> builds -- the main drawback is of course, black code canvas against a bunch
> of white text ;-(
> Hopefully the issue will get sorted, semantic highlighting is a huge plus.
> Thanks
> On Sunday, October 7, 2012 3:02:10 PM UTC+2, Iulian Dragos wrote:
>> On Sun, Oct 7, 2012 at 2:41 PM, virtualeyes <sit...@gmail.com> wrote:
>> > and this has nothing to do with sematic highlighting forever issue?
>> > A nightly from a couple of days ago made progress in the sense that
>> after a
>> > few minutes the hung thread is resolved (interestingly, only when I
>> shift
>> > focus away from the IDE and do something else like check email).
>> The timeout is 10 seconds. I don't think it has anything to do with the
>> focus.
>> iulian
>> > On Sunday, October 7, 2012 2:30:31 PM UTC+2, Mirco Dotta wrote:
>> >> Oh, the null at the end was supposed to be the git hash. Fixing this
>> now,
>> >> thanks Simon!
>> >> > On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
>> >> >> Hi Simon,
>> >> >> I've seen similar, it's a binary incompatibility between different
>> >> >> versions of 2.10 nightlies. It looks like your system has an older
>> >> >> scala-refactoring build, that is incompatible with the compiler
>> >> >> bundle. Can you paste here the version of the
>> scala.library/compiler
>> >> >> bundle, and also scala-refactoring? (the first 2 can easily be
>> >> >> copy-pasted from the Scala/Report A Bug dialog).
>> >> >> The second is not an exception per se, it's not thrown: it's a
>> timeout
>> >> >> in ask-option, and we print the stack trace for debugging purposes.
>> >> >> It would be great to get to the bottom of this..
>> >> >> thanks,
>> >> >> iulian
>> >> >> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer <ma...@antoras.de>
>> >> >> wrote:
>> >> >>> After updating to the last nightly build, I get some internal
>> build
>> >> >>> errors.
>> >> >>> They are extremely problematic because they can block the
>> UI-Thread
>> >> >>> for
>> >> >>> about 5 to 10 seconds. First I thought it is related to the bug
>> that
>> >> >>> lets semantic highlighting running forever but after deactivating
>> >> >>> semantic highlighting the errors still occur. It seems that the
>> errors
>> >> >>> are unproblematic on simple save actions but when I want to use
>> >> >>> hyperlinking for example the UI-Thread is blocked for several
>> seconds.
> On Sun, Oct 7, 2012 at 6:56 PM, virtualeyes <sit1...@gmail.com
> <mailto:sit1...@gmail.com>> wrote:
> k, can't get anything done with semantic highlighting enabled,
> hung thread issue just drags IDE performance to a crawl.
> This issue has been fixed in recent nightlies. Can you please give it
> another try?
> iulian
> Have semantic highlighting disabled, pretty snappy, even with
> incremental builds -- the main drawback is of course, black code
> canvas against a bunch of white text ;-(
> Hopefully the issue will get sorted, semantic highlighting is a
> huge plus.
> Thanks
> On Sunday, October 7, 2012 3:02:10 PM UTC+2, Iulian Dragos wrote:
> On Sun, Oct 7, 2012 at 2:41 PM, virtualeyes <sit...@gmail.com>
> wrote:
> > and this has nothing to do with sematic highlighting forever
> issue?
> > A nightly from a couple of days ago made progress in the
> sense that after a
> > few minutes the hung thread is resolved (interestingly, only
> when I shift
> > focus away from the IDE and do something else like check
> email).
> The timeout is 10 seconds. I don't think it has anything to do
> with the focus.
> iulian
> > On Sunday, October 7, 2012 2:30:31 PM UTC+2, Mirco Dotta wrote:
> >> Oh, the null at the end was supposed to be the git hash.
> Fixing this now,
> >> thanks Simon!
> >> > On Sun 07 Oct 2012 08:23:19 AM CEST, iulian dragos wrote:
> >> >> Hi Simon,
> >> >> I've seen similar, it's a binary incompatibility between
> different
> >> >> versions of 2.10 nightlies. It looks like your system
> has an older
> >> >> scala-refactoring build, that is incompatible with the
> compiler
> >> >> bundle. Can you paste here the version of the
> scala.library/compiler
> >> >> bundle, and also scala-refactoring? (the first 2 can
> easily be
> >> >> copy-pasted from the Scala/Report A Bug dialog).
> >> >> The second is not an exception per se, it's not thrown:
> it's a timeout
> >> >> in ask-option, and we print the stack trace for
> debugging purposes.
> >> >> It would be great to get to the bottom of this..
> >> >> thanks,
> >> >> iulian
> >> >> On Sun, Oct 7, 2012 at 12:58 AM, Simon Schäfer
> <ma...@antoras.de>
> >> >> wrote:
> >> >>> After updating to the last nightly build, I get some
> internal build
> >> >>> errors.
> >> >>> They are extremely problematic because they can block
> the UI-Thread
> >> >>> for
> >> >>> about 5 to 10 seconds. First I thought it is related to
> the bug that
> >> >>> lets semantic highlighting running forever but after
> deactivating
> >> >>> semantic highlighting the errors still occur. It seems
> that the errors
> >> >>> are unproblematic on simple save actions but when I
> want to use
> >> >>> hyperlinking for example the UI-Thread is blocked for
> several seconds.
