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 219889 - IllegalStateException: Current state = FLUSHED, new state = CODING_END
Summary: IllegalStateException: Current state = FLUSHED, new state = CODING_END
Status: RESOLVED DUPLICATE of bug 219467
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
: 219891 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-10-11 08:14 UTC by Alexander Simon
Modified: 2012-11-06 16:08 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 193382

Attachments
stacktrace (4.97 KB, text/plain)
2012-10-11 08:14 UTC, Alexander Simon 		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 Alexander Simon 2012-10-11 08:14:52 UTC 
Build: NetBeans IDE Dev (Build 20121010-4f4577f2b675)
VM: Java HotSpot(TM) Client VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b05
OS: SunOS

Stacktrace: 
java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END
   at java.nio.charset.CharsetEncoder.throwIllegalStateException(CharsetEncoder.java:968)
   at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:554)
   at org.netbeans.api.queries.FileEncodingQuery$ProxyCharset$ProxyEncoder.implFlush(FileEncodingQuery.java:432)
   at java.nio.charset.CharsetEncoder.flush(CharsetEncoder.java:650)
   at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:786)
   at java.nio.charset.CharsetEncoder.canEncode(CharsetEncoder.java:892)
Comment 1 Alexander Simon 2012-10-11 08:14:58 UTC 
Created attachment 125756 [details]
stacktrace
Comment 2 Antonin Nebuzelsky 2012-10-11 09:02:27 UTC 
*** Bug 219891 has been marked as a duplicate of this bug. ***
Comment 3 Ondrej Vrabec 2012-11-06 16:08:55 UTC 

*** This bug has been marked as a duplicate of bug 219467 ***