Closed Bug 94772 Opened 24 years ago Closed 23 years ago

Potential memory leak - nsRenderingContextOS2::CopyClipRegion

Categories

(Core :: XUL, defect)

Product:
Core
Component:
XUL
Platform:
x86
OS/2
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: aaronr, Assigned: mkaply)

Details

I was looking at gfx\src\os2\nsRenderinContextOS2.cpp and found a potential bug. In nsRenderingContextOS2::CopyClipRegion, we call OS2_CopyClipRegion, but we don't do anything with the region that we've created. We definitely don't clean it up. I think that we either need to make this a stub function. Right now I don't see where we ever use this, instead we use OS2_CopyClipRegion. But we need to stub this out so that if it is ever used, some kind of assert will happen so that the user knows that this isn't implemented. In the very least, we need to not call something that allocates a region that never gets freed up.
-> mkaply
Assignee: trudelle → mkaply
Summary: Potential memory leak → Potential memory leak - nsRenderingContextOS2::CopyClipRegion
May God have mercy on us all. The 212 bug spam-o-rama is Now!
QA Contact: aegis → jrgm
This was fixed. The function asserts if it is ever used.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.