On Tue, Dec 16, 2008 at 01:41:01AM -0000, djtm wrote:
> As much as you doubt he can confirm this is really the same bug
> -- how can you be sure it's not?
>
> network-manager is leaking memory for over a year now. We could start installing scripts that automatically track its memory usage and report leaks.
> What about a generic "network-manager leaks memory" bug?
> Then people can list all their different situations in separate bug reports.
> I don't know if that'd make it a lot better...
> I definitely understand the frustration this causes.
>
> But hey, everyone - you hear him: open your own bugs. It can only bring
> more visibility to this issue...
>
> How sad, though. Usually the open source process works pretty well... So
> anyone pulling his hair out over these annoying memory leaks: rest
> assured, this is an exception.
>
A fix for the "hardy" (0.6.x) memory leak should be in -proposed
now. Please help testing that package.
On Tue, Dec 16, 2008 at 01:41:01AM -0000, djtm wrote:
> As much as you doubt he can confirm this is really the same bug
> -- how can you be sure it's not?
>
> network-manager is leaking memory for over a year now. We could start installing scripts that automatically track its memory usage and report leaks.
> What about a generic "network-manager leaks memory" bug?
> Then people can list all their different situations in separate bug reports.
> I don't know if that'd make it a lot better...
> I definitely understand the frustration this causes.
>
> But hey, everyone - you hear him: open your own bugs. It can only bring
> more visibility to this issue...
>
> How sad, though. Usually the open source process works pretty well... So
> anyone pulling his hair out over these annoying memory leaks: rest
> assured, this is an exception.
>
A fix for the "hardy" (0.6.x) memory leak should be in -proposed
now. Please help testing that package.
- Alexander