major crash

Quote
garbanzo wrote: i was about an hour into a complex filter when i decided it was about time to save. but the program wouldn't let me. it said users of the basic edition cannot save filters they create

when it happens try saving filter under different new version of name - it works for me

Quote
garbanzo wrote: it said users of the basic edition cannot save filters they create. i checked 'help - about' and it said i was running Filter Forge 1.020 Unknown Edition.

It's a known thing about the Pro edition suddenly turning into Unknown. I'll check the status of this bug with the developers.

it's just the same as Professional Edition except it doesn't work

Quote
Kraellin wrote: dilla is already running the 'enterprise' version.

What??? Where??? I want that version too.... LOL.....

re-install wont help. and you're lucky, i usually get 64 the ONE thing to look for to prevent this is, watch the mouse cursor. if it starts to get sluggish or 'jumpy', save, exit FF and restart it. that's the only warning sign i know of and even that isnt true all the time. sometimes that bug will show up when FF is running and idle for a while. you can also hit control-alt-delete and watch the 'processes' or 'performance' tab and watch your resources get eaten up while FF is running. so, it basically amounts to a memory leak or resource leak. when the resources get low, FF starts to struggle to stay alive and finally gasps for a last breath and dies.

the other thing you can do is, cut the other things that eat your resources. i often have paint shop pro running along with FF. and i've got anti-virus, firewall and other junk running. kill off as many other tasks as you can and increase your virtual memory/swap file. when you notice your harddrive coming on a lot, time to save and exit. you can also go to blackviper.com and configure your machine to be less of a resource hog. however, all of this is simply a prolonging action. it wont necessarily keep FF from crashing, but it shld prolong the time before it does. you can also add more memory to your machine and that will prolong it also.

i actually havent had FF crash on me too often of late and particularly since the last version update. this is partially because i know the warning signs and partially because FF seems a bit more stable.

but do do that test. just open up FF and then hit control-alt-delete and choose the performaance tab. then just watch system memory and kernal memory. both will start to steadily decline. once you've noticed that and are sure of what i'm saying, kill FF and watch some more. you shld now see both those indicators move still, but they will go up AND down, not just down. windows loops. it's on a continuous loop, checking this and that in the system and looking for calls. that's why the numbers arent static; they go up and down. but with FF open, they will just go down. resources are being eaten and not returned. so, eventually, even if idle, it will crash.

increase your windows swap file, too. that might help. and when i say idle, this is going to be relative. how much have you already had FF running and so on.

but, there is a leak. it's a known problem and it's one of the worst to find and fix in programs. some crashes you can isolate and fix because certain things happen and those certain things are related to particular piece of known code. but, a leak can be caused anywhere in the program, so the entire code is suspect and must be gone over with a fine tooth comb. it can be tedious to find. it's often related to certain api calls, but not always. what it looks like when you run the performance thing is that there is a call to memory but the program loops somewhere and calls it again but sees its the memory slot already filled, so it makes another one and keeps duplicating this until memory is used up. and that can happen almost anywhere in the program and be nothing more than a comma where there should be s semi-colon or something almost insignificant like that. can be a real bugger to find.