Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #105
Closed
Open
Created Feb 28, 2005 by Trac@tracbot

Todays Build - Possible memory leak?

I sync'd and built against CVS this AM - Launched at 6:45 EST. Memory usage is at 25M and climbing.

I suspect a memory leak, but am unsure how to help you find it.

Will it crash at some point and generate a useful core?

I'm on NetBSD 2.0_Stable w/P2-300 256M Ram.

Process limits: clarity 13 -> limit cputime unlimited filesize unlimited datasize 131072 kbytes stacksize 2048 kbytes coredumpsize unlimited memoryuse 251972 kbytes memorylocked 83990 kbytes maxproc 160 openfiles 1648

I'm also getting 6-10 of the following messages per hour: Feb 28 13:55:08.261 [warn] circuit_receive_relay_cell(): connection_edge_process_relay_cell (away from origin) failed. Feb 28 13:55:08.261 [warn] command_process_relay_cell(): circuit_receive_relay_cell (forward) failed. Closing.

[Automatically added by flyspray2trac: Operating System: BSD]

Trac:
Username: yancm

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking