Code not working when running normally, but working in debug (eclipse)

Question

I\'m really confused by this: some of my code is not working when i run my program normally in eclipse, but it does wok when i run through each step separately using the deb

Answer 1

I had same problem in UIAutomator with UiObject2 wait(Until.findObject(),20) .

Thread.yield() - works for me

Answer 2

I had a very similar problem with a "while" loop that wouldn't run and that loop was my main routine. How I got the loop to run was that the very first thing that was done in the loop was a sleep:

    try
        {Thread.sleep(0);}
    catch (Exception e)
        {e.printStackTrace();}

This was enough to get everything going.

Answer 3

I had the same Problem, but with some more specification. The code was working fine in 32bit but I had this issue in 64bit (I am using native library so I need to maintain both).

The solution I found is to add Thread.sleep() in the while loop. I don't know why it works, so your guess is as good as mine.

A better solution would probably to implement an Observer Pattern instead of having an infinite loop. But that would require some re-factoring.

Answer 4

Using Thread.sleep(), as the other answers have suggested, should solve the problem but it is not a very good approach. Instead, we should be using Thread.yield().

Why yield and not sleep?

Refer: Difference between Thread.Sleep(0) and Thread.Yield() and Are Thread.sleep(0) and Thread.yield() statements equivalent?

Why this works?

When we just run the threads, the OS puts them to "idle" state and when it is expected to "wake-up", it does not. On the other hand, in debug mode, we have a controlled environment. The OS has little control over it as everything goes on step-by-step, slowly. If we run the debug a few times without any break-points, after a few successful runs, we should see the same effect.