BUG: Stop a Running Project From Immediate Window Crashes IDE (190087)

SYMPTOMS

In a Visual Basic project, attempting to create and show a large number of modal forms and then stopping the application from running in the IDE will either shut down Visual Basic 5.0 automatically or crash it and generate the following message:

VB5 caused a stack fault in module KERNEL32.DLL at 0137:bff725c5.

The crash occurs when you go into break mode, use the Immediate window, and then stop the application in IDE.

This error does not occur if the application is run as a compiled EXE.

CAUSE

Too many modal forms in a Visual Basic project will cause Visual Basic to check numerous system message loops and go into an infinite loop, thus creating a stack overflow. This may occur due to a low stack space as numerous copies of a form are currently loaded modally.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

Open a new Standard EXE project in Visual Basic. Form1 is created by Default.
Add a CommandButton (Command1) on Form1.

Paste the following code in Form1's code module:

      Private Sub Command1_Click()
         Dim x As Form1
         Set x = New Form1
         x.Show vbModal
      End Sub

Press the F5 key to run the project. Click Command1 39 times to create 40 modal forms.
Press the CTRL+BREAK key combination to pause the project.
Press the CTRL+G key combination to bring up the Immediate window.
Type ? 1 in the Immediate window, and press the ENTER key.
Stop the project from running by clicking the Stop button on the toolbar.

Note that while Visual Basic is closing all the modal forms, it eventually crashes and either shuts down or generates the following error message:
VB5 caused a stack fault in module KERNEL32.DLL at 0137:bff725c5