X3 not giving back memory

[bigfatron]

Another minor update. The techs are now working on the issue but the time frame for a fix/patch isn't known at this point.

[JONE5]

So I'm not on my own then. Really annoying when working with multiple images, cutting pasting etc only to find that you can't save all the hard work as it states not enough memory. Also very slow when carrying out commands such as resizing or pick and move object. I know there were problems with graphics card conflicts on PSPX2, and thought the same was going on here. Was on the verge of upgrading just to get more memory, but sounds as though it wouldn't work anyway.....

[bigfatron]

So I'm not on my own then. Really annoying when working with multiple images, cutting pasting etc only to find that you can't save all the hard work as it states not enough memory. Also very slow when carrying out commands such as resizing or pick and move object. I know there were problems with graphics card conflicts on PSPX2, and thought the same was going on here. Was on the verge of upgrading just to get more memory, but sounds as though it wouldn't work anyway.....

No. As things stand you're better off sticking with X2 for working with multiple large images (I have X2 and X3 installed but use X2 most of the time at the moment).

I haven't had a chance to download and check but it sounds very much like any fix for this issue didn't make the second and most recent patch unfortunately.

[Rob717]

I have seen the same issue

It would be nice if they have more memory control in the program or even an option to clear the memory in the menu options some where, kind of like a workspace reset without having to exit the program.

Or they could just fix the memory issue where such a tool is not needed.

[LeviFiction]

They're working on it. It has been reported, and submitted to the engineers. They will fix it when they can. It's not necessarily as simple as changing a variable at the right time. Depending on what's actually going wrong it may be ready by the next patch, it may not. But it will be fixed.

[bigfatron]

They're working on it. It has been reported, and submitted to the engineers. They will fix it when they can. It's not necessarily as simple as changing a variable at the right time. Depending on what's actually going wrong it may be ready by the next patch, it may not. But it will be fixed.

Yes, given the timescales it was reported that i'm aware of then it would've been pretty tight for it to have made it through any testing and into the patch thats just come out. Hopefully the next one isn't too far away anyway.

[grafxman1]

They're working on it. It has been reported, and submitted to the engineers. They will fix it when they can. It's not necessarily as simple as changing a variable at the right time. Depending on what's actually going wrong it may be ready by the next patch, it may not. But it will be fixed.

Yes, given the timescales it was reported that i'm aware of then it would've been pretty tight for it to have made it through any testing and into the patch thats just come out. Hopefully the next one isn't too far away anyway.

This problem is driving me crazy. I have a huge number of photos to process and I am constantly having to close and restart X3. X2 won't open the CR2 images from my Canon 7D or else I would use it. The issue was first reported 4 months ago and the last posting is 2 months ago. X3 tells me no updates are available. Have I missed something? Is there a solution?


http://www.flickr.com/photos/80431173@N00/

[LeviFiction]

We're still waiting for a patch. The problem with being on this side of the issue is we have no idea what is required to get it fixed. We would like to think it's easy for those who made the software but the more complicated the software the harder it is to find where all of the problems are. Some problems are related to each other, fix one and fix a few. Others are problems where something works because something else is broken. Fix that issue and the other function breaks.

I realize it's annoying but they got themselves into this mess. And it's a big mess. So it's not going to be quickly fixed.

On the other hand the issue may be solved by now but they want to fix lots of other issues and update them all in one big patch rather than releasing patches each time they solve an issue. Fact is we just don't know. So I called Corel and on the report that I filed over the phone they had no markups or updates listed. But that doesn't mean anything. They may have updated the one submitted by Simone. But you'd have to ask her directly.

Till then my suggestion would be just put up with it until they get the patch out. However far away that may be. They've been telling us since the beginning of Summer that a third patch is planned and on the way. How long? I couldn't say.

[grafxman1]

Thanks for the feedback LeviFiction. Right now I am wondering if there is another comparable software solution for a reasonable price. I've been using Corel products since CorelDraw 2.1 but this is impacting my time and money. That's just plain unacceptable. Waiting four months for a fix to a problem this serious is also unacceptable.




http://www.flickr.com/photos/80431173@N00/

[Simone Corel UK]

Hi to all

I have no information when (and if) this problem will be solved. The only thing I had done was to make sure that the DevTeam became aware of the problem. The last news I got was that they are generally working on the problem that PSPPX3 takes plenty of memory.

