Re: kolccst obj: large streams pool memory segment
- From: "Charles Schultz" <sacrophyte@xxxxxxxxx>
- To: "Rajeev Prabhakar" <rprabha01@xxxxxxxxx>
- Date: Thu, 4 Oct 2007 10:53:18 -0500
Any workaround? I am curious if turning off the evil ASMM will bypass the
issue or not. Surely we can set hard memory limits, but does that have other
ramifications for this Streams-specific bug?
On 10/4/07, Rajeev Prabhakar <rprabha01@xxxxxxxxx> wrote:
>
> Charles
>
> From what I could find, it looks like the "kolccst obj" are used to
> maintain the streams heap collection.
>
> Rajeev
>
--
Charles Schultz
Other related posts:
