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

Initialize ObjectMonitor eagerly

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 12
    • 12
    • hotspot
    • None
    • b14

    Description

      ObjectMonitor::DeferredInitialize is called lazily/on demand when the first object monitor instance is used.

      Before JDK-8210848 it contained code to process command line arguments etc., but after JDK-8210848 the only part that remains is setting up some spin related settings. The only dependency that code has is that os::is_MP() returns the actual number of processors, which is done in os::init().

      The ObjectMonitor initialization can and should be done explicitly instead.

      Attachments

        Activity

          People

            mikael Mikael Vidstedt
            mikael Mikael Vidstedt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: