X3 not giving back memory

[grafxman1]

I doubt that they're even working on it. Since X3 has been on the market for quite a while now, I suspect they are more likely than not working on getting X4 out the door. They'll make money selling a new software package. They won't make any money on a patch.

[LeviFiction]

First, let's focus on what little is known. Speculation is good for nothing more than rumor mongering.

Second, as far as I and the people I've spoken to at Corel know, a patch is still planned. As of my last reply to you specifically I was assured that a patch was planned and being worked on. Admittedly this could have changed since then but it's again what little we know about the situation.

Third, there's a problem with your reasoning. You make more money on something you can sell, this is true. But you make less money by disappointing your more devoted users. In many cases upgrades are more profitable than full purchases. By forcing users to buy a whole new version to get what should have been done originally you lose your good standing in the eyes of your users. And users are a big part of how Corel sells Paint Shop Pro. Because in today's world it's not difficult at all to look up information on a piece of software before buying. If Corel's previous users say the product is good but the support and the company are not many will be far more likely to stay away.

So attempting to keep the users happy is a big part of producing software especially in an age where cheap alternatives are not hard to come by. It's hard to sell a $100 piece of software when something for $30 or even $10 will do just fine for many. Some are more than willing to just take what free software like Picasa offers them. So you do a better job maintaining your current customers than chasing them away with bad business practices.

So it is actually in Corel's best interest to patch X3 sufficiently before working on X4 which sill probably will not offer that much more, but that's mere speculation. Does that mean they'll consider this? No, but it's far more likely.

In all honesty the use of X3 Ultimate offers a chance for them to continue work on X3 and get X4 out the door next year. Sort of a delay tactic for those who have gotten use to 1 to 2 year upgrade release dates.

[bigfatron]

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.

Yes i'm speculating to a certain extent but i'm speculating from the viewpoint of a programmer who has worked as such for about 15 years. If I was saying "is a relatively easy fix" then I take your point. As I am making some assumptions (and I freely admit that) then hence i'm saying "should" instead. If you compare this version with X2 then its not unreasonable to surmise that they haven't rewritten X3 from scratch either. This is also something that really should've been spotted in testing pre-release.

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.

Upsetting isn't the right term, as i've said before i'm working around it anyway. Its merely slightly frustrating and I see no harm in giving a "gee-up" every once in a while.

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.

From occasional direct correspondence i'm still having with Simone then it doesn't sound like they've licked it yet, no. And yes, it may well be part of a wider fix that is ongoing. As I said, i'm mainly just giving a little reminder. And you'll probably note that i've updated my posts on this issue very little since Simone took the issue onboard (which is now approaching 3 months ago) as I have been mainly happy to let them get on with it.

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.

Again, I don't believe i've "unloaded" on anyone.

[bigfatron]

I doubt that they're even working on it. Since X3 has been on the market for quite a while now, I suspect they are more likely than not working on getting X4 out the door. They'll make money selling a new software package. They won't make any money on a patch.

I've been told that they are still looking at the issue, although no indication of timescales or progress is forthcoming at this point.

[LeviFiction]

*sigh* Text is a horrible medium in which to communicate. At the very least for me anyway. I do tend to respond making people seem like they've reacted in a slightly larger way than their own post indicated and I do apologize for that. That's merely my own lack of ability to communicate properly.

bigfatron,I didn't accuse you of unloading on anyone. I'm not that ridiculous as to believe frustration and getting upset is the equivalent of unloading. I said you could if it wasn't fixed in the third patch. A future event should you wish to do so. If you don't then that is also no big deal.

While I still don't agree with you on a number of items, and completely confused by a few of your statements it makes no sense to spam this topic with this little discussion any further. So I apologize for any mis-communication on my part. As I've said text is not a good medium for me.

[bigfatron]

*sigh* Text is a horrible medium in which to communicate. At the very least for me anyway. I do tend to respond making people seem like they've reacted in a slightly larger way than their own post indicated and I do apologize for that. That's merely my own lack of ability to communicate properly.

bigfatron,I didn't accuse you of unloading on anyone. I'm not that ridiculous as to believe frustration and getting upset is the equivalent of unloading. I said you could if it wasn't fixed in the third patch. A future event should you wish to do so. If you don't then that is also no big deal.

While I still don't agree with you on a number of items, and completely confused by a few of your statements it makes no sense to spam this topic with this little discussion any further. So I apologize for any mis-communication on my part. As I've said text is not a good medium for me.

