Opened 7 years ago
Closed 3 years ago
#9042 closed defect (user disappeared)
Too resource hungry
Reported by: | myopenid | Owned by: | ioerror |
---|---|---|---|
Priority: | Medium | Milestone: | Tor: unspecified |
Component: | Core Tor/Tor | Version: | Tor: 0.2.3.25 |
Severity: | Normal | Keywords: | tor-relay memory cpu resource |
Cc: | Actual Points: | ||
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
After a few hours of running Tor it uses up all CPU cycles and unusual amount of memory, in the range of 120Mbytes, regardless of traffic condition, which is, at the time of observation 1Kbytes/s.
It is running on Ubuntu 12.10 VPS, and is configured to run as an exit node.
Once the log showed "Error creating network socket: No buffer space available
", even though there is still 300Mbytes of free memory.
Now, attempt to restart, reinstall Tor does not solve the problem.
Child Tickets
Attachments (1)
Change History (5)
Changed 7 years ago by
comment:1 Changed 7 years ago by
Component: | Torouter → Tor |
---|
comment:2 Changed 6 years ago by
Milestone: | → Tor: unspecified |
---|---|
Status: | new → needs_information |
Version: | Tor: 0.2.2.35 → Tor: 0.2.3.25 |
comment:3 Changed 6 years ago by
Keywords: | tor-relay memory cpu resource added |
---|
comment:4 Changed 3 years ago by
Resolution: | → user disappeared |
---|---|
Severity: | → Normal |
Status: | needs_information → closed |
Note: See
TracTickets for help on using
tickets.
Are recent 0.2.4 versions any better here?
What kind of a configuration is this?
Have you tried using 'perf' or 'oprofile' to see where Tor is spending its time?
It might also be a good idea to ask on the tor-relays mailing list whether other people have seen similar issues, and if so what they did to solve them.