Simone

[grafxman1]

FWIW I drilled through all the posts and I saw one post that mentioned turning off autosave. I did that and I'm now able to process about 3 dozen photos before having to restart X3. That's a whole lot better than having to restart every eight to ten photos. However, it's still unacceptable.

http://www.flickr.com/photos/80431173@N00/

[grafxman1]

Hi to all

I have no information when (and if) this problem will be solved. The only thing I had done was to make sure that the DevTeam became aware of the problem. The last news I got was that they are generally working on the problem that PSPPX3 takes plenty of memory.

Simone

Hi Simone,

I thought I would respond to your posting separately. I don't find that X3 takes very much memory at all. When it was constantly crashing for me before I turned off autosave I monitored the memory levels and the amount of memory X3 used. I used the task manager and X3 would go up to about 1.1 or 1.2 GB of memory then crash. I did not go onto to the net and I closed every single application that was running that windows would let me close. I even used taskinfo to flush out all the memory and I got down to under 1 GB of memory used. It made no difference whatsoever.

I'm running Windows 7 Pro 64 bit with 8 GB. I realize the 4GB limitations of 32 bit apps. My point is that X3 always crashed when a certain memory point was consumed even though a couple more GB was available. It's as if the software was deliberately engineered to crash when it used a certain amount of memory even though there is still plenty of memory available. It doesn't seem to check for any available memory that might be utilized. I'm not a programmer or engineer that doesn't make much sense to to me. I guess there's a lot I don't know about software. On the other hand, I seem to remember some memory intensive apps years ago writing to and off of the hard drive when the memory started running out.

[Simone Corel UK]

@ grafxman1

You are right: PSPP doesn't use more than max. 2 GB of RAM. I noticed it while testing that memory thing: it stops at about 1.7 GB. I tested it on a Win7 64bit (with 8GB RAM) and XP 32-bit with 3 GB RAM and there was no difference.

[bigfatron]

@ grafxman1

You are right: PSPP doesn't use more than max. 2 GB of RAM. I noticed it while testing that memory thing: it stops at about 1.7 GB. I tested it on a Win7 64bit (with 8GB RAM) and XP 32-bit with 3 GB RAM and there was no difference.

Allow me to clarify. Although the 32 bit address space is 4GB, because of how Windows works then in reality for most 32 bit programs a single process typically cannot use itself more than the 2GB allocated per process to 'user mode' memory. The other 2GB is reserved for the system kernel. This applies to both 32 bit Windows and most 32 bit processes running under Windows 64 (you can get up to 3GB user mode memory under Win64 but the program has to be written to support this). So in other words, it falling flatly on its arse at 2GB+ is entirely expected behaviour.

And I am also growing a bit impatient about this issue now too. It really shouldn't be that hard to fix, should be a relative priority (of course i'd say that!) and its worth reiterating that X2 does not suffer this issue AND X3 used in batch script processing mode on multiple images somehow doesn't suffer the same problem either. Yes, general memory usage for X3 is slightly higher than X2 was. The problem here though is seemingly memory not being released when its no longer required.

[LeviFiction]

I'm sorry, I can't agree that it "should" be a relatively easy fix. Without actually looking at the code and going through it, everything is hearsay. And that's not a good thing to consider if it's only going to start upsetting you. As for it not being a problem with batch processing, this again means nothing without knowing how it interacts with the program. Making a few assumptions we can assume that how resources are allocated and changed in the full editor is apparently different so it does narrow down the search but doesn't necessarily make it easier.

Also as much of a priority as it should be, and I do agree with you there, if it's already fixed but not had its status updated then it's waiting for the other patches to continue. If it's not fixed then it's probably more difficult than you're assuming.

All in all it makes no sense to continue to get frustrated about the unknown. If the third patch comes out and this still isn't fixed, then please feel free to unload on these people because even if the memory leak problem here is a hard fix there is no reason, beyond pressure from the company, for them to take this long on the third patch and then release the patch without a fix for this.

I would rather wait another two months then get another patch without a fix for this problem. Even though it doesn't really effect me, I'm not a photographer, I only do photo edits and that doesn't require opening, editing, and saving multiple files. Especially not multiple large files.