Closed Bug 526309 Opened 15 years ago Closed 6 years ago

Basic static analysis for memory leaks

Categories

(Developer Infrastructure :: Source Code Analysis, defect)

Product:
Developer Infrastructure
Component:
Source Code Analysis
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: taras.mozilla, Unassigned)

References

Details

Attachments

(2 obsolete files)

Ensure that following new/malloc a variable either escapes(therefore too much hassle to prove anything) or is free()ed.
hello.. I'm a student of SJCE,Mysore. I'd like to take up the Bug 526309 Basic check for memory leak
Assignee: nobody → seema.ankadavar
Attachment #444296 - Flags: feedback?
Comment on attachment 444296 [details] [diff] [review] Script comparing dynamic allocations and deallcations. - Marking the attachment as patch - Including taras' name in the feedback request. - Making the patch description concise.
Attachment #444296 - Attachment description: This code puts dynamicaaly allocated variables in an araay and deallocated variables in another array. checks for any variable that is not deallocated comparing both arrays → Script comparing dynamic allocations and deallcations.
Attachment #444296 - Attachment is patch: true
Attachment #444296 - Attachment mime type: application/javascript → text/plain
Attachment #444296 - Flags: feedback? → feedback?(tglek)
Attachment #444296 - Attachment is obsolete: true
Attachment #444317 - Flags: feedback?(tglek)
Attachment #444296 - Flags: feedback?(tglek)
(In reply to comment #4) > Created an attachment (id=444317) [details] > This code checks for variable pointing to dynamically allocated memory block looks promising, please run this on mozilla and post some results.
Comment on attachment 444317 [details] [diff] [review] This code checks for variable pointing to dynamically allocated memory block waiting on results
Attachment #444317 - Flags: feedback?(tglek)
Whiteboard: [MemShrink]
Taras, I'm highly skeptical that the attached patch can produce anything useful. What do you think? Should we close this bug? There are other tools like cppcheck that statically detect leaks.
Summary: Basic check for memory leaks → Basic static analysis for memory leaks
Comment on attachment 444317 [details] [diff] [review] This code checks for variable pointing to dynamically allocated memory block This is a valid static analysis bug, this patch is not useful. This should not be part of memshrink.
Attachment #444317 - Attachment is obsolete: true
Whiteboard: [MemShrink]
Product: Core → Firefox Build System
Anyone working on this?
Flags: needinfo?(taras.mozilla)
Taras isn't working at Mozilla anymore and I don't think there is anyone working on it!
Flags: needinfo?(taras.mozilla)
Assignee: seema.ankadavar → nobody
I no longer see the point of this bug since now we have Coverity Analysis that is going o be integrated at review phase. Sylvestre I propose that we should close it.
Flags: needinfo?(sledru)
Agreed, closing
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(sledru)
Resolution: --- → WONTFIX
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: