Closed
Bug 114646
Opened 23 years ago
Closed 22 years ago
The setenv/putenv calls leak
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: gray, Assigned: gray)
References
Details
(Keywords: memory-leak)
The setenv/putenv calls in libical leaks (quite badly). The libical is moving
away from using setenv, but I think we still need to do something to prevent the
calls from leaking if we can.
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•22 years ago
|
||
Default QA Contact for Calendar has changed. If you wish to remain the QA
contact for this bug, feel free to change it back.
QA Contact: colint → brantgurganus2001
Comment 3•22 years ago
|
||
I'm going to resolve this as won't fix, since I don't think anyone is working on it.
It may be fixed in libical 0.24. libical bugs should be moved to libical's bug
repository.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Updated•19 years ago
|
QA Contact: gurganbl → libical
Updated•19 years ago
|
Component: libical → Internal Components
Comment 5•19 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base
You need to log in
before you can comment on or make changes to this bug.
Description
•