On Thu, May 08, 2014 at 11:38:13PM -0400, Tom Stellard wrote:
> The screen takes ownership of the winsys, and is responsible for
> destroying it. Users of pipe-loader should make sure they destory
> and screens they've created to avoid memory leaks.
>
I did not mean to send this whole series ag
The screen takes ownership of the winsys, and is responsible for
destroying it. Users of pipe-loader should make sure they destory
and screens they've created to avoid memory leaks.
This fixes a crash in clover introduced by
ce6c17c0833032e91a2d1b34f9eb80c738a854a2 where the pipe-loader was
dest
On 09/05/14 02:17, Tom Stellard wrote:
> The screen takes ownership of the winsys, and is responsible for
> destroying it. Users of pipe-loader should make sure they destory
> and screens they've created to avoid memory leaks.
>
I was under false impression that our current sw screens do not des
The screen takes ownership of the winsys, and is responsible for
destroying it. Users of pipe-loader should make sure they destory
and screens they've created to avoid memory leaks.
This fixes a crash in clover introduced by
ce6c17c0833032e91a2d1b34f9eb80c738a854a2 where the pipe-loader was
dest
