I had this problem for about seven years. It had to be tackled, but until
just now I had more pressing problems revolving around getting my
application to work. I feared learning the profiler and solving this
problem. I thought the process would be a distraction that I didn't want to
deal with; I s
I'd just like to let you know that I solved my CPU load and socket
stability problems by removing a call I was making to System.gc() I put in
when I was trying to solve the problem earlier. I've been running my
application now for about 30 minutes, and the profiler shows that no
instances survive o
Hello Leo.
On Sun, 25 Nov 2018 at 08:29, Leo Donahue wrote:
> Maybe this helps?
>
> SER10-J
>
> https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=88487787
>
>
Still early days yet, but I think a heart-felt thank you might be in order
here.
Resetting the output stream after writin
te:
>>
>>> Looks like I'm getting confused and dismayed with my attempts to run the
>>> profiler. Any help from any NetBeans user would be appreciated.
>>>
>>> Thanks,
>>>
>>> Owen.
>>>
>>> -- Forwarded message -
>>
Sounds like there are two issues being discussed here:
1. Memory leak in your application
2. Bug in Netbeans profiler.
For the first one, I don't think anyone can help without the code,
unfortunately. I have found this article to be useful in the past:
https://www.toptal.com/java/hunting-memory-le
used and dismayed with my attempts to run the
>> profiler. Any help from any NetBeans user would be appreciated.
>>
>> Thanks,
>>
>> Owen.
>>
>> -- Forwarded message -
>> From: Owen Thomas
>> Date: Sat, 24 Nov 2018 at 20:11
>>
wrote:
> Looks like I'm getting confused and dismayed with my attempts to run the
> profiler. Any help from any NetBeans user would be appreciated.
>
> Thanks,
>
> Owen.
>
> -- Forwarded message -
> From: Owen Thomas
> Date: Sat, 24 Nov 2018 at 20
