aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/assistant_eats_all_CPU
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/assistant_eats_all_CPU')
-rw-r--r--doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment b/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment
new file mode 100644
index 000000000..cd14d9084
--- /dev/null
+++ b/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.227"
+ subject="comment 1"
+ date="2014-01-01T20:13:04Z"
+ content="""
+This strongly resembles ghc RTS bugs such as <http://bugs.debian.org/677096> (except that one got fixed, and affected the non-threaded RTS, while this is using the threaded RTS).
+
+The assistant and the webapp are the same process. The only difference is whether a web browser is talking to it. Unless the other bug is regarding the CPU used by the web browser, that other bug is a duplicate of this one.
+"""]]