On Tue, 2012-07-10 at 08:52 -0400, Kristian Høgsberg wrote:
> On Tue, Jul 10, 2012 at 01:20:24AM -0700,
> juan.j.z...@linux.intel.com wrote:
> > From: Juan Zhao
> >
> > When the client was hanged and not responsible for a long time, the
> server will generate
> > endless and useless "set_busy_cu
On Tue, Jul 10, 2012 at 01:20:24AM -0700, juan.j.z...@linux.intel.com wrote:
> From: Juan Zhao
>
> When the client was hanged and not responsible for a long time, the server
> will generate
> endless and useless "set_busy_cursor" related events. And finally, weston
> crashed, with
> error mes
Please ignore this mail!
Sorry for the TYPO!
Thanks,
Juan
On Tue, 2012-07-10 at 01:20 -0700, juan.j.z...@linux.intel.com wrote:
> From: Juan Zhao
>
> When the client was hanged and not responsible for a long time, the server
> will generate
> endless and useless "set_busy_cursor" related eve
From: Juan Zhao
When the client was hanged and not responsible for a long time, the server will
generate
endless and useless "set_busy_cursor" related events. And finally, weston
crashed, with
error message:"read error from connection 0x823b560: Connection reset by peer
(104)
read error: C
