Eclipse启动错误：与FlashGet冲突

作者：JBossWeek http://blog.csdn.net/JBossweek email：jbossweek AT gmail.com 版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息

今天上午突然发现Eclipse启动不了，错误画面如下：

 

这个Eclipse版本我已经使用一段时间了，一直都很正常。怎么回事，折腾了大半个上午，终于发现只要先启动了FlashGet程序，再启动Eclipse就会出现这个问题。Eclipse和FlashGet的版本如下：

Eclipse：3.3.1.1 Build id: M20071023-1652

FlashGet：1.9.6.1073

对于这个问题目前有两个解决方法：

1. 启动Eclipse之前先关闭FlashGet
2. 增加启动参数-vm %JAVA_HOME%/jre/bin/javaw.exe

问题暂时解决了，但是还有两个问题没有彻底弄明白：

1. 为什么Elicpse和FlashGet会冲突？
2. 为什么java虚拟机切换到javaw.exe就不会出现Eclipse和FlashGet冲突？java.exe和javaw.exe到底有什么区别？

不知哪位高手能够帮着解释清楚呢？

下面可能是其中原因之一：

The reason we need a contiguous memory region for the heap is that we have a bunch of side data structures that are indexed by (scaled) offsets from the start of the heap. For example, we track object reference updates with a "card mark array" that has one byte for each 512 bytes of heap. When we store a reference in the heap we have to mark the corresponding byte in the card mark array. We right shift the destination address of the store and use that to index the card mark array. Fun addressing arithmetic games you can't do in Java that you get to (have to :-) play in C++.

Usually we don't have trouble getting modest contiguous regions (up to about 1.5GB on Windohs, up to about 3.8GB on Solaris. YMMV.). On Windohs, the problem is mostly that there are some libraries that get loaded before the JVM starts up that break up the address space. Using the /3GB switch won't rebase those libraries, so they are still a problem for us.

We know how to make chunked heaps, but there would be some overhead to using them. We have more requests for faster storage management than we do for larger heaps in the 32-bit JVM. If you really want large heaps, switch to the 64-bit JVM. We still need contiguous memory, but it's much easier to get in a 64-bit address space.