archive/jdk
1
0
Fork 0
mirror of https://github.com/openjdk/jdk.git synced 2025-09-20 02:54:35 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

8149901: [Solaris] Use of -XX:+UseThreadPriorities crashes fastdebug

Browse source 
Reviewed-by: gziemski, sspitsyn
This commit is contained in:
David Holmes 2016-05-20 01:47:32 -04:00
parent 5648deddee
commit 81a0fa24dd
1 changed files with 7 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

16
hotspot/src/os/solaris/vm/os_solaris.cpp
View file

@ -756,15 +756,9 @@ extern "C" void* thread_native_entry(void* thread_addr) {
}
}
// If the creator called set priority before we started,
// we need to call set_native_priority now that we have an lwp.
// We used to get the priority from thr_getprio (we called
// thr_setprio way back in create_thread) and pass it to
// set_native_priority, but Solaris scales the priority
// in java_to_os_priority, so when we read it back here,
// we pass trash to set_native_priority instead of what's
// in java_to_os_priority. So we save the native priority
// in the osThread and recall it here.
// Our priority was set when we were created, and stored in the
// osthread, but couldn't be passed through to our LWP until now.
// So read back the priority and set it again.
if (osthr->thread_id() != -1) {
if (UseThreadPriorities) {
@ -1044,6 +1038,10 @@ bool os::create_thread(Thread* thread, ThreadType thr_type,
// Remember that we created this thread so we can set priority on it
osthread->set_vm_created();
// Most thread types will set an explicit priority before starting the thread,
// but for those that don't we need a valid value to read back in thread_native_entry.
osthread->set_native_priority(NormPriority);
// Initial thread state is INITIALIZED, not SUSPENDED
osthread->set_state(INITIALIZED);