Chris,
The excas that is supplied with R3.14.2 was leak tested in purify prior to its
release. I just finished running the regression tests against it twice and the
memory consumption appears to follow a high water mark behavior and not a
steadily increasing ramp as is typically the case with memory leaks.
But that is only how the software was tested. Your situation may be different.
Perhaps I will be able to reproduce your problem if I have more details about
your situation:
o OS version?
o I assume that this is all linked with EPICS R3.14 libraries?
o Perhaps there is something special about how the clients use this server?
o If the changes are small perhaps some diffs between the stock excas and your
version will help?
PS:
Be careful that GDDs are properly unreferenced when you are done using them.
Jeff
> -----Original Message-----
> From: Chris Timossi [mailto:[email protected]]
> Sent: Monday, July 21, 2003 12:35 PM
> To: [email protected]
> Subject: memory leak in excas?
>
>
> Has anyone experienced a memory leak in the server tool example 'excas'?
>
> I'm trying to run down a leak in my application that's based on that
> example. The leak seems to be in exScalar.cc in the scan routine.
>
> I'm running on solaris and R3.14.2. I'm restarting the application once
> a
> day as a 'workaround'.
>
> Chris Timossi
- Replies:
- RE: memory leak in excas? Chris Timossi
- References:
- memory leak in excas? Chris Timossi
- Navigate by Date:
- Prev:
memory leak in excas? Chris Timossi
- Next:
Applications Software Engineer paul heelas
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
memory leak in excas? Chris Timossi
- Next:
RE: memory leak in excas? Chris Timossi
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|