Bug 124640 - REGRESSION (r159486): EFL WK2 MiniBrowser doesn't launch
Summary: REGRESSION (r159486): EFL WK2 MiniBrowser doesn't launch
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-19 23:58 PST by Gyuyoung Kim
Modified: 2017-06-07 19:50 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gyuyoung Kim 2013-11-19 23:58:06 PST 
EFL MiniBrowser doesn't launch since r159486.

ERR<5599>:efreet_cache efreet_cache.c:159 efreet_cache_init() Failed to set up ecore file monitor for '/home/gyuyoung/.cache/efreet'
CRI<5599>:ewebkit2 /home/gyuyoung/webkit/WebKit/Source/WebKit2/UIProcess/API/efl/ewk_main.cpp:83 ewk_init() could not init efreet.
Comment 1 Ryuan Choi 2013-11-20 01:25:09 PST 
(In reply to comment #0)
> EFL MiniBrowser doesn't launch since r159486.
> 
> ERR<5599>:efreet_cache efreet_cache.c:159 efreet_cache_init() Failed to set up ecore file monitor for '/home/gyuyoung/.cache/efreet'
> CRI<5599>:ewebkit2 /home/gyuyoung/webkit/WebKit/Source/WebKit2/UIProcess/API/efl/ewk_main.cpp:83 ewk_init() could not init efreet.

weird, It looks fine to me on both debug and release build.

Could you check the folder status of ~/.cache and ~/.cache/efreet ?
Comment 2 Gyuyoung Kim 2013-11-20 01:56:33 PST 
(In reply to comment #1)
> (In reply to comment #0)
> > EFL MiniBrowser doesn't launch since r159486.
> > 
> > ERR<5599>:efreet_cache efreet_cache.c:159 efreet_cache_init() Failed to set up ecore file monitor for '/home/gyuyoung/.cache/efreet'
> > CRI<5599>:ewebkit2 /home/gyuyoung/webkit/WebKit/Source/WebKit2/UIProcess/API/efl/ewk_main.cpp:83 ewk_init() could not init efreet.
> 
> weird, It looks fine to me on both debug and release build.
> 
> Could you check the folder status of ~/.cache and ~/.cache/efreet ?

Though I have ~/.cache and ~/.cache/efreet, I have still this problem.
Comment 3 Gyuyoung Kim 2013-11-21 22:46:59 PST 
I can't run layout test locally because of same reason.
Comment 4 Ryuan Choi 2013-11-21 22:53:04 PST 
(In reply to comment #3)
> I can't run layout test locally because of same reason.

I think that it looks efreet bug, but I can't reproduce. :(

I will check whether we can disable efreet_cache as a workaround.
Comment 5 Gyuyoung Kim 2013-11-24 17:17:24 PST 
Now I can't work anything on EFL MiniBrowser. How about reverting it until you solve this issue ?
Comment 6 Ryuan Choi 2013-11-24 19:35:08 PST 
(In reply to comment #5)
> Now I can't work anything on EFL MiniBrowser. How about reverting it until you solve this issue ?

Sad, I think that we should remove all efreet related code or call efreet_init correctly.

Anyway, I checked in someone's machine which reproduced same issue.
It looks because inotify was limitted and other process used all available inotify resources.

Could you tried once more with below command? (temporal solution)
sudo sh -c 'echo 1048576 > /proc/sys/fs/inotify/max_user_watches'

If it is fine, you can read more information (including permanant solution) at
http://peter-butkovic.blogspot.kr/2013/08/tail-inotify-resources-exhausted.html
Comment 7 Michael Catanzaro 2017-06-07 19:50:21 PDT 
Closing some bugs that probably only affect EFL. Please leave a comment if you feel this bug was closed in error.