Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Runtime: Threads and Concurrency
-
Labels:None
-
Number of attachments :
Description
TimerThread doesn't use as much locking as it should: it gets a thread from a list, without locking, and then proceeds to set some fields on it. That "works" except that the TimerThread doesn't stop for GC, so it's possible that a GC occurs in between it getting the thread and setting the field.
The simplest solution is to use more locking (acctLock would work), but there are probably other, better, ways.
Activity
Filip Pizlo
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Assignee | Filip Pizlo [ pizlo ] |
David Grove
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |