There is no NetBeans code involved in the stacktrace, so it is probably not
problem of NetBeans. Can you try it in Notepad demo application which is bundled
in JDK, please?

You've hit a JDK issue
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4749220 so closing as invalid
since this cannot be fixed in the NB code.

This issue is not appear in NetBeans IDE 6.0 Preview (M9, build 070502). I 
don't know how it been fixed. Now I can type Chinese normally in 6.0M9 
with "Intelligent KuangPin IME(version 3.3)". The JDK is 1.6.0_01-b06 or 1.6.0-
b105.
But I can find a mass of Exception records in UI Gestures Collector. For 
example:
<record>
  <date>2007-05-08T16:43:54</date>
  <millis>1178613834218</millis>
  <sequence>1673</sequence>
  <level>SEVERE</level>
  <thread>12</thread>
  <exception>
    <message>java.lang.IllegalArgumentException: TextHitInfo is out of 
range</message>
    <frame>
      <class>java.awt.font.TextLayout</class>
      <method>checkTextHit</method>
      <line>753</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.font.TextLayout</class>
      <method>getCaretInfo</method>
      <line>1193</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.font.TextLayout</class>
      <method>getCaretInfo</method>
      <line>1295</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.CompositionArea</class>
      <method>getCaretRectangle</method>
      <line>104</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.CompositionArea</class>
      <method>paint</method>
      <line>126</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.CompositionArea</class>
      <method>setText</method>
      <line>207</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.CompositionAreaHandler</class>
      <method>inputMethodTextChanged</method>
      <line>204</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.CompositionAreaHandler</class>
      <method>processInputMethodEvent</method>
      <line>156</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>sun.awt.im.InputMethodContext</class>
      <method>dispatchEvent</method>
      <line>175</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.Component</class>
      <method>dispatchEventImpl</method>
      <line>4344</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.Container</class>
      <method>dispatchEventImpl</method>
      <line>2116</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.Component</class>
      <method>dispatchEvent</method>
      <line>4240</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventQueue</class>
      <method>dispatchEvent</method>
      <line>599</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>pumpOneEventForFilters</method>
      <line>273</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>pumpEventsForFilter</method>
      <line>183</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>pumpEventsForHierarchy</method>
      <line>173</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>pumpEvents</method>
      <line>168</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>pumpEvents</method>
      <line>160</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
    <frame>
      <class>java.awt.EventDispatchThread</class>
      <method>run</method>
      <line>121</line>
      <file>${java.home}lib/rt.jar</file>
    </frame>
  </exception>
</record>

Chinese:
这个问题在NetBeans IDE 6.0预览版(M9, build 070502)中没有再次出现。我不知道它是如何被修
理好的。现在，我能用“智能狂拼Ⅲ.3”输入法在6.0M9中正常录入汉字了。使用的JDK版本是
1.6.0_01-b06或1.6.0-b105。
但是，在“UI Gestures Collector”中，我却发现大量的异常记录，例如：

I run "D:\jdk1.6.0_01\demo\jfc\Notepad\Notepad.jar".
And then, I can type Chinese normally with "Intelligent KuangPin IME" in the 
demo application. But, at the same time, there are a mass of Exception records 
in the DOS console. For example: "Exception in thread "AWT-EventQueue-0" 
java.lang.IllegalArgumentException: TextHitInfo is out of range at 
java.awt.font.TextLayout.checkTextHit(TextLayout.java:753)".

So, in my opinion, indubitably, the issue is problem of JDK assuredly.

Chinese:
我运行了"D:\jdk1.6.0_01\demo\jfc\Notepad\Notepad.jar"，然后，我可以在这个演示程序中正
常地使用智能狂拼输入法录入汉字了。但是，与此同时，DOS控制台却输出了大量的异常信息，比如：
“Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: 
TextHitInfo is out of range at java.awt.font.TextLayout.checkTextHit
(TextLayout.java:753)”。
因此，我的结论是：毫无疑问，这个（智能狂拼的兼容性）问题确实是JDK的问题。

This issue is not appear in NetBeans IDE 5.5(chinese version), 5.5.1(chinese version),
6.0 Milestone9(english version) and 6.0 Milestone10(english version).
But it still appear in daily version(means not a milestone version and not a release version).
I can't use "Intelligent KuangPin IME(version 3.3)" in NetBeans IDE Dev 200707261200 and 200709050000.

