EasyThread Bug?

[remon...@ordyx.com]

I think EasyThread has a bug where a Runnable is never executed. 

Here is the simplest code to reproduce the problem. Add the following code in the start() method of the app:

        EasyThread et1 = EasyThread.start("et1");

        

        et1.run(()->java.lang.System.out.println("************ EASYTHREAD1"));

        EasyThread et2 = EasyThread.start("et2");

        

        et2.run(()->java.lang.System.out.println("************ EASYTHREAD2"));

In the simulator in my case it only shows the following in the log:

************ EASYTHREAD1

The second one never shows. This could be different on different machines and you might need to add more threads for this to show however on my computer it always produces the same result.

Looking at the source for EasyThread the first thing I noticed was that "LOCK" is a static final. Why would lock be static? Why would each instance of EasyThread share the same LOCK?

However I don't think "LOCK" being static is what causes the issue.

Please let me know what is the issue and how it can be fixed.

[Shai Almog]

That makes sens, we'll remove the static modifier for the next update.

[remon...@ordyx.com]

Thank you for your response.

Do you think this static is the whole issue?

[Shai Almog]

It sounds like it. That's exactly the type of problem that would happen.

[remon...@ordyx.com]

Do you have an ETA on this fix?

[Shai Almog]

This was fixed ages ago. I just tried the test case on the simulator and it worked for me.

[remon...@ordyx.com]

Since I didn't see a comment from you here saying that is was fixed I assumed it was not.

Thank you.

[Shai Almog]

For future reference when I say next update I usually mean Friday. I should have explicitly specified it.