Fix wrong initialization

Before creating the loaders, the launchpad-process-pool should read the vconf values.
While creating the loaders, the launchpad-process-pool checks whether
the system memory is low or not. If the system memory is low state,
the launchpad-process-pool makes the state of the loader context is paused.
This patch fixes it.

Change-Id: Ieb14f997f2bd4bcdce58beb911c493997571ea24
Signed-off-by: Hwankyu Jhun <h.jhun@samsung.com>

diff --git a/src/launchpad-process-pool/src/launchpad.c b/src/launchpad-process-pool/src/launchpad.c
index efdcfbcb6f2fbb65ca85a81e697f149bb7dfc506..c18c158fa602e80b975d58325874bfd3b934fbb9 100644 (file)
--- a/src/launchpad-process-pool/src/launchpad.c
+++ b/src/launchpad-process-pool/src/launchpad.c
@@ -3518,6 +3518,7 @@ static int __before_loop(int argc, char **argv)
        _inotify_init();
        _memory_monitor_init();
        _memory_monitor_set_event_cb(__memory_monitor_cb, NULL);
+       __register_vconf_events();
 
        MAX_CPU_CHECK_COUNT = _config_get_int_value(
                        CONFIG_TYPE_CPU_CHECKER_MAX_COUNT);
@@ -3541,7 +3542,6 @@ static int __before_loop(int argc, char **argv)
        if (ret < 0)
                return ret;
 
-       __register_vconf_events();
        __init_app_defined_loader_monitor();
        _log_init();
        _print_hwc_log("%s(%d): END", __FUNCTION__, __LINE__);