Re: [PATCH weston] compositor: fix usage of dangling output pointer after destroying it

2015-01-22 Thread Giulio Camuffo
Actually, this seems to cause the cursor to sometimes disappear, not sure why... A different approach would be to go through the view_list in weston_output_destroy() and reset the output pointers if needed, but I don't quite like it. 2015-01-22 16:52 GMT+02:00 Giulio Camuffo : > When an output is

[PATCH weston] compositor: fix usage of dangling output pointer after destroying it

2015-01-22 Thread Giulio Camuffo
When an output is destroyed a view may still hold a pointer to it. Calling weston_view_assign_output() on one view of a surface ends up updating the output on that view and later iterating over all the views of a surface and using their output, which may be bogus. Instead, call weston_surface_assig