Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Linux x86-64
-
Advanced
Description
The safe_point called from hycond_wait, which called from many places include locktable_reader_enter and locktable_writer_enter.
From other side access to locatable there is in function hythread_reclaim_recources, which works during stop the world.
It leads to dead lock, when first thread, which catch locktable monitor goes into safe poin and GC starts. In this case GC can't complete work, because one or several threads waiting on following stack, when first thread free locktable monitor:
#1 <pthread_mutex_lock>
#2 <hymutex_lock>
#3<hythread_reclaim_resources>
#4 <vm_reclaim_native_objs>
#5 <gc_reclaim_heap>
#6 <fspace_alloc>
#7 ....
So it's a deadlock when firs thread waits when second thread free monitor, and send thread waits when first thread free the other monitor.
Attachments
Attachments
Issue Links
- relates to
-
HARMONY-2772 [drlvm][gc] test stress.Mix intermittently failed on the em64t platform
- Closed