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 227915 - Netbeans IDE UI Frozen: Malformed floating point literal
Summary: Netbeans IDE UI Frozen: Malformed floating point literal
Status: RESOLVED INVALID
Alias: None
Product: contrib
Classification: Unclassified
Component: Other (show other bugs)
Version: 7.2.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@contrib
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-25 16:49 UTC by mark_barnes
Modified: 2013-03-27 20:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (142.80 KB, application/octet-stream)
2013-03-25 16:49 UTC, mark_barnes
Details
uigestures file (115.34 KB, application/octet-stream)
2013-03-25 16:51 UTC, mark_barnes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mark_barnes 2013-03-25 16:49:40 UTC
Created attachment 133045 [details]
messages.log

Windows 7 Pro 64-bit
JDK 1.7.0_17 64-bit.

I was typing along in the Java jVI editor when the entire Netbeans UI froze.  It's absolutely unresponsive.  I see the message "malformed floating point literal" on the status line.  I assume I've lost my edits.

When I look at the Windows Resource Monitor I see that netbeans64.exe has CPU at around 15%. My system has two quad-core Xeons and 16 gig.  15% of that is quite a bit for doing nothing.

I cannot readily reproduce this, unfortunately.
Comment 1 mark_barnes 2013-03-25 16:51:11 UTC
Created attachment 133046 [details]
uigestures file
Comment 2 Tomas Danek 2013-03-26 12:25:19 UTC
please report this bug to jVI (https://sourceforge.net/projects/jvi/). 
Hint: Thread dump seems to be necessary to evaluate why was UI frozen (http://wiki.netbeans.org/GenerateThreadDump).
Comment 3 mark_barnes 2013-03-26 14:42:50 UTC
When I submitted this report I figured it probably wouldn't help much because I can't provide a repro scenario.  I was following what I thought were the guidelines for submitting a bug, and they didn't tell me about the thread dump or how to get one. Maybe this info should be added there?

When the problem occurred it was too late.  There was no way to get a thread dump.  I was not running from a console.

I will see if I can add "--console new" to the shortcut for the future.
Comment 4 Jan Lahoda 2013-03-27 20:14:39 UTC
(In reply to comment #3)
> When I submitted this report I figured it probably wouldn't help much because I
> can't provide a repro scenario.  I was following what I thought were the
> guidelines for submitting a bug, and they didn't tell me about the thread dump
> or how to get one. Maybe this info should be added there?
> 
> When the problem occurred it was too late.  There was no way to get a thread
> dump.  I was not running from a console.

FWIW, the thread dump can be generated using jstack or VisualVM even without having the console - see:
http://wiki.netbeans.org/GenerateThreadDump#jps_.26_jstack_Tools
(for jstack)
and:
http://wiki.netbeans.org/GenerateThreadDump#VisualVM
(for VisualVM)