John P.
10th August 2005 21:51 UTC

"Application error - memory could not be "read"" - my installers fault?
Hi.

Again, today I am updating an old installer I haven't touched for a while.

So I update a Readme which will go in the installer, and I change a few very small things in the installer script.

I then compile the script, with no warnings and no errors.

I install the installer, again with no problems.

But - - I then open the un-installer, and I get an:

Application error | The instruction at "0x10106022" referenced memory at "0x6d7563f7". The memory could not be "read". Click on OK to terminate the program.


I then click the OK button of this dialogue, but my un-installer works just fine after that.

I have several other un-installers I have created in the same folder, and they all work without giving me an error.

I then try an older version of this file, because I have never seen this error before, so I'm thinking that if I get the same error with the old file, it will probably be something wrong with the hard drive. And sure enough; when I have installed the old version, and try to use the un-installer, I get the same error.

BUT - I then create a test folder on the Desktop, and install it to that folder. But even there I get the same error when trying to use the un-installer.


So I was wondering if there is a known problem that could cause this? Too long name, too long sentences in the un-installer, etc.? I guess it could be my hardware, but it's weird that it's just this file, and that it gives the error no matter where I install it.

And also that the same error is also in the old file, as I have never gotten this error before, and I'm almost 100% positive that I've tested the un-installer back then.

Again - the installer part works without errors. It's only the un-installer that opens with a 'bang', so to speak...

Any clues? I'm looking for something you know could cause this, 'cause I'm reluctant to post the script here.

Afrow UK
11th August 2005 14:07 UTC

I'm not 100% sure on this but that error message is a "memory leak". We used to get the exact same error message in Half-Life 2 Deathmatch (but I think it's fixed now).

You could attach the uninstaller exe in a Zip here and see if we get it?

-Stu

John P.
11th August 2005 14:56 UTC

OK, thanks - I didn't even think of that!

You can download the uninstaller from here

-Just don't try to actually uninstall anything, 'cause you'll get a bunch of error messages since you don't have the game installed. The installer part contains high-res. textures I have made for the game Thief: Deadly Shadows.

The error should occur the second you open the .exe, if it happens at all.

Afrow UK
11th August 2005 15:11 UTC

I get a "NSIS Error" "Error launching installer" error message if I try to run it.

-Stu

John P.
11th August 2005 15:21 UTC

Hmm... that's weird. I unpacked it from the .rar and put it on my Desktop now, and I get the same memory error as in the first post here. I haven't gotten an NSIS error yet.

I'm on Windows XP Pro SP2, if that makes any difference.

Afrow UK
11th August 2005 15:24 UTC

I am on Windows XP Pro SP2 too :D
I will download it again. The rar isn't corrupt though as WinRAR had no problems opening/extracting it.

Edit: Nvm, it's gone.

-Stu

John P.
11th August 2005 15:41 UTC

Well - it gets weirder and weirder... I found an old version of this installer, one I made one year ago, and I know I tested both install and un-install thorroughly back then. I compile it without touching the folder at all, install it, and when I try the un-installer; voila - same memory error message.

I have asked people who have the game and my installer installed if they could check it out for me, but no-one has replied yet, so I'll just have to wait.

Afrow UK
11th August 2005 16:46 UTC

Which NSIS version are you using?
Perhaps you used an older version before which worked ok?

-Stu

kichik
11th August 2005 17:05 UTC

This is not a memory leak. This is a crash in one of the DLLs loaded by the installer. It might be a standard Windows DLL, or a DLL you unregister in the uninstallation process. Try getting a Dr. Watson log for more details about the DLL that contains the code that crashes.

John P.
11th August 2005 17:28 UTC

I tested an old version of this installer that I compiled using 2.00 or 2.05, and got the same error. I'm using 2.08 now.

Anyway - it doesn't really matter, 'cause I just got word back from two people who use my installer, and they didn't get any error when opening the un-installer, so I guess there's some strangeness going on with my computer.

Thanks for trying to help though. :)