vb6.exe hangs while compiling

Harald Ott

unread,

Feb 18, 2003, 5:05:27 PM2/18/03

to

Hello ng,

i have a standard-exe project containing about 15 activeX components.
When i try to compile the project the process vb6.exe has a CPU-usage of
99%. I waited for 10 Minutes but nothing happened. One time the compiler
made it created .obj files but wasn't able to link then-> again vb6.exe
hangs.
The problem appeared the first time when i tried to compile the ocx-files
and the exe file at once in a project group.

I tried to copy everything into an empty project but the error remained.

Does anybody has an idea?

Thank you for your time,

Harald

RUNTIME_DLL

unread,

Feb 21, 2003, 9:36:27 AM2/21/03

to

Harald

99% of CPU usage is a lot. Proboably too much for the OS
to survive.

What OS do you have?

How many MHz/GHz does your processor have.

How much ram does your system have?

Does the problem happen with any other VB projects?

The most likely thing that is happening is that your
system does not have enoguth RAM/Processing power to run
normally. When VB6 compiles this project it takes up all
the processing power causing your system to become
unresponsive to a certain extent. It then in turn causes
VB to hang as the system struggles for enough CPU to
become free.

>.
>

dnagel

unread,

Feb 21, 2003, 9:14:55 PM2/21/03

to

Try adding one ocx at a time and build the DLL...

See which one (or how many) it takes to kill the compiler.

D.

"Harald Ott" <haral...@siemens.at> wrote in message news:#YFrXm51CHA.2564@TK2MSFTNGP12...

Wilko

unread,

Feb 22, 2003, 5:34:19 PM2/22/03

to

My experience is that VB really uses all CPU time when compiling.
Of course 10 minutes of non-activity is long. How big is your project?
If you compile to native code (rather than p-code) object files are created.
You can use programs like Windows Explorer to see which module or form is
being compiled (I think the object files are created in the same directory
as the executable). That allows you to see if there is any hidden progress
or not. It also allows you to see which module if form is causing the
hanging.

Hope this helps.

Wilko Verweij

RUNTIME_DLL heeft geschreven in bericht
<035601c2d9b6$9db14170$2f01...@phx.gbl>...

Duane Bozarth

unread,

Mar 4, 2003, 3:33:33 PM3/4/03

to

Sometimes VB <does> hang/fail to complete compilation to .exe -- in my
experience, it seems to be a problem w/parsing a file that contains some
particular sequence of commands but which I have never been able to
discern what is the particular cause.

Solutions--
1. Sometimes (almost always?) p-code will succeed where full
compilation fails.

2. Sometimes (I've been told but don't think I've ever had it work)
changing compilation options will work

3. Piecewise isolate the portion of code that causes the problem and
rearrange the source code to accomplish the task in another way. I've
had as simple a change as introducing a temporary variable in a complex
line or even just adding a "do-nothing" line of code make the problem go
away.

BTW, wrt option 1. above--often one can simply go to using p-code while
completing development, then when done revert to compilation and the
revised project will compile just fine...

I'll also note that I've been able to reproduce a failure cured by
option 3. above repeatedly so I'm convinced it is real.

HTH...