Opened 17 months ago

Last modified 8 months ago

#30729 new defect

Possible memory leak in torsocks 2.2.0

Reported by: adYpc Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torsocks Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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/

Child Tickets

Change History (2)

comment:1 Changed 17 months ago by gaba

Owner: dgoulet deleted
Status: newassigned

removing dgoulet from ownership in torsocks component

comment:2 Changed 8 months ago by teor

Status: assignednew

Change tickets that are assigned to nobody to "new".

Note: See TracTickets for help on using tickets.