Bug report

[EghamQin]

Hi Martin,

I find a potential bug - which threw an unexpected exception. Enclosed is the error report generated by the app. Hope it would be of help.

Qin

[EghamQin]

Hi Martin,

Here is another possible bug...

Qin

[Martin]

Hi,

Definitely a bug. Should be fixed in the next update.
If your flow allows, could you please add Wait for called flows to finish to the action Execute Flows to see if this helps?

If not, could you please send the flow(s) to info@automagic4android.com so I can check that my fix also works for your case?

Thanks & Regards,
Martin

[EghamQin]

Hi Martin,

Thanks for your reply. I personally feel the problem is caused by flow concurrency. In my case, there is a list type of variable that multiple flows may update it. When more than one flow happen to update the list at the same time, the system may throw error. I may be completely wrong but this is my naive interpretation of the problem. It sounds to me that Automgic at the moment is not thread safe...

At the moment, my design of the flows requires concurrent execution of multiple flows: they coordinate with each other to achieve an overall goal. So for me to making it execute on single flow basis is really not an option to me, unfortunately.

But this bug does not happen that often. I just try to make the probability that more than one flow update the same variable to be small enough.

Hope this would help.

Qin

[Martin]

Hi Qin,

There is indeed a threading issue here but I think it should be fixed in the next update. This crash came from an internal tracing feature that missed to acquire the proper lock.
However, could you please send the flows to info@automagic4android.com so I can make some tests and check if I really fixed the issue you encountered. The stacktrace of the exception itself only shows one side of the problem so I might not have fixed the issue completely.

Regards,
Martin

[EghamQin]

Hi Martin,

I have sent you the flows...

Cheers
Qin