I don't know????

Some errors I have recieved as of late.

Before the update:
I was editing a certain filter of mine and going back and forth between the edit mode and the main window. All of a sudden Filter Forge closed with the message saying that I could generate a bug report. I hit okay, and a window popped up asking me if I would like to generate a bug report, so I hit okay again, and another window popped up. I hit close, and a new window popped up. So no matter what I did a new error message would pop up with a new error name. I tried to open FF again to see if it would close the window but I got a message saying FF was already running (presumably referencing the generate report window.) I finally had to hit ctrl. alt delete and shut down the error message with the system manager.

I gathered some information about this bug, namely the error numbers and they are as follows:


I didn't submit this report because I thought it was just a gliche with the old FF; however, I have sense had a very similiar occurence(after downloading the new update): but the issue has seemed to escalate. This time around I was working on a pretty beefy filter and FF close with a generate report message appearing. Like before I could not get rid of the window and everytime I clicked close or generate report or cancel a new window with a new error code would take the place of the preceeding window. I once again had to close the generate report window in my system manager The escalation was found when I opened up FF and a message appeared informing me that the filter I had been working on was not formated to be readable. Everytime I open FF I get this message.


I hope this is helpful in the future development of FF, and if you have any questions let me know.


P.S. It is strange because it comes back saying the invalid file is 0KB big but it is still on my computer? Another bug? I tried to attach it but since it is 0 kb Big I can't.

I've noticed that if I worked on or left FF on for long amounts of time it tended to do that bug more often. Now I make sure it's closed whenever its not in use (and actually have only been making relatively quick and filters as of late) and I haven't had this problem for a quite a while. But I still make multiple versions of the same filter (e.g. "blur1a" and a renamed, "blur1b") just in case one gets corrupted...

Quote
Redcap wrote: P.S. It is strange because it comes back saying the invalid file is 0KB big but it is still on my computer? Another bug? I tried to attach it but since it is 0 kb Big I can't.

This is normal -- the file was created empty (0 bytes) but nothing has been writen into it due to the bug. Just delete it.

yes, the multiple reports often accompanies the resource leak bug. i've gotten as many as 120 error reports from one crash. just keep clicking the 'X' and they'll eventually go away.

CF, i dont think this resource leak thing is related to any one filter. i believe it's a windows thing. and more than likely isnt an FF bug at all, but rather a windows bug that simply shows up through FF.

i dont think so, redcap. it's resource management thing with windows. and mostly related to ram handling. ram gets fragmented with use. it's just like with a harddrive that gets fragmented. windows has no real good way to clean or de-frag the ram. so, after a lot of use it gets so bad that it finally sort of blows up.

there are ram flushing utilities out there that can clean this up. you can also just kill FF and restart it and that will help. that shld always be done when you start to see the mouse jerk and lag. you can also sometimes tell it's coming when you see your harddrive light start coming on a lot. that often means your virtual mememory/swap file is being used as ram and that tells you that your ram is basically in full use.

getting more ram will also help, but only in delaying this inevitable occurrence, since you now have more ram space. but, with enough use, it will still end up fragging.