[TTVD] Do not treat conflict as error on scaler

After resource conflict scaler should still be available
to use as some later point. We are protected agains
constant resource conflict, as we should not get resource
when other client has higher priority (e.g we are
suspended).

Bug: https://jira-eu.sec.samsung.net/browse/VDGAME-712
Change-Id: Ifc70874448fc04ce3138d6399e3fb80bbe1648c8
Signed-off-by: Jakub Gajownik <j.gajownik2@samsung.com>

diff --git a/tizen_src/chromium_impl/ui/ozone/platform/efl/output_surface_state.cc b/tizen_src/chromium_impl/ui/ozone/platform/efl/output_surface_state.cc
index 638f438f6ebf690d2d94212bba61eec7d5aed664..2e609a72a0ed1f11329f9f1d202f0058e3a859c9 100644 (file)
--- a/tizen_src/chromium_impl/ui/ozone/platform/efl/output_surface_state.cc
+++ b/tizen_src/chromium_impl/ui/ozone/platform/efl/output_surface_state.cc
@@ -201,7 +201,10 @@ void OutputSurfaceState::Reset() {
 }
 
 void OutputSurfaceState::MarkResourceTaken() {
-  state_ = State::kError;
+  // After resource conflict, treat surface as it'd be allocated from the
+  // scratch. It won't be possible in case other client priority is higher
+  // or allocation of this resource is disabled.
+  state_ = State::kNotInitialized;
 
   // Resource has been taken by some other process/client. Remove it from
   // surface factory, so clients are not capable of accessing it.