Closed GoogleCodeExporter closed 9 years ago
What's the JRE version?
Original comment by frankshaka
on 6 Mar 2009 at 10:11
You may find this information in XMind: Help menu -> About XMind ->
Configuration Details. If you fail to find
it, just copy-paste the whole text here, or upload it as a txt file. Thanks!
Original comment by frankshaka
on 6 Mar 2009 at 10:22
here infos you may search
-------------
java.runtime.version=1.6.0_11-b03
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_11
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Client VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=11.0-b16
---------------------------
Hope it will help
Original comment by nicolas....@gmail.com
on 7 Mar 2009 at 9:43
Same memory issue here ...
----------------------------------
java.runtime.name=Java(TM) SE Runtime Environment
java.runtime.version=1.6.0_12-b04
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.6
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.6.0_12
java.vm.info=mixed mode, sharing
java.vm.name=Java HotSpot(TM) Client VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=11.2-b01
------------------------------------
on Windows XP Professional
Original comment by c7n...@gmail.com
on 9 Mar 2009 at 12:05
Good news. We have finally figured out the cause of this kind of problem, and
you're
expected to see the bug fixed in next release. Thanks to all of you that have
taken care!
Original comment by frankshaka
on 26 Apr 2009 at 1:42
Original issue reported on code.google.com by
nicolas....@gmail.com
on 2 Mar 2009 at 9:58