Re: Freeradius 2.2.0 memory leak issue.

kao quadrantx wrote: > new log with radiusd -m Which still shows for many symbol names. Are you sure you're running the latest v2.x.x from git? Please try to simplify the issue down to a small configuration, and email it to me. That will let me reproduce the problem, and fix it. Ala

Re: Freeradius 2.2.0 memory leak issue.

kao quadrantx wrote: > Hi, > > i rebuild freeradius with the latest updated on git v2.x.x and attach > the valgrind log. > If you need anything else, please feel free to ask me. Did you run with "radiusd -m" ? That is needed in order to get the debugging symbols in the modules. Alan DeKok.

Re: Freeradius 2.2.0 memory leak issue.

Hi, i rebuild freeradius with the latest updated on git v2.x.x and attach the valgrind log. If you need anything else, please feel free to ask me. Thanks a lot :) On Thu, Mar 7, 2013 at 10:32 PM, Alan DeKok wrote: > kao quadrantx wrote: > > i rebuild freeradius with the latest updated today (i

Re: Freeradius 2.2.0 memory leak issue.

kao quadrantx wrote: > i rebuild freeradius with the latest updated today (i noticed the > userparse() in valuepair.c has updated) and the memory leak still the same. > (same memory growth in VmRSS and same valgrind log.) OK. > FR_TOKEN userparse(const char *buffer, VALUE_PAIR **list) Why?

Re: Freeradius 2.2.0 memory leak issue.

Sorry, update the userparse() i use is: FR_TOKEN userparse(const char *buffer, VALUE_PAIR **first_pair) { VALUE_PAIR *vp, *head, **tail; const char *p; FR_TOKEN last_token = T_OP_INVALID; FR_TOKEN previous_token; /* * We allow an empty line. */ if (buffer[0] == 0) return T_EOL; head = NULL; t

Re: Freeradius 2.2.0 memory leak issue.

Hi, i rebuild freeradius with the latest updated today (i noticed the userparse() in valuepair.c has updated) and the memory leak still the same. (same memory growth in VmRSS and same valgrind log.) FR_TOKEN userparse(const char *buffer, VALUE_PAIR **list) { VALUE_PAIR *vp, *head, **

Re: Freeradius 2.2.0 memory leak issue.

kao quadrantx wrote: > I try to test with the latest version of freeradius in git 2.x.x and > still get the same behavior. $ git pull Then rebuild. > Seems the envp variable in radius_exec_program function (exec.c) not clean? No. It looks like the userparse() function isn't cleaning up pro

Re: Freeradius 2.2.0 memory leak issue.

On 06.03.2013 11:43, kao quadrantx wrote: > Hi, > > I try to test with the latest version of freeradius in git 2.x.x and > still get the same behavior. > Seems the envp variable in radius_exec_program function (exec.c) not clean? > To help the developers to identify the bug, could you follow the

Re: Freeradius 2.2.0 memory leak issue.

Hi, I try to test with the latest version of freeradius in git 2.x.x and still get the same behavior. Seems the envp variable in radius_exec_program function (exec.c) not clean? PS: my system is 64bit. valgrind log below: ==3043== 13,852 (368 direct, 13,484 indirect) bytes in 2 blocks are defin

Re: Freeradius 2.2.0 memory leak issue.

Hi, >i download from here http://freeradius.org/download.html >Version 2.2.0: tar.gz (PGP Signature) >This version should be the latest version. Am i right? as per the download page: http://git.freeradius.org/ that will be the 'latest 2.2.x version' 2.2.0 is the latest RELEASE ve

Re: Freeradius 2.2.0 memory leak issue.

Hi Alan, i download from here http://freeradius.org/download.html Version 2.2.0: tar.gz (PGP Signature) This version should be the latest version.

Re: Freeradius 2.2.0 memory leak issue.

Have you tried the latest 2.2 GIT release? Many code updates alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Freeradius 2.2.0 memory leak issue.

Hi, i got the same issue in freeradius memory issue http://freeradius.1045715.n5.nabble.com/Memory-leak-in-FR-2-1-10-and-2-2-0-tt5717545.html#a5717576 My test ENV: eapol_test with md5 to do AUTH (client) -> freeradius 2.2.0 to proxy the client request (proxy)