From 3ac056924ce508288fc34050ee44fc27a6ed7ae8 Mon Sep 17 00:00:00 2001
From: Julian Oes <julian@oes.ch>
Date: Thu, 15 Dec 2016 08:47:17 +0100
Subject: [PATCH] navigator: increase stack The stack size was generally ok but
 seemed to get exhausted in the case of a waypoint which is too far away and
 therefore exercises some more code in the mission feasability checker.

Generally, we should have more margin in the navigator stack size
because there are a bunch of different code paths that can happen.
---
 src/modules/navigator/navigator_main.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/modules/navigator/navigator_main.cpp b/src/modules/navigator/navigator_main.cpp
index 361a8510af..28d7c246d8 100644
--- a/src/modules/navigator/navigator_main.cpp
+++ b/src/modules/navigator/navigator_main.cpp
@@ -673,7 +673,7 @@ Navigator::start()
 	_navigator_task = px4_task_spawn_cmd("navigator",
 					 SCHED_DEFAULT,
 					 SCHED_PRIORITY_DEFAULT + 5,
-					 1300,
+					 1600,
 					 (px4_main_t)&Navigator::task_main_trampoline,
 					 nullptr);