mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 00:25:56 +03:00
[GH-ISSUE #1535] Browsers are slow in loading pages. #1527
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1527
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 @dbarros on GitHub (Feb 10, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1535
I've noticed that when I run Proxyman, the loading of sites becomes very slow -- sometimes where a page will not load at all. Sometimes things kick back in, and work as normal. But more often than not, performance is slow. When I quit Proxyman, all's back to its speedy self.
I've experience this both with Chrome and Firefox (latest versions), on macOS 12.6.
I'm looking at the traffic of one domain, which I've added the the SSL Proxying List. So I am able to see HTTPS traffic as decrypted plaintext.
Is there something that I may not have done when it comes to configuring Proxyman for this scenario?
@NghiaTranUIT commented on GitHub (Feb 10, 2023):
Not sure what Proxyman version you're using? Do you use the latest 4.2.0?
Can you try on 4.1.0 (Download at https://download.proxyman.io/41000/Proxyman_4.1.0.dmg), because I'm working on a similar bug on the 4.2.0
@dbarros commented on GitHub (Feb 10, 2023):
@NghiaTranUIT Thanks for the response. I tried 4.1.0, and I am not experiencing any slowdown like I was with the latest version.
@NghiaTranUIT commented on GitHub (Feb 10, 2023):
Thanks. Then, you can update to the latest build 4.2.1 (which I released hours ago). It's fixed the bug on 4.2.0 👍