Re: vb6.exe crash while debugging

Tech-Archive recommends: Fix windows errors by optimizing your registry

I just joined this group because I am getting a very similar problem.

I have an application which I have been working on for years. I just put
some new features in it and it's grown into quite a complicated beast.

Now I can run it once, maybe twice, during a VB session but eventually VB
will crash either with something like:

The instruction at "0x77f551c0" referenced memory at "0xfffffff8". The
memory could not be "read"

Hardly surprising that it couldn't read memory with an address like that
(and why is "read" in inverted commas?).

I have found that by removing large chunks of my vb code I can delay the
fail - ie. run it more times in a session before it crashes. I therefore
suspect it is some kind of resource limit that's being exceeded. My
suspicion is that VB just can't handle large applications.

I also fear that now Microsoft have moved on to .net they may have lost
interest in the old VB development environment, but hopefully I am wrong.

I am also running SP 6. I even tried setting up a brand new machine with VB
and SP 6 and got exactly the same results on that box, so it's not a
corruption on my dev box, it's a VB "feature".

If anyone knows any get around I should be very interested.

Keith




.

Quantcast