Chinese:
这个（死循环报错）问题在NetBeans IDE 5.5中文版、5.5.1中文版、6.0M9英文版、6.0M10英文版中没有再次出现。
但是，它仍然出现在每日构造的版本里（我是指“非里程碑版本”与“非发布版”）。
我依旧无法在in NetBeans IDE Dev 200707261200与200709050000里正常使用“智能狂拼Ⅲ.3”输入法。

Do you used the same JDK version for running NetBeans?

Could you please attach the latest exception here or <userdir>/var/log/messages.log showing the exception? Do not
copy-paste it in the text field, but use 'Create a new attachement' link please. Thanks

Created attachment 48543 [details]
the messages.log of NetBeans IDE 6.0 Beta1 (build 200709101200)

Created attachment 48544 [details]
the new messages.log of NetBeans IDE 6.0 Beta1 (build 200709101200)

Created attachment 48550 [details]
the uigestures of NetBeans IDE 6.0 Beta1 (build 200709101200)

The first attachment(id=48543) is incorrect and useless. It should be removed.
The second attachment(id=48544) is useful. It contain the exception message(java.lang.IllegalArgumentException: 
TextHitInfo is out of range).

This is strange. The only thing that could explain this behavior is that dev (daily) builds report more exceptions than
milestones or releases. So, in fact in a milestone many exceptions may end up in a log file but are not shown to a user.
This really is JDK issue, because there is no Netbeans code in the stacktraces you attached. Please check with the
official release of beta1 (comparing to daily builds from release60_beta1 branch) and reopen if the exception is shown
to the user. Thanks.

Liujiaguang,

what platform, os and locale are you rinning netbeans in ?

and does this happen only in editor or in other windows of netbeans ?

ken.frank@sun.com

Ken Frank,

System Info: 
  Product Version         = NetBeans IDE Dev (Build 200709101200)
  Operating System        = Windows 2000 version 5.0 running on x86 (Windoz 2000 Professional SP4, 5.0.2195)
  Java; VM; Vendor        = 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06; Sun Microsystems Inc.
  Java Home               = D:\jdk1.6.0_02\jre
  System Locale; Encoding = zh_CN (nb); GBK
  Home Directory          = C:\Documents and Settings\Administrator
  Current Directory       = D:\NetBeans6.0
  User Directory          = C:\Documents and Settings\Administrator\.netbeans\dev

This issue happen in any JTextComponent of NetBeans, including text editor and other windows. For example, a textfield
in dialog.

As soon as I use Intelligent KuangPin IME in dev (daily) builds, the Exception dialog box show immediately.
And then, because netbeans show the exception dialog again and again even after I click the [close] button,
So, I must kill netbeans IDE's process in Windows Task Manager.
Sometime the NetBeans IDE may crash(exit unexpectedly) by the issue.

I agree the opinion of vstejskal -- it's do en issue involving compatibility between the IME and JVM.

