The FreeType Project - Bugs: bug #46439, Leak of glyph_name after being...
You are not allowed to post comments on this tracker with your current authentication level.
bug #46439: Leak of glyph_name after being allocated in bdf parser.
Submitter: | bungeman <bungeman> | ||
Submitted: | Fri 13 Nov 2015 09:19:17 PM UTC | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.6.2 |
Mon 16 Nov 2015 03:37:06 PM UTC, comment #2: |
bungeman <bungeman> |
Sun 15 Nov 2015 03:54:29 AM UTC, comment #1: Fixed in git, thanks!
|
Werner LEMBERG <wl> |
Fri 13 Nov 2015 09:19:17 PM UTC, original submission:
Found with libFuzzer at FreeType 75722f89290eb1cb316cd240763545d7277e0481 , reproduction attached.
|
bungeman <bungeman> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-11-15 | wl | Status | None | Fixed | |
Assigned to | None | wl | |||
Open/Closed | Open | Closed | |||
Planned Release | None | 2.6.2 | |||
2015-11-13 | bungeman | Attached File | - | Added ftfuzzer.cc.patch, #35450 | |
Attached File | - | Added crash-b4f5bea86648179bf1759ec1b5a3c5c3ec874463, #35451 |
Powered by Savane 3.13-f8d8.
Corresponding source code
That would probably be a good idea, though I'm not sure what to call such an option nor exactly what it should look like. The issue is that this does two separate things. The first is to ensure there is nothing shared between runs (tying the FT_Library to the stack frame). The second if to force lsan to run each time. Something like 'FT_FUZZER_FULL_ISOLATION' or something might work.
If this were a runtime flag it may be required to dynamically load the lsan symbols (instead of assuming that the user is always running with an lsan build). If this is a compile time flag it might need to be two flags, one for forcing the FT_Library to the stack frame and another for forcing lsan to run each time.