#11363 closed bug (fixed)
Investigate semaphore leaks detected by Coverity
| Reported by: | waddlesplash | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | System/Kernel | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Selecting "Categories" then "RESOURCE_LEAK" shows a number of leaks in semaphore code (at least the first 10-15 or so). These should be examined and determine if any of these are really leaking semaphores (as Adrien ran into some instances where the system would run out of semaphores due to a leak somewhere).
Change History (4)
comment:1 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 5 years ago
comment:4 by , 4 years ago
| Milestone: | R1 → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Note:
See TracTickets
for help on using tickets.
I reviewed these again and it seems that they're mostly false positives or were already fixed. Haiku can run for quite a long time now without running into issues; so this is probably fixed.