Jh4X007 |
After making a few filters myself, when I closed the Filter Forge window (main window), I got a crash message referring to an instruction at 0x00e05283 referencing memory at 0x00000000 and the memory being unreadable. This is clearly an indication of a null pointer dereferencing somewhere in the exit code of the program.
Also, after crashing a few times like this, Filter Forge is unable to access the normal library (i.e. the main filters that come preinstalled, for example, the organic textures). It just refuses to notice the files. I tried removing the files from the AppData Roaming folder and then putting them back but the problem seems to persist. I have attached images of both the bugs. I hope Filter Forge Team looks into this issue ASAP. (And counts this as 2 bug submissions ![]() ![]() ![]() |
|||
Posted: March 17, 2013 3:36 am | ||||
Jh4X007 | ||||
Posted: March 17, 2013 3:39 am | ||||
Jh4X007 |
I just noticed one more thing, the filters are back if i download a new filter... Queerer and queerer...
![]() |
|||
Posted: March 17, 2013 4:15 am | ||||
CFandM
![]() |
Ahh yes I remember that one...
![]() ![]() I ran across this on windows7....Did you close out/quit FF and restart the computer?....That is one way to get FF back and running as well.... Heres where I came across this one...Still not sure on the cause... I do remember thou that if you keep FF opened while letting it crash a couple of times the categories will become corrupt until you restart...This was during the intslider bug testing... http://www.filterforge.com/forum/read...&TID=10506 Stupid things happen to computers for stupid reasons at stupid times! |
|||
Posted: March 17, 2013 11:25 am | ||||
Bionic
Posts: 134 |
0x00e05283 referencing memory at 0x00000000
I think this error is related to Windows 8 and you will get this everytime you close FF (for now). I'm sure this will be fixed at final stages before commercial release since beta keys were sent out. Windows 8 & v3 users had this same error with the old license format which is still present in FF 4 (beta) |
|||
Posted: March 17, 2013 2:43 pm | ||||
GMM
Moderator
Posts: 3491 |
Bionic is right: the beta will show an error message on close under Win8, this is not specifically related to beta and I don't expect this to be fixed until the commercial release.
As for the corrupt categories, we're unable to reproduce this. Though I admit the categories file may get corrupted in some cases we have no way to reproduce it reliably. |
|||
Posted: March 18, 2013 4:37 am | ||||
Jh4X007 |
what i don't understand is why the error message with "Filter Forge x86.exe" appears even if i specifically run the "Filter Forge.exe" (i.e. the 64 bit executable) from the bin folder...
and, i'll post back once i figure out what exactly caused the category corruption... hopefully its not a freak system time based event ![]() |
|||
Posted: March 18, 2013 2:25 pm | ||||
GMM
Moderator
Posts: 3491 |
Filter Forge.exe is simply a loader that calls Filter Forge x86.exe. |
|||
Posted: March 19, 2013 5:35 am |
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!
28 unregistered users.