• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.6
    • 2.5.1
    • None
    • None

      Steps taken:
      1. Installed the plugin, added Clover to two projects: one containing a test, another one I wanted to measure the coverage for.
      2. I've run a single JUnit test class with "Run With Clover | As JUnit"
      3. The test ran fine, TestRunExplorer, CoverageExplorer, TestContributions were populated correctly.
      4. But the Eclipse process in OS seemed to take more and more GDI objects (as reported by taskmgr.exe). This led to first Eclipse being not responsive, then even all the other applications having problems to render them correctly. The GDI objects number kept on growing until it reached 10000, which was enough for my computer.

      Note that the GDI objects number keeps on rising without a single click in Eclipse after selecting the "CoverageExplorer" view (about new 8-12 GDI objects each second). Without EclipseForClover no such a problem is observed when running tests.
      Reverting the changes in ".classpath" and ".project" and restarting Eclipse restores the proper behaviour.

            [CLOV-723] GDI objects leak

            Sorry, Michael, for not responding. I didn't get any e-mail notification.
            Thanks for fixing!

            Grzegorz Olędzki added a comment - Sorry, Michael, for not responding. I didn't get any e-mail notification. Thanks for fixing!

            Actually implemented in 2.5.X

            Michael Studman (Inactive) added a comment - Actually implemented in 2.5.X

            Hi Grzegorz,

            I believe I may have found the core of the problem and this will be addressed in Clover 2.5.1 released tomorrow (Thursday 28th). Please let us know if it addresses the problem for you.

            Michael.

            Michael Studman (Inactive) added a comment - Hi Grzegorz, I believe I may have found the core of the problem and this will be addressed in Clover 2.5.1 released tomorrow (Thursday 28th). Please let us know if it addresses the problem for you. Michael.

            Hi Grzegorz ,

            I apologise that you are encountering this problem.

            I can certainly see some GDI resource leaks but I can't see this 8-12 / second behaviour you describe. Could you please turn off the "Look for updated coverage every..." setting (and click Apply) and then see if the constant GDI resource leak continues? I'm wondering if it's related to the scan Clover does every 2s (by default) for new coverage data.

            Thanks.

            Michael

            Michael Studman (Inactive) added a comment - Hi Grzegorz , I apologise that you are encountering this problem. I can certainly see some GDI resource leaks but I can't see this 8-12 / second behaviour you describe. Could you please turn off the "Look for updated coverage every..." setting (and click Apply) and then see if the constant GDI resource leak continues? I'm wondering if it's related to the scan Clover does every 2s (by default) for new coverage data. Thanks. Michael

              mstudman Michael Studman (Inactive)
              4cf38e4cf4c1 Grzegorz Olędzki
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: