vijaymoorthy001 / xmind3

Automatically exported from code.google.com/p/xmind3
0 stars 0 forks source link

Constant raise of used memory #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use the software several hours on a project, adding and deleting items

What is the expected output? What do you see instead?
When you are using the software a long time, the memory used grows
dramatically. After a moment it can be more than 200 or 300MB. If you close
the program and reopen the file it uses only 80MB ...

What version of the product are you using? On what operating system?
XMind 3.0 on Windows Vista Professionel SP1

Please provide any additional information below.
As a programmer, I see two possibilities for this problem :
 * some memory isn't free, maybe a bug caused by eclipse ?
 * the undo/redo tree takes too many place

Good luck :)

Original issue reported on code.google.com by scham...@gmail.com on 19 Nov 2008 at 8:09

GoogleCodeExporter commented 9 years ago
I am running Windows XP Professional SP2.  I have tried both the Eclipse plugin 
and
the standalone executable of XMind 3 (downloaded a couple days ago).  In both 
cases I
see there is clearly a resource leak.  I simply open  XMind with a map.  I then 
place
another app's window in front of XMind and move it around.  As XMind re-draws 
its
content you can see the memory usage climb steadily in the Windows task 
manager. 
After a short time XMind displays an error saying there are no more free 
handles.

Original comment by glow...@gmail.com on 9 Dec 2008 at 4:09

GoogleCodeExporter commented 9 years ago
I got the same problem too... i think it's connected to the "save" function... 
if you
save your document you can see a memory raise from ~80mb to ~200mb... same with 
the
next "save"

Original comment by Scheinku...@googlemail.com on 16 Dec 2008 at 2:53

GoogleCodeExporter commented 9 years ago

Original comment by frankshaka on 24 Dec 2008 at 8:42

GoogleCodeExporter commented 9 years ago
Issue 7 has been merged into this issue.

Original comment by frankshaka on 24 Dec 2008 at 8:47

GoogleCodeExporter commented 9 years ago
I am running in WinXP Professional SP3.I have same issue.
My Xmind Version is V3.0.1 Standalon
When I edit fishbone diagram ,memory use about ~1GB in short time. It is 
terrible.

Original comment by java.jav...@gmail.com on 26 Dec 2008 at 1:56

GoogleCodeExporter commented 9 years ago
I found the problem to be worst when editing fish bone diagrams with a lot of 
relationships. I find 3.0.1 still 
has the problem, but it no longer crashes and prevents me from saving. Now it 
starts failing to draw all the 
elements, but I can still save (which is obviously great).  While it is still 
an issue I don't find it too hard to quit 
and restart periodically now that I don't worry about losing my changes. 

I downloaded the source code last week thinking to debut the issue in Eclipse, 
but the sources didn't seem 
to be up-to-date and I hsd to give up. 

Original comment by glow...@gmail.com on 27 Dec 2008 at 12:24

GoogleCodeExporter commented 9 years ago
There is an easy way to repro this. Right click on a node and start draging it 
around, watch the process grow by 12Megs at a time in Task manager in about 30 
seconds the application will be 1Gb

Original comment by danr...@gmail.com on 9 Jan 2009 at 10:03

GoogleCodeExporter commented 9 years ago
It seems to be a windows only problem.
I can not verify it on Mac OSX 10.5.6 with Java 1.5.0_16-133 only on win xp sp3 
with Java 1.6.0 latest.
What  about Linux? Are there any users with Linux to verify this?

On windows dragging the map raises memory usage really fast but not if you use 
the scrollbars to move the 
map.

Original comment by mobang...@gmail.com on 10 Jan 2009 at 12:06

GoogleCodeExporter commented 9 years ago
Happens for me in Vista Ultimate 64bit by just opening and collapsing a node 
with 16 
children which have children of their own.

Original comment by tmil...@gmail.com on 6 Feb 2009 at 11:26

GoogleCodeExporter commented 9 years ago
Debian, standalone version: moving nodes around, collapsing and expanding 
subtrees,
and also opening and closing the woorkbook is free. Saving, however, increases 
the
memory consumption with some 10 MB.

Original comment by choma...@gmail.com on 19 Feb 2009 at 7:30

GoogleCodeExporter commented 9 years ago
Hey guys, we'd like to inquire EXACTLY the JRE version you're using on which 
XMind runs and 
crashes/slows/drains memory. You may find this information in XMind: Help menu 
-> About XMind -> 
Configuration Details. If you fail to find it or don't know what to find, 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:26

GoogleCodeExporter commented 9 years ago
I tried to get the Configuration Details, but clicking the button didn't do 
anything.
 But I am pretty sure I am running jdk1.6.0_11 (I have forced my PATH to have that
first before starting xmind from the command line, and I also added a -vm 
option in
the xmind.ini file to try to be sure this was the jdk being used).

Original comment by glow...@gmail.com on 11 Mar 2009 at 4:25

GoogleCodeExporter commented 9 years ago
I'm using Windows XP with SP3. Tested the XMind 3.0.1 memory leak issue with 
several
configurations:

Stand alone with JRE 1.6.0 update 12: memory leak
Portable ZIP with included JRE 1.6.0 update 10: memory leak
Stand alone with JRE 1.6.0 update 10: memory leak
Stand alone with JRE 1.6.0 update 7: memory leak (tested because there was a 
big step
between update 7 and 10)
Stand alone with JRE 1.5.0 update 17: memory leak

It seems that using Windows XMind has a serious memory leak no matter which SUN 
JRE
version is installed.

Perhaps the developers are not able to reproduce the problem as they are using 
MACs?
Maybe the MAC version of JRE can garbage collect something of the redraw 
procedure to
which the Windows version still has a handle to.

Original comment by andre.st...@gmail.com on 13 Mar 2009 at 10:39

GoogleCodeExporter commented 9 years ago
Another user of JRE 1.6.0-12 experiencing the leak:

java.runtime.version=1.6.0_12-b04
java.version=1.6.0_12
java.vm.version=11.2-b01

Original comment by ben.bea...@gmail.com on 18 Mar 2009 at 1:08

GoogleCodeExporter commented 9 years ago
I have the same problem, whatever events i am doing, the amount of memory is 
growing 
from 80Mo up to more than 1,5Go.
When I close eclipse and reopen the memory usage restart from 80 Mo.
It is very problematic for an intensive work !!!!

My configuration WindowsXP; Eclipse ganimede; Sun JRE 1.6.0
Please make it a high priority

Original comment by lebenoit...@gmail.com on 20 Mar 2009 at 7:45

GoogleCodeExporter commented 9 years ago
Ok I have a update.

Now using Windows XP Pro x64
java.version=1.6.0_12

and the Memory is still rising.

But very interesting in 32bit Windows XP with Java 1.6.0_11 the memory usage 
was not 
rising by using the scrollbars to move around. That is now also rising memory 
usage.

Original comment by mobang...@gmail.com on 26 Mar 2009 at 8:44

GoogleCodeExporter commented 9 years ago
I can't confirm your statement, just installed Java 1.6.0_11 using Win XP but 
the
memory leak still occurs. I installed the new Java 1.6.0_13, too: memory leak.
Afterwards I installed the new XMind 3.0.2: memory leak. Annoying :-(

Original comment by andre.st...@gmail.com on 28 Mar 2009 at 6:02

GoogleCodeExporter commented 9 years ago
I have the same problem with Windows Vista professional SP1. Does anyone know if
there is a solution for this problem?

Thanks

Original comment by daniel.s...@gmail.com on 15 Apr 2009 at 1:51

GoogleCodeExporter commented 9 years ago
Good news. We have finally figured out the cause of the 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:30

GoogleCodeExporter commented 9 years ago
Issue 36 has been merged into this issue.

Original comment by frankshaka on 26 Apr 2009 at 1:42

GoogleCodeExporter commented 9 years ago
Issue 37 has been merged into this issue.

Original comment by frankshaka on 26 Apr 2009 at 1:42

GoogleCodeExporter commented 9 years ago
I've been using XMind 3.0.3 on WinXP heavily for the past week and have not 
suffered 
from Memory Leaks like previously. Memory usage averages around 150MB. Thanks 
for 
identifying the bug. Will you be working to reduce memory usage in the future?

Original comment by james.f....@gmail.com on 18 May 2009 at 11:43