We created concurrent remote connections and checked shared memory that remained constant after Patch apply which is not the case before patch apply.
This sounds like a completely new set of previously undisclosed symptoms.
How did you check that "shared memory remained constant"? What tool did you use to do this and what numbers are you observing? (Shared memory usage is not something that is trivially observed -- so the tool that you used and the metric in question will tell us a lot about whether or not you are really seeing what you think you are seeing. Of course the very nature of shared memory is that it is *shared* which means that it generally gets allocated up front and everyone uses it -- it doesn't grow or shrink as connections are made and a "leak" isn't really a sensible notion.)
What were the previous non-constant values?
Apparently creating "concurrent remote connections" is your hypothesized root cause for a "memory leak". In the pre-patch scenario how does creating these connections correlate to increased shared memory usage? (What metric changes by how much when you add remote connections?) How does that metric change when remote connections are closed?
Does your test involve anything other than opening and closing connections? IOW do they do any work? Did you run the
same tests pre-patch?
This lead us to that the memory leak is resolved.
Please pardon my skepticism but I doubt it. So far you haven't really described anything that would fit that description.