YOUR ACCOUNT

Login or Register to post new topics or replies
rgoer
Posts: 46
I have found out the hard way not to leave filterforge running overnight if your pc is set to go into sleep mode after a certain timeout... if you have a filter open in the editor when your pc goes to sleep, when you come back the next day things are bad.

It will appear at first as if nothing is wrong, and I see that my filter is marked as "unsaved" so I think "oh no, quickly I must save, or else I'll lose everything!" But trying to save a filter after coming back from overnight sleep mode causes a crash "unable to create record." Fine, I lost my unsaved changes, whatever I could deal with that.

BUT!

It's not just unsaved changes getting lost! The entire filter is corrupted! The file is replaced with a 0KB empty garbage file!

This has happened twice now, so I have learned my lesson for sure (the first time I thought it was maybe just a fluke). But since it has happened again, I figured I should report the bug/warn others...
  Details E-Mail
rgoer
Posts: 46
sorry, the error was: "Failed to create event (event 0011F738)."
  Details E-Mail
ssamm
Posts: 364
Filters: 21
rgoer,

FF has an unfortunate "Resource Leak" bug/problem. (It's been often mentioned in this forum.) Until it gets fixed, some rules of thumb (that I use) are:

1. Continually back up filters you're working on. (E.g. I'll often "save as" one filter under two different names.)
2. Don't have FF open for too long at a time. That is, it seems the longer it is open, the greater the chance there will be a crash. (E.g. After using FF for a while, I'll save or cancel things, close it down, then re-open it (where I'm generally using FF as a PS plugin). Yeah, it sounds sort of "ghetto", but it seems to work (vs. where before when I was often running into the 0 KB crash problem).)

  Details E-Mail
jffe
Posts: 2869
Filters: 90
The crash where it f*cks yer filter by erasing all the xxml code or whatever and leaving it as a named file of 0kbs in size is a real treat. There seems to just be a point at which (I dunno if it's time using FF, or the size of the pagefile it creates or what) nothing you can do will stop the leak/problem, ie = shutting FF and reopening it is useless at that point. Since getting a dualcore system recently, the problem is 100 fold worse than it ever was for me. I highly and not so politely recommend they pull the mac version off the high priority list, and fix what little they have before word of mouth gets around and scares away those few mac sales they might've gotten if it worked stable to begin with on pcs. I can't imagine what they are thinking at this point. *sigh*

jffe
Filter Forger
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
Quote
jffe wrote:
I highly and not so politely recommend they pull the mac version off the high priority list, and fix what little they have before word of mouth gets around and scares away those few mac sales they might've gotten if it worked stable to begin with on pcs.


i tend to agree. nothing is more frustrating than a software program that doesnt work right and loses all your work for you because of a crash or lock-up. i mean, unless you're pretending to be microsoft or something; then we'd expect it smile;)
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  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:

14 unregistered users.