This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE 6.8 (Build 200912041610) VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-b33 OS: Windows 2000, 5.0, x86 User Comments: GUEST: scala compiler allways dies on bigger projects: init: deps-jar: Compiling 40 scala and 55 java source files to D:\Projects\InternetCallCenter\Code\TrestoServerScala\build\classes (fsc,Argument 'D:\Projects\InternetCallCenter\Code\TrestoServerScala\src\org\puremvc\scala\multicore\core\Controller.scala' does not start with '-'. fsc -help gives more information) java.lang.StackOverflowError at scala.tools.nsc.typechecker.Typers$Typer.typed1(Typers.scala:3429) at scala.tools.nsc.typechecker.Typers$Typer.typed(Typers.scala:3744) at scala.tools.nsc.typechecker.Typers$Typer.typedQualifier(Typers.scala:3811) at scala.tools.nsc.typechecker.Typers$Typer.typed1(Typers.scala:3661) at scala.tools.nsc.typechecker.Typers$Typer.typed(Typers.scala:3744) at scala.tools.nsc.typechecker.Typers$Typer.typedQualifier(Typers.scala:3811) at scala.tools.nsc.typechecker.Typers$Typer.typed1(Typers.scala:3661) at scala.tools.nsc.typechecker.Typers aquaglia: Using the java editor Maximum slowness yet reported was 16327 ms, average is 6633
Created attachment 92852 [details] nps snapshot
Probably it shall be easy to move most of the action outside of AWT thread...
Very similar to bug #178497. AWT is waiting for a lock that is held by the write thread.
(In reply to comment #2) > Probably it shall be easy to move most of the action outside of AWT thread... Thanks Jaroslav, can you explain what you mean (or indicates me appropriate doc), please. I am using this architecture since 1996, and it's the first time I see a similar issue. However, the only thing that changed was an upgrade from Window7 to Window8.
Thanks Martin, You mean: The Netbeans UI (not the one I am coding and testing) is locked because it waits for the output to finish writing? As it was seldom the case with W7 (three weeks ago), and the only difference I can see is a decrease in the available RAM, do you think a RAM extension will solve the issue? Note: I do not thing the issue is specific to Netbeans, but it is the most sensitive product, may be because I spend more 10hrs/day on it. AlainD
*** Bug 245246 has been marked as a duplicate of this bug. ***