BUG: VJ++ Does Not Start or Uses Too Much Memory on Startup (201527)


The information in this article applies to:

  • Microsoft Visual J++ 6.0
This article was previously published under Q201527

SYMPTOMS

Certain corrupt configuration files cause Visual J++ to do one of the following:

  • Not load.
  • Use excessive amounts of memory when the developer shell loads.

RESOLUTION

  • If your Visual J++ 6.0 generates a GPF on startup then try renaming or moving the following file to a different directory:

    \windir\Profiles\user\Application Data\Microsoft\Visual Studio\views.prf (profile file)

    NOTE: The user's profile will be re-created the next time Visual J++ is loaded so it is safe to remove this file.
  • If Visual J++ uses excessive amounts of memory during startup and after releases some of that memory after loading Visual J++, you might have a corrupt file in the project that you are loading. Check the following file and rename or move them:

    project name.suo

    NOTE: The .suo file will be automatically re-created the next time the development environment is loaded for this project so it is safe to remove it.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

REFERENCES

For support information about Visual J++ and the SDK for Java, visit the following Microsoft Web site:

http://www.microsoft.com/java



(c) Microsoft Corporation 1998, All Rights Reserved. Contributions by Scott R. deBeaubien, Microsoft Corporation.

Modification Type:MajorLast Reviewed:6/14/2006
Keywords:kbBug kbpending KB201527
©2004 Microsoft Corporation. All rights reserved.