[UI, performance] Websocket caches are shared but not thread-safe nor transactionally safe
Bug #1489149 reported by
Gavin Panella
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
The cache allocated to each websocket connection by WebSocketProtocol
can be read and mutated by multiple threads, but there is no locking in
place. It is also often mutated within a transactional block but those
changes are not undone if the transaction is aborted.
In practice this does not seem to have been much of an issue. However,
bugs will most likely manifest as slight glitches rather than complete
meltdowns.
| Changed in maas: | |
| milestone: | none → 2.1.0 |
| Changed in maas: | |
| milestone: | 2.1.0 → 2.1.1 |
| Changed in maas: | |
| milestone: | 2.1.1 → 2.1.2 |
| Changed in maas: | |
| milestone: | 2.1.2 → 2.1.3 |
| tags: | added: performance |
| Changed in maas: | |
| milestone: | 2.1.3 → 2.4.x |
| summary: |
- Websocket caches are shared but not thread-safe nor transactionally safe + [websockets] Websocket caches are shared but not thread-safe nor + transactionally safe |
| Changed in maas: | |
| milestone: | 2.4.x → 2.5.x |
| summary: |
- [websockets] Websocket caches are shared but not thread-safe nor + [UI, performance] Websocket caches are shared but not thread-safe nor transactionally safe |
| Changed in maas: | |
| milestone: | 2.5.x → next |
| importance: | High → Undecided |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| milestone: | next → none |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team