We are using slogger to do a fair bit of logging in an application. We have
found that if we leave a terminal session running sloginfo -w for long
periods of time it will consume more and more memory. Stopping sloginfo
(cntl-c) does not release the memory - but terminating the terminal window
does.
We are running 6.1.
Is this a known problem?
Mike Nunan
Hi Michael,
I reproduced this here, however its actually slogger that is leaking
the memory and not sloginfo. I’ll take a quick look and see if the
lastest version fixes this and if there is something that was missed
in the code that I can quickly fix. Then I will file a PR against it.
Best regards,
Erick
Michael Nunan <m.nunan@ieee.ca> wrote:
We are using slogger to do a fair bit of logging in an application. We have
found that if we leave a terminal session running sloginfo -w for long
periods of time it will consume more and more memory. Stopping sloginfo
(cntl-c) does not release the memory - but terminating the terminal window
does.We are running 6.1.
Is this a known problem?
Mike Nunan
Hi Michael,
I checked out the source from the head branch and found that the issue
was fixed in the latest release.
I will see wether or not it can get into the 6.2.1 patch.
Best regards,
Erick
Hardware Support Account <hw@qnx.com> wrote:
Hi Michael,
I reproduced this here, however its actually slogger that is leaking
the memory and not sloginfo. I’ll take a quick look and see if the
lastest version fixes this and if there is something that was missed
in the code that I can quickly fix. Then I will file a PR against it.Best regards,
Erick
Michael Nunan <> m.nunan@ieee.ca> > wrote:
We are using slogger to do a fair bit of logging in an application. We have
found that if we leave a terminal session running sloginfo -w for long
periods of time it will consume more and more memory. Stopping sloginfo
(cntl-c) does not release the memory - but terminating the terminal window
does.We are running 6.1.
Is this a known problem?
Mike Nunan
Thanks - what is the actual effect of this leak. We are using slogger
significantly!
Will we run out of memory eventually even if we do not run sloginfo?
In which version is ther problem corrected "i.e. what is “the latest
release” refered to below?
Mike
“Hardware Support Account” <hw@qnx.com> wrote in message
news:asq9g7$rqn$2@nntp.qnx.com…
Hi Michael,
I checked out the source from the head branch and found that the issue
was fixed in the latest release.I will see wether or not it can get into the 6.2.1 patch.
Best regards,
Erick
Hardware Support Account <> hw@qnx.com> > wrote:
Hi Michael,I reproduced this here, however its actually slogger that is leaking
the memory and not sloginfo. I’ll take a quick look and see if the
lastest version fixes this and if there is something that was missed
in the code that I can quickly fix. Then I will file a PR against it.Best regards,
Erick
Michael Nunan <> m.nunan@ieee.ca> > wrote:
We are using slogger to do a fair bit of logging in an application. We
have
found that if we leave a terminal session running sloginfo -w for long
periods of time it will consume more and more memory. Stopping sloginfo
(cntl-c) does not release the memory - but terminating the terminal
window
does.We are running 6.1.
Is this a known problem?
Mike Nunan
Hi Mike,
It was a ocb memory leak that occured with the opening and closing of
/dev/slog.
So if you don’t use sloginfo on a heavy basis you should be ok, so
perhaps they may be another way for you to do your logging.
I checked into this and this won’t make the 6.2.1 release, however if
this is something that you need fixed you can talk to your sales rep or
if you have a bronze support plan or higher you can have this issue
escalated with the support team.
Best regards,
Erick
Michael Nunan <m.nunan@ieee.ca> wrote:
Thanks - what is the actual effect of this leak. We are using slogger
significantly!Will we run out of memory eventually even if we do not run sloginfo?
In which version is ther problem corrected "i.e. what is “the latest
release” refered to below?Mike
“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:asq9g7$rqn$> 2@nntp.qnx.com> …
Hi Michael,I checked out the source from the head branch and found that the issue
was fixed in the latest release.I will see wether or not it can get into the 6.2.1 patch.
Best regards,
Erick
Hardware Support Account <> hw@qnx.com> > wrote:
Hi Michael,I reproduced this here, however its actually slogger that is leaking
the memory and not sloginfo. I’ll take a quick look and see if the
lastest version fixes this and if there is something that was missed
in the code that I can quickly fix. Then I will file a PR against it.Best regards,
Erick
Michael Nunan <> m.nunan@ieee.ca> > wrote:
We are using slogger to do a fair bit of logging in an application. We
have
found that if we leave a terminal session running sloginfo -w for long
periods of time it will consume more and more memory. Stopping sloginfo
(cntl-c) does not release the memory - but terminating the terminal
window
does.We are running 6.1.
Is this a known problem?
Mike Nunan
In one of our Driver implementations for our own FrameGrabber’ we are using
slog() to capture acquisition runtime information. Normally we will not run
sloginfo, we instruct our customers after a failure to run this for use and
capture any of our error messages. I have yet to run across this “memory
leak” though. We are currently configuring our embedded board to use 98% of
the available memory. (Slog is running on a RAM disk as well). Can you give
any info on the size of the leak that a single call would give? We are
still on 6.1A for the time being.
Thank you
Jeff
–
Jeffrey B. Holtz
Software Engineering
Electro Scientific Industries, Inc.
Ph: 734-332-7054
Fax: 734-332-7077
email: holtzj@esi.com
“Hardware Support Account” <hw@qnx.com> wrote in message
news:av4th7$l2d$2@nntp.qnx.com…
Hi Mike,
It was a ocb memory leak that occured with the opening and closing of
/dev/slog.So if you don’t use sloginfo on a heavy basis you should be ok, so
perhaps they may be another way for you to do your logging.I checked into this and this won’t make the 6.2.1 release, however if
this is something that you need fixed you can talk to your sales rep or
if you have a bronze support plan or higher you can have this issue
escalated with the support team.Best regards,
Erick
Michael Nunan <> m.nunan@ieee.ca> > wrote:
Thanks - what is the actual effect of this leak. We are using slogger
significantly!Will we run out of memory eventually even if we do not run sloginfo?
In which version is ther problem corrected "i.e. what is “the latest
release” refered to below?Mike
“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:asq9g7$rqn$> 2@nntp.qnx.com> …
Hi Michael,I checked out the source from the head branch and found that the issue
was fixed in the latest release.I will see wether or not it can get into the 6.2.1 patch.
Best regards,
Erick
Hardware Support Account <> hw@qnx.com> > wrote:
Hi Michael,I reproduced this here, however its actually slogger that is leaking
the memory and not sloginfo. I’ll take a quick look and see if the
lastest version fixes this and if there is something that was missed
in the code that I can quickly fix. Then I will file a PR against
it.Best regards,
Erick
Michael Nunan <> m.nunan@ieee.ca> > wrote:
We are using slogger to do a fair bit of logging in an application.
We
have
found that if we leave a terminal session running sloginfo -w for
long
periods of time it will consume more and more memory. Stopping
sloginfo
(cntl-c) does not release the memory - but terminating the terminal
window
does.We are running 6.1.
Is this a known problem?
Mike Nunan
\