• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

VB6 crashing & "Out of Memory" compile errors

T

TakedownCA

Senior member
I've got an app that has two main formst with ~30 controls on each, mainly just buttons and textboxes with a couple listviews thrown in. Half the time when I run the program in the IDE it runs fine. The other half I get "Compile Error - Out of Memory" and the VB6 IDE freezes until I end process. I've got 2GB of memory, so I don't think memory is the problem. Also when I run the compiled program (and it compiles fine) I always get a "The instruction at 0x77fcc887 referenced memory at 0x0010a08d. The memory could not be read". If anyone has any ideas, I'd be very thankful. I spent a week developing this for work, and I doubt the boss would be too happy if it was time wasted. Thanks again for any help provided.
 
30 controls on a form isn't alot so thats not it. Are you using any special form controls from third party vendors? If so remove them. Create a new form and copy the controls to that the new form and see if that form is being affected. What looping code are you using in the form? Are you looping through something to fill in the List controls? If so check your looping code to make sure it isn't looping too much.
 
Nope, no third party anything. Closest thing I have is a wrapper for some registry manipulation functions. I have 4 control arrays of 5 instances each that I loop through to populate. But from what I've seen it doesn't do anything odd there. Even when the iteration parameters were off (forgot whether using base 0 or 1) it just gave me the usual corrective error. No crashing of the IDE.
 
Yes, I use loops to populate the listview controls. But again, nothing special there. If there was an actual programmatic error I would think it would show up every time I ran the program, but that's not the case. I've been using VB for 2 years now (I know, not that long) and have never seen anything this odd.
 
it sounds like some kind of memory leak. i would either look into a tool to help track down memory leaks or isolate the various components you're using.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top