Bug 124640
Summary: | REGRESSION (r159486): EFL WK2 MiniBrowser doesn't launch | ||
---|---|---|---|
Product: | WebKit | Reporter: | Gyuyoung Kim <gyuyoung.kim> |
Component: | WebKit EFL | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | lucas.de.marchi, ryuan.choi |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Gyuyoung Kim
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.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ryuan Choi
(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 ?
Gyuyoung Kim
(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.
Gyuyoung Kim
I can't run layout test locally because of same reason.
Ryuan Choi
(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.
Gyuyoung Kim
Now I can't work anything on EFL MiniBrowser. How about reverting it until you solve this issue ?
Ryuan Choi
(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
Michael Catanzaro
Closing some bugs that probably only affect EFL. Please leave a comment if you feel this bug was closed in error.