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

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:


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

Svojstva

ID članka: 201527 - posljednja izmjena: 14. velj 2017. - verzija: 1

Microsoft Visual J++ 6.0 Standard Edition

Povratne informacije