Opened 8 years ago

Closed 8 years ago

#1360 closed defect (fixed)

check leak in logging library and log4cplus

Reported by: jinmei Owned by: UnAssigned
Priority: medium Milestone: Sprint-20111122
Component: logging Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 1.5 Internal?: no

Description

Apparently we have memory leak around the logging system
(see the "BTW" note of #1359). We should check whether there's
leak in our C++ wrapper for log4cplus or in log4cplus itself
(also as noted in #1359, there's a stackoverflow comment that
log4cplus has leak).

Subtickets

Change History (8)

comment:1 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 5

comment:2 Changed 8 years ago by jelte

  • Milestone changed from Next-Sprint-Proposed to Sprint-20111122

comment:3 Changed 8 years ago by jinmei

I've done similar tests as I did for #1359 for C++ liblog:

    while (true) {
        LOG_DEBUG(logger, DBG_TRACE_DETAILED, DATASRC_DATABASE_ITERATE_END);
    }

and didn't see any apparent leak.

So I'm planning to just close this ticket after leaving it in the
review queue for a while.

comment:4 Changed 8 years ago by jinmei

  • Owner set to UnAssigned
  • Status changed from new to reviewing

comment:5 Changed 8 years ago by vorner

Hello

I agree. Let's be optimistic and believe that there's no problem unless we have an indication otherwise. We can always reopen or create a new ticket if it turns out it leaks somewhere.

comment:6 follow-up: Changed 8 years ago by stephen

I also checked:

  • logging to a selection of loggers and with different severities.
  • creating and destroying the logger objects multiple times.

... and didn't see any apparent leak either.

comment:7 in reply to: ↑ 6 Changed 8 years ago by jinmei

Replying to stephen:

I also checked:

  • logging to a selection of loggers and with different severities.
  • creating and destroying the logger objects multiple times.

... and didn't see any apparent leak either.

Okay, closing.

comment:8 Changed 8 years ago by jinmei

  • Resolution set to fixed
  • Status changed from reviewing to closed
  • Total Hours changed from 0 to 1.5
Note: See TracTickets for help on using tickets.