YOUR ACCOUNT

Login or Register to post new topics or replies
Carl
c r v a

Posts: 7289
Filters: 82
As I was generating presets the program froze and I'm not sure bug reports were sent to you as my internet would not open while this was happening, the following occurred - Failed to close event handle { event 000EC16C ]This was only the final bug error message as each time I pressed bug report button it generated a new error number and I couldn't close the the error report box, they all had the message - Failed to close event handle [event ....... ]. I left touching machine for say 5 minutes, returned and I closed the error report box and the filter Forge GUI closed at the same time. The desktop Icon was ghosted out, there was no FF icon running in the bottom bar of desktop, when I tried to open filter Forge the message said - Cannot run FilterForge - the program is running, and I couldn't get the GUI to appear. I tried to reboot windows but couldn't turn computer off...... turned pc off at power supply ......... turned on......... FF launched normally but had that old gem - Cannot load ..... ffxml file format is invalid.
Anyway if you got bug reports ignore smile:) ........ Carl
  Details E-Mail
StevieJ
Designer/Artist

Posts: 11264
Filters: 163
Your mouse/cursor will start to get choppy and/or rendering will start to slow usually right before this happens. I would suggest, if you see these signs, save your work and close FF immediately. FF usually comes back OK, but if it doesn't, clean all the junk files off of your computer the restart FF. If you go too long after seeing these symptoms, FF usually crashes and 0-bytes (destroys) the filter that you have open. Hopefully, this bug will get fixed soon.....
Steve

"Buzzards gotta eat...same as worms..." - Clint :)
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
Quote
StevieJ wrote:
Your mouse/cursor will start to get choppy and/or rendering will start to slow usually right before this happens. I would suggest, if you see these signs, save your work and close FF immediately.


Interesting. I had the same on my machine today.
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
carl,

if it happens again, just keep pressing the close on all those error messages. they will eventually stop. i think i got 44 or 54 of them once. i forget, but it was a lot.

then, if FF still seems to be running...somewhere... , hit 'control-alt-delete' to call up the task manager, find FF, highlight it if it's not already, and hit 'end process' (or end task). that shld clear it.

then, it's recommended that you reboot your machine. your resources will be low and a reboot shld restore everything.

you're still going to lose that one filter as being corrupted. so, like steve said, when you see those early warning signs, save and kill FF and start again.

also, i have noticed since upgrading my 'critical updates' for windows, including service pack 2, i.e. 7, windows media upgrades and some other things, that this hasnt happened AT ALL on my machine, where i was getting it regularly before. so, this all points to a very large memory leak within windows xp itself, and not filter forge. filter forge is just the victim here and not the problem itself.
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
Carl
c r v a

Posts: 7289
Filters: 82
Thanks every one, I will do all suggested, Kraellin just a note my windows is fully updated but I can have problems caused by updates themselves screwing up my whole machine, very frustrating and I dred when they come in - but I feel I can't ignore them............... Thanks smile:) .......... Carl
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,711 Registered Users
+18 new in 30 days!

153,531 Posts
+36 new in 30 days!

15,347 Topics
+72 new in year!

Create an Account

Online Users Last minute:

30 unregistered users.