Home/ Questions/Q 1007961
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T08:41:50+00:00

For some reason, my paintComponent(Graphics g) method is being called infinitely. I can’t seem

  • 0

For some reason, my paintComponent(Graphics g) method is being called infinitely. I can’t seem to tell who is calling it, even if I dump a StackTrace in the call (it’s an event that’s dispatched and handled).

Are there any easy ways to find out who’s triggering the event?

Update: I’ve found the cause and I now understand the reason. Whoever answers it correctly will get the answer to the question.

Here is the code that’s causing the issue:

@Override
public void paintComponent(Graphics g)
{
    myJButton.setIcon(ResourceLoader.getImageIconWithLocale(MY_BUTTON_IMAGE));
    super.paintComponent(g);
}

FYI: It’s a really tricky one!! It’s not obvious by looking at the code. I made an assumption that was wrong.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The setIcon(ImageIcon) will revalidate and repaint itself ONLY if the ImageIcon is another instance.

    When working with Locales, most people are use to the ResourceBundle, which returns Strings, which in turn are immutable. Therefore setting the text over and over doesn’t matter.

    However, in this case, the ResourceLoader (custom class) returned a new instance of an ImageIcon. Sure it was the same Image, but it was another instance. And if you decompile the code, you’ll see that setIcon (at least for JButtons), it will repaint and revalidate if newIcon != oldIcon.

    The solution was to use a HashMap in the ResourceLoader, this way it saves from loading the images more than once since most of the images are used very frequently (might as well reuse the instances if you can). Turns out that overall this quick adjustment also saved a decent amount of overall memory consumption as an added bonus.

    • 0