🚀 go-pugleaf

"Zoran Pjevic" <zpjevic@anitesystems.de> wrote in message 
news:mdfb21hrbfafuvk3o6p7ormovgbj64cumo@4ax.com...
> Hello
>
> I not sure that my question is related to Swing, but is is my best
> guess.
>
> We have an Swing based GUI which is on top of a C++ embedded
> application which feeds data into a hardware unit.
>
> In stress testing conditions under very high data rates everything
> runs fine for up to 15 hours. But then occasionaly it happens that the
> hardware gets a datadrop.
>
> When the same test is performed without the GUI, this is not noticed.
>
> So I suppose that the garbage collector is doing incremental
> collecting for hours and hours and then when some limits are reached
> it peforms some major collecting, which slows down the GUI and with it
> the underlying C++ core.
>
> If this is the case - is there any way to programmatically influence
> the schema of how the garbage collector works or at least to get a
> message from the garbage collector when it starts this major
> collecting? Or can I force it to to do its job in the background?
>
> Or do you think I am completely wrong with my interpretation of the
> problem?
>
> Thanks for any hints,
> Zoran

Try calling System.gc() from your GUI application.
I've found if you call it on a periodic basis, major garbage collection
hesitations are minimized (but not eliminated entirely)

regards,
    Dar7yl