Weird behaviour on error conditions

Create issue
Issue #60 resolved
Tygre repo owner created an issue
cache_file_name = \mods\boray
cache_file_path = ENVARC:AmiModRadioCache/Aminet\mods\boray
cache_file_name = \mods\boray
cache_file_path = ENVARC:AmiModRadioCache/Aminet\mods\boray
cache_file_name = \
cache_file_path = ENVARC:AmiModRadioCache/Modules.pl\
cache_file_name = \
cache_file_path = ENVARC:AmiModRadioCache/Modules.pl\

Fortify: Memory leak detected leaving scope at main.c.157
   Address     Size Allocator
0x686cc1fc      175 http.c.381
0x686cc15c       48 http.c.1280
0x686cc0d4       27 http.c.1256
0x686cc004       98 utils.c.427
0x686cbf84       15 http.c.1409
0x686cbf14        3 http.c.1224
0x686cbe94       16 http.c.1189
0x686cbe1c        5 http.c.1053
0x686cbd84       40 http.c.1005
0x68e24aa4      175 http.c.381
0x68e24594       48 http.c.1280
0x68e2450c       27 http.c.1256
0x68e2443c       98 utils.c.427
0x68e243bc       15 http.c.1409
0x68e2434c        3 http.c.1224
0x68e242cc       16 http.c.1189
0x68e24254        5 http.c.1053
0x68e241bc       40 http.c.1005
0x6949bdf4      151 http.c.381
0x6949bd6c       27 http.c.1280
0x6949bce4       28 http.c.1256
0x6949bc2c       74 utils.c.427
0x6949b204       15 http.c.1409
0x6949b194        3 http.c.1224
0x6949b11c       12 http.c.1189
0x6949b0a4        5 http.c.1053
0x6949b00c       40 http.c.1005
0x68e1ab24      175 http.c.381
0x68e1aa84       48 http.c.1280
0x68e1a9fc       27 http.c.1256
0x68e1a92c       98 utils.c.427
0x68e1a8ac       15 http.c.1409
0x68e1a83c        3 http.c.1224
0x68e1a7bc       16 http.c.1189
0x68e1a744        5 http.c.1053
0x68e1a6ac       40 http.c.1005
     total     1636 bytes in 36 blocks with 3744 bytes overhead

Fortify: Statistics at main.c.158
         Memory currently allocated: 1636 bytes in 36 blocks
         Maximum memory allocated at one time: 9838069 bytes in 197 blocks
         There have been 58017 allocations and 57981 deallocations
         There was a total of 1908414496 bytes allocated
         The average allocation was 32894 bytes

Comments (4)

  1. Tygre reporter
    • edited description
    • changed status to resolved

    The problem was with the connection... besides, the cache now use multi-OS friendly separator ('+' instead of '\').

  2. Log in to comment