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.

Bug 249103 - StackOverFlow in Kenai Dashboard
Summary: StackOverFlow in Kenai Dashboard
Status: RESOLVED INVALID
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Kenai (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-04 12:20 UTC by Jaroslav Tulach
Modified: 2016-05-25 06:10 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 213903

Attachments
Thread dump with stack overflow (583.18 KB, text/plain)
2014-12-05 07:11 UTC, Tomas Hurka 		Details
stacktrace (2.46 KB, text/plain)
2015-04-20 16:40 UTC, IrianR 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2014-12-04 12:20:52 UTC 
See http://statistics.netbeans.org/exceptions/exception.do?id=748566
and my analysis in issue 235748:


The thread dump in the issue shows your IDE is parsing/checking the disk. That is however not a reason to throw OOME.

There is 7M of TreeMap.Entry instances occupying 412MB of memory. It could be related to javax.management.openmbean.CompositeDataSupport which has 1.4M of instances. Possibly the slowness detector profiler has problems with deep stack traces that happen when StackOverFlowError is raised. And yes, there is one in messages.log:

	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.create(OneProjectDashboard.java:132)
	at org.netbeans.modules.team.server.ui.common.DashboardSupport.<init>(DashboardSupport.java:96)
	at org.netbeans.modules.kenai.ui.api.KenaiServer.<init>(KenaiServer.java:103)
	at org.netbeans.modules.kenai.ui.api.KenaiServer.forKenai(KenaiServer.java:154)
	at org.netbeans.modules.kenai.ui.impl.TeamServerProviderImpl.getTeamServer(TeamServerProviderImpl.java:145)
	at org.netbeans.modules.team.server.api.TeamServerManager.getTeamServer(TeamServerManager.java:129)
	at org.netbeans.modules.team.server.Utilities.getLastTeamServer(Utilities.java:89)
	at org.netbeans.modules.team.server.TeamView.<init>(TeamView.java:100)
	at org.netbeans.modules.team.server.TeamView.getInstance(TeamView.java:140)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.getProjectPicker(OneProjectDashboard.java:1047)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.loadSelectedProject(OneProjectDashboard.java:609)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.handleLogin(OneProjectDashboard.java:310)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.initServer(OneProjectDashboard.java:267)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.<init>(OneProjectDashboard.java:196)
	at org.netbeans.modules.team.server.ui.common.OneProjectDashboard.create(OneProjectDashboard.java:132)
Comment 1 Tomas Hurka 2014-12-05 07:11:02 UTC 
Created attachment 150902 [details]
Thread dump with stack overflow

Attached is a thread dump extracted from a slowness report extracted from attached heap dump. It shows stack overflow in "AWT-EventQueue-0".
Comment 2 IrianR 2015-04-20 16:40:52 UTC 
Created attachment 153277 [details]
stacktrace

Was working normally when IDE froze for a really long time on invoking code completion; afterwards it resumed and I was able to continue working with an apparently hung "saving snapshot" process.

After confirming that the "saving snapshot" was really hung, I restarted the IDE and this is the report that popped up immediately after restart.
Comment 3 Exceptions Reporter 2015-04-20 16:40:56 UTC 
This bug already has 10 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=213903