Solved

Out of Memory Error while writing EXE

Posted on 2000-05-08
10
791 Views
Last Modified: 2008-02-01
We are currently developing a (fairly large) VB6 App which has developed a major problem.

The problem we have is that whenever we try and compile now we get an "Out of Memory" error WHILE WRITING THE EXE (NOT while compiling).

As stated above - there is no problem running the entire program in design mode - it just won't compile.

Tried using native code and p-code options and turning off all optimisations to no avail.

The program used to compile fine - at some point recently it has stopped working (only things added to it are a couple of modules and references to a couple of ActiveX Dlls).


We're using VB6 SP3 and see the same problem on both NT and 9x machines.

Can anybody shed any light on this.

0
Comment
Question by:paulstamp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
10 Comments
 
LVL 1

Expert Comment

by:ofirg
ID: 2787633
Try re-installing VB ,SP3 and all other
component u r using?
0
 
LVL 3

Author Comment

by:paulstamp
ID: 2787645
I've tried on a completely fresh machine - no joy unfortunately.
0
 
LVL 2

Accepted Solution

by:
BobbyOwens earned 250 total points
ID: 2787658
I've had a problem before with opening files and getting out of memory errors. It was due to Source Safe corrupting one of the files. The only way round it was by manually editing the file involved. Try opening every module in your project to see if any are corrupted.

Are you using Source Safe?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 3

Author Comment

by:paulstamp
ID: 2787666
We are using SourceSafe but none of the files have been corrupted. As mentioned before - it does run fine in design mode.
0
 

Expert Comment

by:syedAliF
ID: 2787681
This is what msdn says just check these could be some of the problems.
Good luck

Out of Memory
More memory was required than is available.  

There are too many applications, documents, or source files open.Close any unnecessary applications, documents, or source files that are open.


There is a module or procedure that is too large.Break extremely large modules or procedures into smaller ones.


There are terminate-and-stay resident programs running.Eliminate terminate-and-stay resident programs.


There are too many device drivers loaded.Eliminate unnecessary device drivers.

0
 
LVL 3

Author Comment

by:paulstamp
ID: 2787713
Unlikely to be a problem with TSRs or device drivers as my own machine is brand new and hence fairly clean.

Its certainly not anything to do with the number of other apps running or memory available. I have 128mb of RAM and about 3Gb free for swap file !

The large procedure is an ouside possibility but I would expect that to fall during design time, or at least at compile time, rather than while writing the executable.

Note - this is not a run-time-error - there is not even an error number returned : just a dialog pops up when trying to write the executable.

0
 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 2787749
Hm, maybe you have UserControls in your project?
If yes, check your Initialize and Terminate Events or them, if any generates errors because not in runtime.
0
 
LVL 3

Author Comment

by:paulstamp
ID: 2787768
Nope.. no user controls in project.

Does anyone know the mechanics of what VB does during the compile / exe build process. Is it possible that graphics get added into the EXE after the "compilation" phase? If so there could be a corrupt image file that causes the problem.
0
 
LVL 3

Author Comment

by:paulstamp
ID: 2787962
Actually... on further inspection one of the files does appear corrupted. I'm quite surprised that running with full compile doesnt spot it.

The curse of SourceSafe strikes again !

Cheers.
0
 

Expert Comment

by:gupta_ashish
ID: 2788177

Break your project into Active-X Exe's or Active-X Dll's and complied them individually.
you won't get this problem

0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …
Background What I'm presenting in this article is the result of 2 conditions in my work area: We have a SQL Server production environment but no development or test environment; andWe have an MS Access front end using tables in SQL Server but we a…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question