mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1094] Excessive page table entries #872
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#872
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @skarfie123 on GitHub (Mar 9, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1094
Describe the bug
Over 70000 page table entries for "barriers.exe" totalling 2.2GB, resulting in 100% ram usage in Task Manager. Caused slow down of my machine and lots of lag. Managed to solve by "Empty Standby List" feature of RAMMap program.
This is even though I have not used Barrier in a while. (I have disabled it in the Startup tab of Task Manager)
To Reproduce
I don't know what is caused it but even after reboot it continued.
However, it did not return when rebooting after the RAMMap solution.
Expected behaviour
Barrier to not be running at all.
Desktop:
Additional context
RAMMap: https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
@skarfie123 commented on GitHub (Mar 14, 2021):
a few days later, I check again and they're back.

what even is
barriers.exefor?@Northbadge commented on GitHub (Jun 7, 2021):
+1 on this issue, finally got around to figuring out what's been eating away at my memory, I had the same excessive page table entries as shown above. For me it was over 1GB of memory for 5 days of uptime (computer put to sleep every night)
@pstaubs commented on GitHub (Jun 10, 2023):
Just experiencd this today. This is a critically serious issue. Is development of this app dead?