Closed Bug 429284 Opened 16 years ago Closed 14 years ago

Leak: sun-calendar-event-dialog-freebusy.xml

Categories

(Calendar :: Dialogs, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dbo, Unassigned)

References

Details

(Keywords: memory-leak)

Using the leak monitor, a leak report occurs when closing the invitation pane:

Leaks in window 0x1ddbc98:
[+] [leaked object] (108ae6f8) = [Object]
 [ ] row = 1
 [+] binding (1e4cd78) = [XULElement]
  [ ] mContentHeight = 323
  [ ] mRowHeight = 17
  [ ] mNumColumns = 1
  [ ] mMaxFreeBusy = 2
  [ ] mPendingRequests (1f10c80) = [Array]
  [ ] mStartDate (10898e90) = [calDateTime]
  [ ] mEndDate (10898e10) = [calDateTime]
  [ ] mScrollOffset = 0
  [ ] mRange = 16
  [ ] mStartHour = 8
  [ ] mEndHour = 17
  [ ] mForce24Hours = false
  [ ] mZoomFactor = 100
 [+] onResult (108ae6e8, chrome://calendar/content/sun-calendar-event-dialog-freebusy.xml, 1318-1328) = [Function]
  [ ] prototype (1bc0ba8) = [Object]
Flags: wanted-calendar0.9+
Flags: wanted-calendar0.9+ → blocking-calendar0.9+
Flags: blocking-calendar0.9+ → wanted-calendar0.9+
Fixed by bug 449177.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.9
Depends on: 449177
I checked this issue with leak monitor using lightning 2008081219 and I get this message after closing the attendees dialog.

Leaks in window 0x2a47650:
[+] [leaked object] (31db030) = [Object]
 [+] observe (31db010, chrome://calendar/content/sun-calendar-event-dialog-attendees.xml, 121-127) = [Function]
  [ ] prototype (25fe3d8) = [Object]

I think this issue isn't completely fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Flags: wanted-calendar0.9+ → wanted-calendar1.0+
Status: REOPENED → NEW
Target Milestone: 0.9 → ---
Component: General → Dialogs
QA Contact: general → dialogs
This no longer occurs for me, closing WFM
Status: NEW → RESOLVED
Closed: 16 years ago14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.