BUG: VB Crashes After Ending Application While in Break Mode (183162)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q183162 SYMPTOMS
While debugging your application in Break mode, Visual Basic may terminate,
hang, or cause one or both of the following errors when you end the
application:
Run-time error '28': Out of stack space
VB5 caused a stack fault in module KERNEL32.DLL at 0137:bff725c5.
NOTE: The memory address at which the error occurs may vary.
CAUSE
This problem can occur when multiple forms are shown modally. The problem
only occurs at design-time when you use the Immediate Window while in Break
mode and then end the application.
RESOLUTION
One workaround for this problem is to avoid using the Immediate Window
while your forms are shown modal or to show your forms modeless instead of
modal. You can show a form modeless yet simulate most of the functionality
of showing a form modal by setting the form's ShowInTaskbar property to
False and by setting the Enabled property of the other visible forms to
False, which prevents users from setting focus to the other forms. When the
user dismisses the form, reset the Enabled property of the other visible
forms as appropriate.
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.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbBug kbpending KB183162 |
---|
|