Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#67227 - [barrier] Memory Leak on Client Disconnect
Attached to Project:
Community Packages
Opened by Jeremy Borgman (borgman_jeremy) - Wednesday, 08 July 2020, 13:59 GMT
Last edited by Morten Linderud (Foxboron) - Sunday, 09 August 2020, 16:13 GMT
Opened by Jeremy Borgman (borgman_jeremy) - Wednesday, 08 July 2020, 13:59 GMT
Last edited by Morten Linderud (Foxboron) - Sunday, 09 August 2020, 16:13 GMT
|
DetailsDescription:
The upstream barrier source has a bug where a memory leak is triggered on client disconnect. A fix was merged to master a while back but still has not been tagged for release. Could you edit the pkgbuild to merge this fix in? Additional info: * package version(s): 2.3.2-2 * config and/or log files etc. * link to upstream bug report, if any: Described here: https://github.com/debauchee/barrier/pull/557 Steps to reproduce: Described here: https://github.com/debauchee/barrier/pull/557 |
This task depends upon
Closed by Morten Linderud (Foxboron)
Sunday, 09 August 2020, 16:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.3.3-1
Sunday, 09 August 2020, 16:13 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.3.3-1