| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0002490 | LibWapcaplet | [All Projects] General | public | 2016-12-05 23:47 | 2020-05-27 08:18 | ||||
| Reporter | Chris Young | ||||||||
| Assigned To | kinnison | ||||||||
| Priority | normal | Severity | minor | Reproducibility | N/A | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | Amiga | OS | AmigaOS | OS Version | 3.5 | ||||
| Summary | 0002490: Memory leaks in libwapcaplet | ||||||||
| Description | I've built the Amiga frontend of NetSurf with clib's memory debugging mode. This logs memory allocations and will note when they haven't been freed. See bug 2489 for more info. For libwapcaplet, we have the following not freed: src/libwapcaplet.c:58 (0002046:0000008 bytes) src/libwapcaplet.c:66 (~16364 bytes) | ||||||||
| Additional Information | Relevant part of the log: [NetSurf] - 8 0x10814570 [allocated at src/libwapcaplet.c:58, freed at stdlib_malloc.c:399] [NetSurf] - 16364 0x10814D7C [allocated at src/libwapcaplet.c:66, freed at stdlib_malloc.c:399] | ||||||||
| Tags | No tags attached. | ||||||||
| Fixed in CI build # | |||||||||
| Reported in CI build # | 3794 | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|||||||
|
|||||||
 Relationships |
| Notes |
|
Chris Young (developer) 2019-06-09 19:22 |
This is still true in the current version. |
kinnison (administrator) 2019-08-01 11:06 |
This looks like the core wapcaplet context which is, indeed, never freed. If the iterator at the end of NetSurf doesn't list any strings, then we've not leaked wapcaplet strings, just the core hash table. Short of adding a 'lwc_closedown()` type function there's no easy way to clear this. |
|
kinnison (administrator) 2019-09-07 14:00 |
I decided to make lwc_iterate_strings() free the global context if no strings were found. This should resolve this. |
Vincent Sanders (administrator) 2020-05-27 08:18 |
Thankyou for reporting this issue. We believe this is fixed in the 3.10 release. If this is not the case please feel free to reopen the issue with additional details. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-05 23:47 | Chris Young | New Issue | |
| 2016-12-05 23:48 | Chris Young | Relationship added | related to 0002489 |
| 2017-01-18 21:29 | Vincent Sanders | Status | new => acknowledged |
| 2019-06-09 19:22 | Chris Young | Note Added: 0001954 | |
| 2019-08-01 11:06 | kinnison | Assigned To | => kinnison |
| 2019-08-01 11:06 | kinnison | Status | acknowledged => assigned |
| 2019-08-01 11:06 | kinnison | Note Added: 0002052 | |
| 2019-08-01 11:06 | kinnison | Status | assigned => confirmed |
| 2019-09-07 14:00 | kinnison | Note Added: 0002087 | |
| 2019-09-07 14:01 | kinnison | Status | confirmed => resolved |
| 2019-09-07 14:01 | kinnison | Resolution | open => fixed |
| 2020-05-27 08:18 | Vincent Sanders | Status | resolved => closed |
| 2020-05-27 08:18 | Vincent Sanders | Note Added: 0002243 | |
| Issue History |