StubCodeDesc constructor publishes partially-constructed objects on StubCodeDesc::_list

While chasing the following bug:

JDK-8047212 runtime/ParallelClassLoading/bootstrap/random/inner-complex assert(ObjectSynchronizer::verify_objmon_isinpool(inf)) failed: monitor is invalid

I ran into three SIGSEGV crashes in StubCodeDesc::desc_for()

My baseline is a clone of RT_Baseline at the following fix:

Changeset: 703df4322ebb
Author: dsamersoff
Date: 2015-10-01 10:33 +0300
URL: http://hg.openjdk.java.net/jdk9/hs-rt/jdk/rev/703df4322ebb

8133063: Remove BasicLauncherTest from the problem list
Summary: Remove BasicLauncherTest from the problem list
Reviewed-by: jbachorik

Here's the changeset info for the entire repo:

$ cat SourceTips.txt
 .:34280222936a jdk:703df4322ebb jaxp:497bc2654e11 pubs:618464525123 corba:ca8a17195884 jaxws:bdb954839363 closed:57176e80ab18 deploy:53398009c566 hotspot:983c56341c80 install:a2caf79947c6 nashorn:678db05f13ba sponsors:9e31857dd56d langtools:8e76163b3f3a jdk/src/closed:59bd18af2265 jdk/make/closed:54d0705354f2 jdk/test/closed:de2be51ab426 hotspot/src/closed:002bf5205dcd hotspot/make/closed:d70cd66cf2f4 hotspot/test/closed:5524c847f372

My testing config is running 4 parallel test runs using the following locally built bits:

$ ../build/linux-x86_64-normal-server-fastdebug/images/jdk/bin/java -version
java version "1.9.0-internal-fastdebug"
Java(TM) SE Runtime Environment (build 1.9.0-internal-fastdebug-ddaugher_2015_10_02_11_39-b00)
Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-internal-fastdebug-ddaugher_2015_10_02_11_39-b00, mixed mode)

$ ../build/linux-x86_64-normal-server-fastdebug/images/jdk/bin/java -Xinternalversion
Java HotSpot(TM) 64-Bit Server VM (1.9.0-internal-fastdebug-ddaugher_2015_10_02_11_39-b00) for linux-amd64 JRE (1.9.0-internal-ddaugher_2015_10_02_11_39-b00), built on Oct 2 2015 12:13:07 by "ddaugher" with gcc 4.8.2


$ elapsed_times mark.start_test_run hs_err_pid*
mark.start_test_run 0 seconds
hs_err_pid26813.log 1 days 18 minutes 22 seconds
hs_err_pid28187.log 17 hours 13 minutes 20 seconds
hs_err_pid8500.log 1 hours 9 minutes 11 seconds
hs_err_pid8630.log 11 hours 49 minutes 23 seconds

The first failure (hs_err_pid26813.log) matches the bug I'm
hunting and the remaining three match this bug. I'll attach
the hs_err_pid files.