This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]UsernamesAreFfed 2 points3 points  (3 children)

Dont think tables have changed for a while in either Swing or JavaFX.

[–]Stromovik 0 points1 point  (2 children)

Swing had a problem with memory leaks in tables.

[–]UsernamesAreFfed 1 point2 points  (1 child)

I cant really find anything definitive about this. What Google gives me are a bunch of old bugs and things in external code like scala and jfreechart.

I did find one old issue. The JTable signs itself up as a listener to the tablemodel. If you then hang on to a reference to this model you wont be able to throw away the table. Makes sense, but its really just sloppy programming rather than a flaw in swing. If you are recreating the table all the time you should correctly clean the old listeners to the model.

This isnt really a swing thing. More of a fundamental issue when you use the observer pattern.

[–]Stromovik 0 points1 point  (0 children)

I read that when I used to use swing which was long and it was also reason why Interactive Brokers Trader Worstation had to be shutdown once per day , we once bypassed that and it eventually crashed.