gobby uses 100% CPU on files >500KB in size
Bug #251472 reported by
Rolf Leggewie
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
net6 (Ubuntu) |
Fix Released
|
Medium
|
Philipp Kern | ||
Hardy |
Fix Released
|
Medium
|
Unassigned | ||
Intrepid |
Fix Released
|
Medium
|
Philipp Kern |
Bug Description
Upstreams devs verified that gobby eats up a lot of CPU when trying to collaborate on a rather large text file (in my case it was just shy of 1MB). After about a minute, the session connection was severed. gobby continued to use 100% of CPU, never recovered, became unresponsive and had to be killed with "killall gobby".
Upstream devs quickly provided a patch in 5d3d8c71645b5bf
Related branches
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in net6: | |
assignee: | nobody → pkern |
importance: | High → Low |
importance: | Low → Medium |
Changed in net6: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Steps to reproduce the problem:
* Install `gobby'.
* Start a Gobby server somewhere (localhost might also be possible)
* Connect with another Gobby client.
* Open a big text(!) file with many newlines, colons and/or slashes (those are the characters that are escaped). In the tests it was a 1Mb file.
* Watch the GUI freeze while Gobby does many, many memmoves while escaping the outgoing packet.