But, the issue don't affect earlier milestones or releases.
When I run D:\jdk1.6.0_02\demo\jfc\Notepad\Notepad.jar(or netbeans' milestones or releases) with Intelligent KuangPin
IME, the GUI is OK, whereas some exceptions been output to System.err(or log file) in background.
So, I need to find the way how to make dev (daily) builds report less exceptions and don't show the annoying exception
dialog!
I must wait for the official release of 6.0beta1? Why not we solve it in release60_beta1 branch?
=================================================
Chinese:
系统信息：
  产品版本：NetBeans IDE Dev (Build 200709101200)
  操作系统：Windows 2000 Professional SP4, 5.0.2195，x86型PC机
  Java虚拟机：Sun的1.6.0_02，Java HotSpot(TM) Client VM 1.6.0_02-b06
  Java Home：D:\jdk1.6.0_02\jre
  系统地区与编码：zh_CN (nb); GBK
  用户主目录：C:\Documents and Settings\Administrator
  NetBeans安装目录：D:\NetBeans6.0
  用户目录：C:\Documents and Settings\Administrator\.netbeans\dev

该问题存在于NetBeans的任何JTextComponent控件（及其子控件）中，包括文本编辑器和其它窗口，比如对话框的文本域中。

只要我在开发版的NetBeans中一使用智能狂拼输入法，出错提示对话框就会立即弹出来。
于是，由于即使我点击了“关闭”按钮，NetBeans还是会一次又一次地弹出那个出错提示对话框，
因此，我不得不在Windos的任务管理器中杀死NetBeans IDE的进程。
有时，由于这个问题还会导致NetBeans IDE崩溃（无征兆地突然退出）。

我同意vstejskal的观点，即，这个问题确实是涉及到（狂拼）输入法与Java虚拟机(JVM)的兼容性问题。

但是，这个问题却并不影响以前的里程碑版本或发布版。
当我在运行D:\jdk1.6.0_02\demo\jfc\Notepad\Notepad.jar(或NetBeans的里程碑版本或发布版)时使用智能狂拼输入法，
图形用户界面(看起来)完全正常，尽管此时后台实际上有出错信息被输出到标准错误输出(System.err)(或日志文件)中了。
因此，我需要找到让开发版（每日构建版）输出更少错误信息的方便，不让那烦人的出错提示对话框出现！
我必须等官方的6.0beta1发布版么？我们为什么不在release60_beta1分支上就解决它？

Created attachment 48621 [details]
the Exception Dialog When Use Intelligent KuangPin IME

Created attachment 48622 [details]
Notepad.jar run with Intelligent KuangPin IME(output exceptions to System.err, but Swing GUI is OK)

Just correct a Chinese typing mistake.
更正一个中文打字错误：
因此，我需要找到让开发版（每日构建版）输出更少错误信息的方法，不让那烦人的出错提示对话框出现！

Could you please try running Netbeans with the following switch:

-J-Dglobal.level=1000

It should increase the logging level to Level.SEVERE, which means that anything below this level will not be logged. I'm
not sure about our policies for setting up logging in milestone or beta releases, but as you're saying that the dialog
didn't popup in previous milestones I believe it won't popup in 6.0beta1 either. The switch above should help with dev
builds. If it does not, please let me know and I'll try to find out more about it.

vstejskal,

Thank you for your advice.

I run NetBeans IDE using the command line: "D:\NetBeans6.0\bin\netbeans.exe -J-Dglobal.level=1000", it is not affect the
issue.
Then, I modify the file "D:\NetBeans6.0\etc\netbeans.conf", 
Replace the old netbeans_default_options:

    netbeans_default_options="-J-Dcom.sun.aas.installRoot=\"D:\glassfish-v2-b58g\" -J-client -J-Xms32m
-J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dnetbeans.logger.console=true -J-ea -J-Dapple.laf.useScreenMenuBar=true
-J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled"

with a new netbeans_default_options:

    netbeans_default_options="-J-Dglobal.level=1000 -J-Dcom.sun.aas.installRoot=\"D:\glassfish-v2-b58g\" -J-client
-J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dnetbeans.logger.console=true -J-ea
-J-Dapple.laf.useScreenMenuBar=true -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled
-J-XX:+CMSPermGenSweepingEnabled"

I run NetBeans IDE and try use IME again, and find this is still not affect the issue.

But your advice give me a helpful idea!
I open the configure file of NetBeans IDE 5.5.1 Chinese version(Build 200704122300), it located at
"D:\netbeans-5.5.1\etc\netbeans.conf".
I copy the netbeans_default_options value of 5.5.1(Build 200704122300), then to paste to the one of 6.0Dev(Build
200709101200).
Now the netbeans_default_options in file "D:\NetBeans6.0\etc\netbeans.conf" look like blow:

    netbeans_default_options="-J-Xms32m -J-Xmx128m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none
-J-Dapple.laf.useScreenMenuBar=true"

Then I run NetBeans IDE 6.0Dev. OK! Now Intelligent KuangPin IME(version 3.3) work fine, just like it did in 5.5.1
Chinese version.

Then proceed to the next step, I try the different options combination. Finally, I find the key is "-J-ea"!
If I remove "-J-ea" from netbeans_default_options, NetBeans IDE 6.0Dev and 5.5.1Chinese version can work fine with the IME.
If only I add "-J-ea" to netbeans_default_options, NetBeans IDE 6.0Dev and 5.5.1Chinese version can't work with the IME.

I don't know the function of "-J-ea". Maybe it mean "Enable Assertions"?

I run "java -ea -jar D:\jdk1.6.0_02\demo\jfc\Notepad\Notepad.jar" in command line, the Swing application still work fine
with the IME.
What the statement "work fine" I said, its meaning is the GUI is run normal, don't popup any exception dialog, but the
exceptions is output to System.err or log file backgroud.

By the way, the issue imply a bug exist in either Swing API or Intelligent KuangPin IME.
===========================
Chinese:
谢谢你的建议。
我在命令行中使用"D:\NetBeans6.0\bin\netbeans.exe -J-Dglobal.level=1000"运行NetBeans IDE，这对这个（输入法兼容性）问题的
解决没有影响。
于是，我修改配置文件"D:\NetBeans6.0\etc\netbeans.conf"，
把原来的旧参数netbeans_default_options:

    netbeans_default_options="-J-Dcom.sun.aas.installRoot=\"D:\glassfish-v2-b58g\" -J-client -J-Xms32m
-J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dnetbeans.logger.console=true -J-ea -J-Dapple.laf.useScreenMenuBar=true
-J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled"

替换为新参数:

    netbeans_default_options="-J-Dglobal.level=1000 -J-Dcom.sun.aas.installRoot=\"D:\glassfish-v2-b58g\" -J-client
-J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dnetbeans.logger.console=true -J-ea
-J-Dapple.laf.useScreenMenuBar=true -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled
-J-XX:+CMSPermGenSweepingEnabled"

在再次运行NetBeans IDE并试用狂拼输入法，发现这对问题的解决依旧没由影响。

但是，你的建议给了我有用的想法！
我打开NetBeans IDE 5.5.1中文版(Build 200704122300)的配置文件，它位于"D:\netbeans-5.5.1\etc\netbeans.conf"。
我把5.5.1(Build 200704122300)的netbeans_default_options参数值复制一下，然后在6.0Dev(Build 200709101200)的配置中粘贴一下，
现在，"D:\NetBeans6.0\etc\netbeans.conf"的netbeans_default_options看起来象下面这样：

    netbeans_default_options="-J-Xms32m -J-Xmx128m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none
-J-Dapple.laf.useScreenMenuBar=true"

于是我又运行NetBeans IDE 6.0Dev。太好啦！现在智能狂拼III.3输入法可以正常使用了，就像在5.5.1中文版时一样。

我再更进一步，尝试不同参数的组合，最后，我发现问题的关键是“-J-ea”!
如果我从netbeans_default_options里删除"-J-ea"，NetBeans IDE 6.0Dev与5.5.1中文版就能与输入法工作正常。
一旦我在netbeans_default_options里添加"-J-ea"，NetBeans IDE 6.0Dev与5.5.1中文版就不能与输入法一同工作。

我不知道"-J-ea"是起什么作用的，难道它是指“启用断言”(Enable Assertions)？

我在命令行里执行"java -ea -jar D:\jdk1.6.0_02\demo\jfc\Notepad\Notepad.jar"，这个Swing程序仍然能正常地与狂拼输入法一同工作。
我所说的正常工作(work fine)，是指图形用户界面(GUI)正常运行，不弹出任何出错提示对话框，但是出错信息依然会在后天输出到标准
错误输出(System.err)或日志文件里。

此外，这个问题也暗示着，要么是Swing API要么是智能狂拼输入法，一定有一个是存在缺陷(bug)的。

Excellent!! Good work. I'm glad that the dev versions work fine for you now.

Today, I download and run the NetBeans IDE Beta 1(Build 200709141330, English version). There is not include "-J-ea" in
the default value of netbeans_default_options. So I can use Intelligent KuangPin IME v3.3 normally without any
modification of launcher options.
Some exceptions(e.g.: java.lang.IllegalArgumentException: TextHitInfo is out of range) were written to the log file, but
they don't disturb me anymore.

NetBeans IDE -- it is a good thing.

Chinese:
今天，我下载并运行了NetBeans IDE 6.0 Beta 1(Build 200709141330，英文版)，它的netbeans_default_options默认值中没有包含“-J
-ea”，因此我不用修改任何参数就可以正常使用智能狂拼Ⅲ.3输入法了。
一些异常(比如：java.lang.IllegalArgumentException: TextHitInfo is out of range)会写入日志文件，但这已不再妨碍我了。

NetBeans IDE——好东西。