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 208200 - ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
Summary: ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
Status: RESOLVED INCOMPLETE
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-09 14:52 UTC by Exceptions Reporter
Modified: 2012-02-10 08:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 184901


Attachments
stacktrace (3.07 KB, text/plain)
2012-02-09 14:52 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2012-02-09 14:52:29 UTC
This issue was reported manually by thurka.
It already has 2 duplicates 


Build: NetBeans IDE 7.1 RC2 (Build 201111302200)
VM: Java HotSpot(TM) Client VM, 1.6.0-b105, Java(TM) SE Runtime Environment, 1.6.0-b105
OS: Windows XP

Stacktrace: 
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
   at org.netbeans.modules.profiler.heapwalk.OverviewController.getStackTrace(OverviewController.java:472)
   at org.netbeans.modules.profiler.heapwalk.OverviewController.computeThreads(OverviewController.java:330)
   at org.netbeans.modules.profiler.heapwalk.ui.OverviewControllerUI$1.run(OverviewControllerUI.java:143)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1411)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1991)
Comment 1 Exceptions Reporter 2012-02-09 14:52:32 UTC
Created attachment 115547 [details]
stacktrace
Comment 2 Tomas Hurka 2012-02-10 08:31:31 UTC
I need to see the heap dump to understand, what is going on. The only explanation I have right now is that  tid variable in java.lang.Thread is int instead of long, which looks strange, but maybe this is in heap dump from some exotic JVM.