#File Error#'s
-
Hi! Recently, I've been getting errors in my output window that looks like: #File Error#(531) : {32787} client block at 0x034030B0, subtype 0, 64 bytes long. an invalid object at $034030B0, 64 bytes long It looks very much like a memory leak, but according to that first name, it looks like it's related to files. I'm having a bit of trouble debugging it because a) the module (a homebrew .dll) that seems to cause the message doesn't open files and b) Boundschecker doesn't even notice them. Any suggestions on how I should find what's causing this? Steve The Plant
-
Hi! Recently, I've been getting errors in my output window that looks like: #File Error#(531) : {32787} client block at 0x034030B0, subtype 0, 64 bytes long. an invalid object at $034030B0, 64 bytes long It looks very much like a memory leak, but according to that first name, it looks like it's related to files. I'm having a bit of trouble debugging it because a) the module (a homebrew .dll) that seems to cause the message doesn't open files and b) Boundschecker doesn't even notice them. Any suggestions on how I should find what's causing this? Steve The Plant
Steve The Plant wrote: I'm having a bit of trouble debugging it because a) the module (a homebrew.dll) that seems to cause the message doesn't open files Huh, doesn't open files? You need to have the source files so you can fix the memory leak. You should be able to go to line 531 of that file and see where the memory was allocated that you didn't free. Regards, Alvaro
-
Steve The Plant wrote: I'm having a bit of trouble debugging it because a) the module (a homebrew.dll) that seems to cause the message doesn't open files Huh, doesn't open files? You need to have the source files so you can fix the memory leak. You should be able to go to line 531 of that file and see where the memory was allocated that you didn't free. Regards, Alvaro
I understand the error a little more. The "#File Error#" part of the message means that it can't find the file the error occurs in, so instead of the filename it gives #File Error#. So, it knows there's a memory leak and it knows at what line it happens, but it doesn't know which file. Ugh. I'll investigate some more. Steve The Plant