Help and Support

Article ID: 201527 - Last Review: June 14, 2006 - Revision: 2.0

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

View products that this article applies to.
This article was previously published under Q201527
Expand all | Collapse all

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.
Back to the top

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.
Back to the top

STATUS

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

REFERENCES

For support information about Visual J++ and the SDK for Java, visit the following Microsoft Web site:
http://www.microsoft.com/java (http://www.microsoft.com/java)


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

Back to the top
APPLIES TO
  • Microsoft Visual J++ 6.0 Standard Edition
Back to the top
Keywords: 
kbbug kbpending KB201527
Back to the top

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations