Re: how to handle the last_error of wl_display

2018-06-21 Thread Pekka Paalanen
On Thu, 21 Jun 2018 11:59:57 +0800 zou lan wrote: > Hi pekka > > I find the last_error is caused by > wl_display_flush()-->wl_connection_flush(). The sendmsg() return fail. > > Many applications write code like this: > > redraw() > { > wl_surface_commit(); > wl_display_sync(); >

Re: how to handle the last_error of wl_display

2018-06-20 Thread zou lan
Hi pekka I find the last_error is caused by wl_display_flush()-->wl_connection_flush(). The sendmsg() return fail. Many applications write code like this: redraw() { wl_surface_commit(); wl_display_sync(); wl_display_flush(); } while (1) { redraw(); } The code will block to wait buffer

Re: how to handle the last_error of wl_display

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 16:59:35 +0800 zou lan wrote: > Dear pekka & All: > > I find a wayland application report error about allocate memory fail. > I check the code, after request to weston to allocate dma buffer, it call > wl_display_roundtrip(). > But this function return very fast, it doesn't

how to handle the last_error of wl_display

2018-06-14 Thread zou lan
Dear pekka & All: I find a wayland application report error about allocate memory fail. I check the code, after request to weston to allocate dma buffer, it call wl_display_roundtrip(). But this function return very fast, it doesn't block until the create events back. I suspect the