Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The CPU of mitmproxy deployed by docker is too high, reaching 100%! #6919

Closed
tl31707chy opened this issue Jun 12, 2024 · 3 comments
Closed
Labels
kind/triage Unclassified issues

Comments

@tl31707chy
Copy link

Problem Description

I used docker to deploy mitmproxy, and when the client connected to the server, there would be a wx request that kept transmitting data, causing the server CPU to quickly reach 100%.

Steps to reproduce the behavior:

Dockerfile

FROM python:3.10

ENV LANG C.UTF-8

WORKDIR /workspace
RUN mkdir "/workspace/mitmproxy"

COPY main.py /workspace/mitmproxy

EXPOSE 8080
EXPOSE 8081

RUN pip install -i https://pypi.mirrors.ustc.edu.cn/simple/ mitmproxy

Execute commands in the container

mitmweb

I have tried mitmproxy and mitmdump both have this situation

20240612233201

@tl31707chy tl31707chy added the kind/triage Unclassified issues label Jun 12, 2024
@mhils
Copy link
Member

mhils commented Jun 12, 2024

This looks like you are capturing traffic to mitmweb itself as well, which creates an infinite loop (WS message about new traffic causes another new message, etc.)

@tl31707chy
Copy link
Author

This looks like you are capturing traffic to mitmweb itself as well, which creates an infinite loop (WS message about new traffic causes another new message, etc.)

Yes, I have tried mitmproxy/mitmproxy mirror with the same problem, which has been bothering me for a few days.

@mhils
Copy link
Member

mhils commented Jun 13, 2024

This is a misconfiguration on your end, not a mitmproxy bug. You need to make it so that accessing the web does not go through the proxy.

@mhils mhils closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/triage Unclassified issues
Projects
None yet
Development

No branches or pull requests

2 participants