Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Torsocks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Torsocks
  • Issues
  • #30729

Closed
Open
Created Jun 02, 2019 by Trac@tracbot

Possible memory leak in torsocks 2.2.0

valgrind found a possible memory leak in torsocks 2.2.0:

==29922== 79 bytes in 8 blocks are definitely lost in loss record 17 of 68
==29922==    at 0x483579F: malloc (vg_replace_malloc.c:309)
==29922==    by 0x569344A: strdup (strdup.c:42)
==29922==    by 0x484D82A: utils_tokenize_ignore_comments (utils.c:146)
==29922==    by 0x484CF88: parse_config_line (config-file.c:134)
==29922==    by 0x484CF88: parse_config_file (config-file.c:218)
==29922==    by 0x484D423: config_file_read (config-file.c:567)
==29922==    by 0x484797E: init_config (torsocks.c:163)
==29922==    by 0x484797E: tsocks_init (torsocks.c:328)
==29922==    by 0x484DFA5: tsocks_once (compat.c:94)
==29922==    by 0x400F259: call_init.part.0 (dl-init.c:72)
==29922==    by 0x400F358: call_init (dl-init.c:30)
==29922==    by 0x400F358: _dl_init (dl-init.c:119)
==29922==    by 0x40010C9: ??? (in /lib64/ld-2.29.so)

Trac:
Username: adYpc

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