KB198605 - BUG: Find Next Crashes After Closing a Maximized Code Window

SYMPTOMS

Closing a maximized code window after performing a Find and Find Next subsequently on the code window causes Visual Basic to crash.

The possible error messages are:

An application error has occurred.
VB6.exe
Exception: Access Violation (0x00000005) Address: 0x0fb16e90

-or-

An application error has occurred.
VB5.exe
Exception: Access Violation (0x00000005) Address: 0x0fb16e90

-or-

This program has performed an illegal operation and will be shut down.

-or-

Edit: VB6.EXE Application Error
The instruction at "0x0fa76bb1" referenced memory at "0x00000058". The
memory could not be "read".

-or-

Edit: VB5.EXE Application Error
The instruction at "0x0fa76bb1" referenced memory at "0x00000058". The
memory could not be "read".

MORE INFORMATION

Steps to Reproduce Behavior

Create a Standard EXE project in Visual Basic. Form1 is created by default.

Paste the following code in Form1:

      Private Sub Form_Load()
         Dim x As Integer
         x = 3
      End Sub

Maximize the code window.

From the Edit menu, select Find.

Enter 'x' in the Find What text box of the Find dialog box.

Click the Find Next command button.

Close the code window by clicking on the 'X' button in the upper right hand corner of the code window, not for Visual Basic IDE.

Click the Find Next button.

BUG: Find Next Crashes After Closing a Maximized Code Window

SYMPTOMS

RESOLUTION

STATUS

MORE INFORMATION

Steps to Reproduce Behavior