summaryrefslogtreecommitdiffstats
path: root/PROBLEMS
diff options
context:
space:
mode:
authorMichael Meeks <michael.meeks@collabora.com>2019-02-13 18:33:06 +0100
committerMichael Meeks <michael.meeks@collabora.com>2019-02-13 18:35:32 +0100
commite1f3a6a38872165ff99e130cde03e994445ef0bd (patch)
tree106233a8ac29e36d52574d5c1a1afd8a90a919a8 /PROBLEMS
parentAdd calc / typing unit test. (diff)
downloadonline-e1f3a6a38872165ff99e130cde03e994445ef0bd.tar.gz
online-e1f3a6a38872165ff99e130cde03e994445ef0bd.zip
Tweak problemms.
Change-Id: I35d82dffba9f0e58ea70c782ee8ce7fcf8f9b314
Diffstat (limited to 'PROBLEMS')
-rw-r--r--PROBLEMS8
1 files changed, 3 insertions, 5 deletions
diff --git a/PROBLEMS b/PROBLEMS
index f220b85ecb..cfe2a01b72 100644
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -35,11 +35,9 @@
poll() calls to be without timeout. Or something similar, depending
on case.
-- Recursive mutexes are evil. In general, I think the consensus is
- that recursive mutexes should be avoided. One should use them only
- when absolutely necessary because the code-base is so complex that
- one has no idea how it works. That was hopefully not the case when
- recursive mutexes were introduced here? But probably it is by now...
+- Recursive mutexes are evil. The last remaining instances should be
+ removed from the Kit/ChildSession.cppp as/when we move to a single
+ threaded Kit process.
- Occasionally Control-C (SIGINT) doesn't shut down loolwsd. One has
to kill it with SIGKILL. Which of course leaves all the chroot jails