YOUR ACCOUNT

Login or Register to post new topics or replies
Kraellin
Kraellin

Posts: 12749
Filters: 99
i think this is another of those 'windows resource' type crashes. i'll keep reporting them, but they all seem pretty similar.

i was working on a variation of CFandM's anaglyph filter. i worked on it a lot yesterday and had no problems. today, i noticed almost immediately on going into the editor, that the mouse was stuttering, 'catching' here and there and i figured this filter was going to crash. sure enough, when i tried to save after making a minor modification, it blew up and took FF with it.

no bug report in i.e. was generated. just got this one screenshot of the error message.

this one did surprise me a little bit, though. i hadnt had a lot of other programs running today. i hadnt run paint shop pro or anything but i.e. and FF since booting up. and i hadnt even run FF that much. so, in comparison with running this same filter yesterday, i had MUCH more going on yesterday than today and never got a crash yesterday.

one difference between yesterday and today is, i imported a .tiff image rather than a .jpg to use with the filter. but being that this is so similar to other crashes i've had like this, i'm guessing that isnt it.

If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
CFandM
ForgeSmith

Posts: 4761
Filters: 266
Yep I get this also..Most likely on the same variation..Don't know which one there was a couple of them that I had this happen. Maybe its a blend between the imported image and how many thumbnails need to render inside the edit window..But this is only a guess...
Stupid things happen to computers for stupid reasons at stupid times!
  Details E-Mail
Vladimir Golovin
Administrator
Posts: 3446
Filters: 55
I'll append this to the other related reports.
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
it may also be related to the 'cant do while rendering' bug. remember that one where we said sliders would move but the numbers wouldnt change (in the GUI). maybe if an image is still rendering and you hit save it would sometimes crash. dont know. also just a guess.

but this one did surprise me. i hadnt used a lot of resources yet in the day. so, my machine was still relatively 'fresh' after just booting up. when i went back and loaded FF again, without rebooting the whole machine, i got an error message about the filter i had tried to save, that it was now corrupt. but i had no more problems with FF all day. so, i dont know what it is. maybe it's a conflict with something else on my machine, like one of those 'run once' type routines. maybe there was just something running in the background of windows that was in conflict and when that quit there was no more problem. i dont know. lol. i could sit here and guess all day, i suppose. 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:

35 unregistered users.