Opened 6 years ago

Last modified 5 months ago

#10371 new defect

Obfsproxy memory leak

Reported by: taher12112 Owned by:
Priority: Medium Milestone:
Component: Archived/Obfsproxy Version:
Severity: Normal Keywords: obfsproxy
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi everyone,

I have installed Obfsproxy from Tor project Debian and Python repositories (one v0.2.3 and the other v0.2.4) on my Ubuntu 12.04 LTS. Unfortunately both of them has memory leak problem and if too many users start using the server, it makes the RAM full and crashes by itself. How can I generate a full report from this memory leak and place it here to help developers fix the issue?

Thanks.

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by asn

Priority: criticalnormal
Status: newneeds_information

Hm, does this still happen?

What kind of machine is this? How much RAM does obfsproxy take?

comment:2 Changed 5 years ago by asn

Yawning says that this might be related to #11197.

comment:3 Changed 3 years ago by htfy96

Severity: Normal

This also happens on my VPS.

System: Linux 2.6.32-042stab102.9 #1(OpenVZ) SMP Fri Dec 19 20:34:40 MSK 2014 x86_64 GNU/Linux
Distribution: Debian GNU/Linux 8 (jessie)

Obfsproxy was installed by pip install obfsproxy, and the version is 0.2.13.

How to reproduce it:

nohup obfsproxy --data-dir=/tmp/scramblesuit-server scramblesuit --password=.... --dest=public-ip-of-VPS:2507 server public-ip-of-VPS:25070 &

Usually the program would occupy around 150MB memory after a whole day, and crashes after 2 or 3 days.

I also set --log-file=obfsproxy.log --log-min-severity warning, but it seems that no information was recorded before crash:

2016-02-03 00:53:54,028 [WARNING] Obfsproxy (version: 0.2.13) starting up.
2016-02-03 00:53:54,028 [ERROR] 

################################################
Do NOT rely on ScrambleSuit for strong security!
################################################

2016-02-03 18:24:49,026 [WARNING] The HMAC was already present in the replay table.
2016-02-05 19:37:02,197 [WARNING] The HMAC was already present in the replay table.
# 2016-02-08 around 00:00 it crashed
# Manually restart it
2016-02-08 00:14:01,662 [WARNING] Obfsproxy (version: 0.2.13) starting up.
2016-02-08 00:14:01,663 [ERROR] 

################################################
Do NOT rely on ScrambleSuit for strong security!
################################################

comment:4 Changed 5 months ago by cohosh

Status: needs_informationnew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.