Fair enough. And yes, sometimes things can get a little 'lost in translation'. I'd like to think that passing on a progress report i'd received (or lack of progress, and yes I did let slip a little dissatisfaction with how things are beginning to drag on) and also clarifying a laymans misunderstanding others were having regarding the memory limit per process for 32 bit applications isn't spamming the thread. If you find anything i've said confusing then by all means PM me (i'm a nice bloke, honest!) and i'll try to elaborate further. In the meantime i'll leave the thread until I have fresh information to hand that needs passing on.

[davidh202]

I have only recently started shooting RAW and use the proprietary software from the manufacturer of my camera to develop the RAW files.
I had not delved into this thread before, but read though the whole issue tonight.
All I can say is I remember the problems and complaints with X3s RAW handeling from the beginning and don't understand why anyone bothers even using it. Tim Morrison gave a very informative report on the PSPUG site in which he said that the RAW developer is a sham in PSP.This is could likely be part of the problem with dealing with memory usage in the program and why there is no fix yet, since the basic problem is the way PSPP deals with RAW files to begin with.
http://www.pspug.org/cgi-bin/forum/Blah ... 268880193/

I have been into Photography for over 50 years,dove into digital 3 years ago,and have been progressing (albiet slowly), in the more technical aspects of digital photography. I am now at a stage where I have set up a very up to date, dedicated, Digital Darkroom and am now in the need of a fully competant color managed workflow..
PSP simply has too many issues that are not acceptable for more advanced image editing and I have reached the point of realizing why Adobe PS is the industry standard.Lightroom or CS5 are lightyears ahead of PSPP for dealing with RAW files.
RAW files deserve better treatment than PSPP can give them and now that X3 'Ultimate' has been released with essentialy the same old core program I see no future in Corel, for my needs.
On an amature level it may suffice for most but I can no longer stand behind the product as I have in the past.
The pricing of PSPP X3 will continue to attract new followers but Corel has done nothing to assure it's old faithful customers that it is commited to them by really refining and dealing with the core problems.In all fairness PSPP does an adequate job with most functions of editing, but it has it's limits.
Quirky add ons and gimmicks to sell PSPP are not what serious users want.

[bigfatron]

Just a quick update to say this issue appears to be still present after applying Service Pack 3 unfortunately. No idea if it was officially meant to be fixed in this release or not, but it doesn't appear they have done.

[df]

Would something like this help?
http://www.pcwintech.com/cleanmem
It claims to free up memory. I just tried it out and it appears to work as advertised, which is to say that I opened about a dozen 16 bit Tiffs with Enable PreProcessing enabled and IR Camera script running. TV card also running on computer (hey, it's a good episode of House) and the TV card never bogged down. Memory usage never went over 65%.

I then closed all windows and used Cleanmem and the usage went back to 38%, which is what it was at when I first opened PSP X3.

Anybody geekier than me want to try it? It gets a pretty high rating on http://www.majorgeeks.com/CleanMem_d5993.html

[c_j_ryan]

That's it? The last post on this was nearly a month and a half ago?

As this is my first post I will try to be kind. I'm running 16 gigs of RAM , and a 2TB hard drive. Getting that "out of memory" warning drives me crazy!

I've used PSP, since version 5, I was very disappointed when Corel bought out JASC. I started, using PSP, 13 years ago, it was, to me more affordable than Photoshop back then.

But times change, and I've owned Photoshop for many years now, currently using CS3. But because I started with PSP, I'm more adept at it, and would rather use it.

But believe me unless someone comes up with a solution for this, I'm gone from the PSP fold! I've tried every one of the so called "fixes", and not one of them has worked.

[kchildress]

has anyone noticed an improvement with this memory issue after installing any of the service updates? Does patch 4 help?

[bigfatron]

has anyone noticed an improvement with this memory issue after installing any of the service updates? Does patch 4 help?

Nope, the problem still exists even after the most recent patch.

[c_j_ryan]

I'm still looking for a fix for this.

Moments ago, I went to edit a fairly large file, because it was large, the first thing I tried to do was resize it. 7.2 MB's on disk, the and the Image information suggests it eating up nearly 62 MB's of ram, and this was after my very first edit, which didn't happen. Because of course I got
Corel Sux by c_j_ryan

Earlier today I was able to do the same edit, using PSP XI, on a laptop running 2gigs of ram, and a 2.2 core duo processor.

Please Corel, someone, a little help here?

[sluwater]

Upon using the object extractor I get the " not enough memory to complete the operation" pop up
This happens continually regardless of the file size of the project
I boosted the virtual memory just as a "grasping at straws" kind of thing with no luck at all
Anybody know of a fix or at least a work around?

[grafxman1]

About the only thing I know to do is close all apps including PSP then reopen PSP and try to work. If that doesn't do it then reboot, do ctrl alt delete and kill as many running apps as you can then try it again.