On Mon, 10 Jan 2011 16:44:53 +0100 (CET) Pavel Reznicek
said:
>
> > gees... wtf is an anon_inode... first time i've seen that... and my quick
> > investigation shows that that is the epoll fd itself... so - something is
> > closing the epoll fd. only 3 ways that happens.
> > 1. _ecore_get_epoll_
> gees... wtf is an anon_inode... first time i've seen that... and my quick
> investigation shows that that is the epoll fd itself... so - something is
> closing the epoll fd. only 3 ways that happens.
> 1. _ecore_get_epoll_fd() detects that current epoll fd and the pid it
> was create in dont ma
On Sat, 18 Dec 2010 11:55:15 +0100 (CET) Pavel Reznicek
said:
gees... wtf is an anon_inode... first time i've seen that... and my quick
investigation shows that that is the epoll fd itself... so - something is
closing the epoll fd. only 3 ways that happens. 1. _ecore_get_epoll_fd()
detects that c
Hi, thanks for the advices - logging the fd's, the problem happens exactly
when this fd disappears:
/proc/5721/fd/3 -> anon_inode:[eventpoll]
No other changes in the fd list. The observation is based on two
occurances only, since the problem was happening much less frequently in
the last week
On Fri, 26 Nov 2010 09:59:19 +0100 (CET) Pavel Reznicek
said:
look at /proc/PID/fd
(PID being the pid of e). see what fd's you have - or not
and how they change over time (ls -l will show you which fd's point where).
write a script to log them often (every second?) and see if the log at the time
Hello,
I am regularly hitting a bug mentioned here:
http://www.mail-archive.com/enlightenment-de...@lists.sourceforge.net/msg27014.html
Using latest SVN revision 54923 compiled via easy_e17 script on debian
squeeze. The problem usually happens after few hours or running e17 or
when graphic
