-
Enhancement
-
Resolution: Fixed
-
P4
-
8u20, 9
-
b42
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083228 | emb-9 | Aleksey Shipilev | P4 | Resolved | Fixed | team |
JDK-8156254 | 8u111 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8148842 | 8u102 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8162051 | emb-8u111 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
"Reported" here: https://twitter.com/VladimirSitnikv/status/518043826678956033
We can just store the String as Thread.name, can't we?
Are there initialization races? Security implications?
We can just store the String as Thread.name, can't we?
Are there initialization races? Security implications?
- backported by
-
JDK-8083228 Thread.getName() instantiates Strings
-
- Resolved
-
-
JDK-8148842 Thread.getName() instantiates Strings
-
- Resolved
-
-
JDK-8156254 Thread.getName() instantiates Strings
-
- Resolved
-
-
JDK-8162051 Thread.getName() instantiates Strings
-
- Resolved
-
- relates to
-
JDK-4745629 (thread) Thread.setName does needless string allocations (don't use char[])
-
- Closed
-