Closed GoogleCodeExporter closed 9 years ago
This has never been reported before, nor have I noticed any problems with any
specific version, so it is most likely a problem with something installed on
your end. Do you have any haxies or similar installed?
Original comment by paracel...@gmail.com
on 9 Apr 2012 at 7:53
That was fast. Not really. If it's something on my end, is there any way to
check what causes this?
Original comment by korparda...@gmail.com
on 9 Apr 2012 at 8:03
Not easily. If you can find a second machine and find out whether the same
thing happens there or not, that might help. There's also the "leaks" command
that will give you some information about what is leaking memory, but it might
not be enough.
Original comment by paracel...@gmail.com
on 9 Apr 2012 at 8:23
I have the same issue - again latest version of Lion and an early 2011 MacBook
Pro 13". Any new suggestions?
Original comment by Mask...@gmail.com
on 13 May 2012 at 11:51
Same for me; scrolling through photos rapidly eats into RAM (MBP 13.3, early
2011). It doesn't take long before I need to quit Xee and reopen.
Original comment by arron.fi...@gmail.com
on 18 May 2012 at 12:45
Should also say that I'm running Lion 10.7.4 and Xee 2.2.
Original comment by arron.fi...@gmail.com
on 18 May 2012 at 12:46
Issue 291 has been merged into this issue.
Original comment by paracel...@gmail.com
on 20 May 2012 at 7:32
I have the same issue... Any suggestions?
Original comment by maxsthom...@gmail.com
on 22 May 2012 at 7:53
I've tested this issue on two separate computers with the same outcome. On one
machine (late 2011 mbp 13") after the system is out of ram (it has 8gb
installed), Xee crashes. If needed, I can attach crash log.
Original comment by thepeg...@gmail.com
on 14 Jun 2012 at 4:14
Well, this is unlikely to get fixed in the current codebase anyway. I don't
think any more development will happen on it. I am playing around with a fresh
new rewrite for v3.0, to catch up with everything that's changed in OS X in the
meanwhile. It will probably not have the same bug any more.
If anyone wants to fix this in the current codebase, though, I am happy to
accept patches.
Original comment by paracel...@gmail.com
on 14 Jun 2012 at 5:45
Thanks for the response! It's great to know that work's being done on the new
version.
It's fast, light-weight and just what I need to simply browse through large
quantities of images.
Is there a date (approximation maybe?) for the release or betas of 3.0?
Original comment by thepeg...@gmail.com
on 15 Jun 2012 at 7:17
Not really, since I am working on it in my spare time and still just
experimenting with what works fast and what doesn't on new versions of OS X.
Original comment by paracel...@gmail.com
on 15 Jun 2012 at 12:57
Issue 294 has been merged into this issue.
Original comment by paracel...@gmail.com
on 16 Jun 2012 at 1:28
Issue 285 has been merged into this issue.
Original comment by paracel...@gmail.com
on 16 Jun 2012 at 1:30
Same here, Mac Pro 13" late 2011...
It really nice app but this memory leak is annoying
Original comment by ShiFtyS...@gmail.com
on 15 Jul 2012 at 9:07
I've downloaded Xee 2.2 (in a Lion 10.7.4) and I had the same problem reported
here. The system run out of memory and restarted with a system error.
I have noticed that the memory consumption increase with every picture I see.
Original comment by jzarzuela
on 22 Jul 2012 at 10:32
[deleted comment]
Macbook pro 13, 8gb, same problem. It annoys a lot. Anyone has an idea of how
to fix it? I'm a programmer, maybe I could create a patch with some help.
Original comment by anton.ca...@gmail.com
on 1 Aug 2012 at 9:11
Try to figure out if it happens for all images, or just for certain kinds. Then
you can track down which image loader class is causing it.
Also, "leaks Xee" in the terminal might help, maybe. Unless it's something more
complicated.
Original comment by paracel...@gmail.com
on 1 Aug 2012 at 9:22
Yup, same here. Xee 2.2, Mac Pro 13''
My Xee crashes regularly when browsing through new photos downloaded from a
camera. Looks like something is trying to capture the image in something more
than just the immediate memory as the problem occurs less frequently once
images have been opened once. Crashes typically occur when browsing from one
image to the next. The Mac rainbow icon appears, hangs for a while and bang,
that's it.
Other than this, I like the app which is quite similar to Irfanview, in some
respects better but not yet fully so.
Original comment by wak...@aidenvironment.org
on 9 Oct 2012 at 12:23
I assume it caused by 8g memory.
Original comment by qteveryw...@gmail.com
on 9 Oct 2012 at 2:59
No, it's not caused by memory. I sold my mbp that had 4 gigs of memory where I
had the problem and bought the latest 13" air with 8 gigs of memory and
everythig works perfectly. Thanks God I don't have that problem anymore...
Original comment by korparda...@gmail.com
on 9 Oct 2012 at 5:29
Same problem. Opening 18MPixel images results in ~70MB RAM for each image
browsed. Memory used for viewing an image is only released after the window is
closed.
Program consumes all memory available after a few images.
MBP 13", Mountain Lion, Xee 2.2
Original comment by jpbarr...@gmail.com
on 20 Oct 2012 at 9:48
Issue 315 has been merged into this issue.
Original comment by paracel...@gmail.com
on 27 Nov 2012 at 11:38
I am having the same issue using Xee 2.2 with Macbook Pro Late 2011 8GB RAM and
running Mountain Lion v 10.8.2. I was viewing a set of around 200 pics
yesterday and my available memory went down from around 5.5 GB to 20 MB at
which point the OS became very laggy and I realised the issue. I was able to
replicate it again and again
Original comment by nikhles...@gmail.com
on 27 Nov 2012 at 4:50
Issue 319 has been merged into this issue.
Original comment by paracel...@gmail.com
on 26 Jan 2013 at 12:41
There's a 3.0 beta now, so I'll close this.
Original comment by paracel...@gmail.com
on 10 Mar 2013 at 1:12
Original issue reported on code.google.com by
korparda...@gmail.com
on 9 Apr 2012 at 7:49