river-status: fix output status destruction
There was a use-after-free if the Output was destroyed first, and the memory of the output status was leaked.
This commit is contained in:
parent
d4c249a5cb
commit
6e51a8fcdd
2 changed files with 10 additions and 2 deletions
|
@ -43,6 +43,13 @@ pub fn init(self: *Self, output: *Output, output_status: *zriver.OutputStatusV1)
|
|||
self.sendFocusedTags(output.current.tags);
|
||||
}
|
||||
|
||||
pub fn destroy(self: *Self) void {
|
||||
const node = @fieldParentPtr(std.SinglyLinkedList(Self).Node, "data", self);
|
||||
self.output.status_trackers.remove(node);
|
||||
self.output_status.setHandler(*Self, handleRequest, null, self);
|
||||
util.gpa.destroy(node);
|
||||
}
|
||||
|
||||
fn handleRequest(output_status: *zriver.OutputStatusV1, request: zriver.OutputStatusV1.Request, self: *Self) void {
|
||||
switch (request) {
|
||||
.destroy => output_status.destroy(),
|
||||
|
@ -50,8 +57,7 @@ fn handleRequest(output_status: *zriver.OutputStatusV1, request: zriver.OutputSt
|
|||
}
|
||||
|
||||
fn handleDestroy(output_status: *zriver.OutputStatusV1, self: *Self) void {
|
||||
const node = @fieldParentPtr(std.SinglyLinkedList(Self).Node, "data", self);
|
||||
self.output.status_trackers.remove(node);
|
||||
self.destroy();
|
||||
}
|
||||
|
||||
/// Send the current tags of each view on the output to the client.
|
||||
|
|
|
@ -203,6 +203,8 @@ pub fn removeOutput(self: *Self, output: *Output) void {
|
|||
// Destroy all layouts of the output
|
||||
while (output.layouts.first) |layout_node| layout_node.data.destroy();
|
||||
|
||||
while (output.status_trackers.first) |status_node| status_node.data.destroy();
|
||||
|
||||
// Arrange the root in case evacuated views affect the layout
|
||||
fallback_output.arrangeViews();
|
||||
self.startTransaction();
|
||||
|
|
Loading…
Reference in a new issue