Sat4j
  1. Sat4j
  2. SAT-55

Fix memory leak in case of repeated use of Sat4j in an application

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.1
    • Fix Version/s: 2.3.2
    • Component/s: core
    • Security Level: Public (Everybody can see)
    • Labels:
      None

      Description

      In an application creating new solvers on user's action, the consumption of memory is growing.
      It looks like there is a memory leak somewhere.

        Activity

        Hide
        Daniel Le Berre added a comment -

        I think I got the origin of the problem.
        The solver uses a thread with a timer to stop the solver.
        That timer was not set to null when the solver was reset, so a thread was keeping a reference to the solver object, thus preventing garbage collection.
        It looks like the problem is now solved.
        Please confirm.

        Show
        Daniel Le Berre added a comment - I think I got the origin of the problem. The solver uses a thread with a timer to stop the solver. That timer was not set to null when the solver was reset, so a thread was keeping a reference to the solver object, thus preventing garbage collection. It looks like the problem is now solved. Please confirm.
        Hide
        Daniel Le Berre added a comment -

        reporting user confirmed that the problem has been solved.

        Show
        Daniel Le Berre added a comment - reporting user confirmed that the problem has been solved.

          People

          • Assignee:
            Daniel Le Berre
            Reporter:
            Daniel Le Berre
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development