why this code is making unity unresposnive?

Question

 using System.Threading.Tasks;
 using UnityEngine;
 public class sampleclass : MonoBehaviour
 {
     bool istrue = true;
     void Start()
     {
          Invoke("hello_false", 5);
         Task<string> result = call();
       



         Debug.Log("is code working" + result.Result);
 
     }
 
     void hello_false()
     {
         istrue = false;
     }
     void hello()
     {
         while (istrue)
         {
             int justcount = 0;
             justcount++;
         }
 
 
     }
     async Task<string> call()
     {
         Task newtask = new Task(hello);
         newtask.Start();
 
         await newtask;
 
         return "task done ";
     }
 
 
 
 }
 
 
 when I don't use return statement code runs perfectly but when i add return statement it hangs/become unresponsive.

Answer 1

Answer by KenanTheFab · Feb 21 at 06:45 PM

It seems to loop

 void hello()

over and over due to

 while(istrue)

And nothing really tells it to stop the loop.

Add comment · Show 3 · Share

MiroslavMilanov · Feb 21 at 06:58 PM 0

Share

Your answer is not true.

      void hello_false()
      {
          istrue = false;
      }

Does exactly that.

greencheese122 MiroslavMilanov · Feb 21 at 10:26 PM 1

Share

He is right though. istrue gets set to false every 5 seconds. BUT unity is calling the while(istrue) every frame and it calls it infinite amount of time in one frame during a second, so it just loops over and over and never allows istrue to get set to false.

unity_RMiJ7SENDRQxhQ · Feb 22 at 03:09 AM 0

Share

it has noting to do with while loop.I have tried this result but still unity editor become unresponsive.i think its due to return statement but i don't have any reason for it.

 using System.Threading.Tasks;
 using UnityEngine;
 public class sampleclass : MonoBehaviour
 {
 
     void Start()
     {
 
 
         Task<string> result = call();
         Debug.Log("is code working" + result.Result);
 
     }
 
 
 
 
     void hello()
     {
         for (int i = 0; i < 10; i++)
         {
             int timewaste = 0;
             timewaste++;
         }
 
 
     }
     async Task<string> call()
     {
         Task newtask = new Task(hello);
         newtask.Start();
 
         await newtask;
 
         return "task done ";
     }
 
 
 
 }

Answer 2

Answer by Kishotta · Feb 21 at 09:56 PM

It might be better to stick with coroutines and use an Action callback:

 private bool isTrue = true;
 
 private void Start () {
     // When 'Call()' completes it will log the result
     StartCoroutine (Call (result => Debug.Log (result)))
     // Kick off the kill condition
     StartCoroutine (SetFalse ());
 }
 
 private IEnumerator Call (Action<string> callback) {
     // When 'Hello()' completes, it returns the string "Task Complete 682" to the initial lambda
     yield return Hello (finalCount => callback ("Task Complete " + finalCount));
 }

 private IEnumerator Hello (Action<int> callback) {
     int count = 0;
     while (isTrue) {
         count++;
         yield return null;
     }
     //  Returns the count to the above lambda
     callback (count);
 }

 // Just a delayed operation
 private IEnumerator SetFalse () {
     yield return WaitForSeconds (5f);
     isTrue = false;
 }

Add comment · Show 1 · Share

unity_RMiJ7SENDRQxhQ · Feb 22 at 03:13 AM 0

Share

I don't want to use coroutine as they return values.I know i can use callbacks but I would rather prefer async and await.also I wanted the reason for this behavior.thanks for help

why this code is making unity unresposnive?

2 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions