Commit 77b1725
Fix data race in JavaDataViewerProxy::GetCurrentEndpoint
IDataViewer returns the endpoint by const reference, so the referent must
outlive the call and must not be mutated while a caller holds it. The
proxy updated a shared member under a mutex and then returned a reference
to it, releasing the lock on return: two concurrent callers could read and
write the same string at once, so the mutex gave no protection.
Use a thread_local buffer instead, which gives each calling thread its own
storage and removes the need for the lock. Behaviour is unchanged: the
endpoint is still read from Java on every call, so a viewer that changes
endpoints still reports the current one.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 65d01fa commit 77b1725
2 files changed
Lines changed: 21 additions & 16 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
168 | 168 | | |
169 | 169 | | |
170 | 170 | | |
171 | | - | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
172 | 177 | | |
173 | 178 | | |
174 | | - | |
| 179 | + | |
175 | 180 | | |
176 | | - | |
177 | | - | |
178 | | - | |
179 | | - | |
180 | | - | |
181 | | - | |
182 | | - | |
183 | | - | |
184 | | - | |
185 | | - | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
186 | 189 | | |
187 | | - | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
188 | 196 | | |
189 | 197 | | |
190 | 198 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
12 | | - | |
13 | 12 | | |
14 | 13 | | |
15 | 14 | | |
| |||
41 | 40 | | |
42 | 41 | | |
43 | 42 | | |
44 | | - | |
45 | | - | |
46 | 43 | | |
47 | 44 | | |
48 | 45 | | |
| |||
0 commit comments