Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4421334

REGRESSION: console must be made truly disable-able in 1.3.0_01+

XMLWordPrintable

    • beta
    • generic
    • generic
    • Verified



      Name: yyT116575 Date: 03/02/2001


      java version "1.3.0_02"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_02)
      Java HotSpot(TM) Client VM (build 1.3.0_02, mixed mode)

      In 1.3.0-C and prior versions of the plug-in, the java console could truly be
      disabled. Output sent to it would not normally cause any performance
      degradation, and there was a relatively small maximum amount of memory that
      would be consumed by the console even if it was open. This has changed in
      1.3.0_01 and later versions. Even with the console "not shown", Applets that
      occasionally (or normally) send output to the console will experience some
      performance degradation and, more importantly, the output sent will consume
      memory and eventually the process that the plug-in runs in will run out of
      virtual memory. Please put a tunable "maximum memory" limit on the console
      and throw stuff away like the old Java plug-in console did.
      (Review ID: 118011)
      ======================================================================

            mafishersunw Margarita Fisher (Inactive)
            yyoungsunw Yung-ching Young (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: