Re: The memory could not be "read". Application Crash??
From: [SolarAngel] (not-for-mail)
Date: 10/06/04
- Next message: Michael Culley: "Re: Aaarrrggghhh -- that ugly flicker!"
- Previous message: Rob: "Re: Aaarrrggghhh -- that ugly flicker!"
- In reply to: Ian: "The memory could not be "read". Application Crash??"
- Next in thread: Michael Culley: "Re: The memory could not be "read". Application Crash??"
- Reply: Michael Culley: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 6 Oct 2004 05:38:05 +0200
Access denied 0x05 (The memory could not be Read/Write)
=========================================
mostly problem could be with subclassing if you haven't released hook and control is unloaded, or unloading and you try to call in
Hook previous WindowProc function that now belongs to the system NT raises Access Denied (0x05) error unable to read or write
memory.
(I had a UserControls with subclassing & subclassing, and after some time my VB.IDE started crashing with this error, I remember
that problem was with having SubClassed VB.TextBox with MultiLine property set to true (!?) After what I have moved that controls to
another New Control, and used that new control, and everything was working after. It seams to me that there maybe was one more hook
that makes mess that executes last and returns my proc address for WndProc...)
It was here on newsgroups documented to the bone how and when, maybe something similar is going on with yours subclassing
!!!!!!!!
Be sure to add in your subclassing test for WM_DESTROY
and destroy there subclassing if somehow you haven't already!
!!!!!!!!
MAXMIN:
I have tried similar code, maybe little different from yours, and have similar thing in my project so I had to exclude code for
sizing windows to min & max size.
But most strange thing was that on some system it work fine and on the other doesn't work but has no same pattern every time.
I had no really time to debug it to the bone to release was the problem, maybe some other day.
[SolarAngel]
"Ian" <ian@NoWhere.com> wrote in message news:#CF5K8uqEHA.1988@TK2MSFTNGP09.phx.gbl...
| Hi all
|
| I have a VB6 application I am developing that seems to be throwing up this
| error message and then crashing the program.
|
| The instruction at "0x77fcdf2a" reference memory at "0x00213408". The memory
| could not be "read".
|
| I don't know what to look for in my program to solve this.
| And there doesn't seem to be a patter for when this happens.
|
| There is only 2 things that I can think of in my program that sort of
| meddle with memory directly.
|
| ONE
|
| I am using (CopyMemoryToMinMaxInfo Lib "kernel32" Alias "RtlMoveMemory") and
| (CopyMemoryFromMinMaxInfo Lib "kernel32" Alias "RtlMoveMemory").
|
| I use them to control the size of my forms. I don't have any error handling
| in my WindowProc function. I was not sure if I could put any there. So I
| don't know if this is what is causing the problem.
|
|
| TWO
|
| I am also handing a large record set to a procedure in a module from a form
| using ByRef.
|
|
| I don't know if I am on the right track but I think the problem is more
| likely #1.
|
| But I don't really know what to do about it.
|
| Any advice would be good.
|
| Thanks heaps,
|
| Ian
|
|
|
|
- Next message: Michael Culley: "Re: Aaarrrggghhh -- that ugly flicker!"
- Previous message: Rob: "Re: Aaarrrggghhh -- that ugly flicker!"
- In reply to: Ian: "The memory could not be "read". Application Crash??"
- Next in thread: Michael Culley: "Re: The memory could not be "read". Application Crash??"
- Reply: Michael Culley: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
