| Age | Commit message (Collapse) | Author |
|---|
|
|
|
For now: use a single lock, which should fix all related crashes.
optimize (with less contended partial locks) if this works.
|
|
Some overzealous locking to track down RequestObject related crashes.
bc0fa4d689a4 wrongly locked the current event loop's
request_invalidation_lock instead of the invalidation's list lock.
Also Abstract UI is able to delete requests concurrently with with
EventLoop invalidation.
e.g. PortManager::PortRegisteredOrUnregistered and GlobalPortMatrixWindow
so the lock needs to be exposed.
If this solves various issues, mutexes should to be consolidated
(request_buffer_map_lock + request_invalidation_lock) and be chosen
such that there is as little contention as possible.
|
|
* use target name in help text
* add options and documentation to copy-mixer
|
|
* emulate 256 i/o (don't loose connections)
* allow "silent" start
|
|
|
|
|
