[TIMOB-7927] Android: Fix concurrency problems with events
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2020-01-09T21:34:13.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android |
| Labels | tbs-2.1.0 |
| Reporter | Marshall Culpepper |
| Assignee | Unknown |
| Created | 2012-03-08T09:40:45.000+0000 |
| Updated | 2020-01-09T21:34:13.000+0000 |
Description
We have run into more ConcurrentModificationExceptions when sending out events by bubbling to the parent hierarchy of a ViewProxy. Since we are sharing event objects, this is causing the runtime and UI threads to iterate the same map at the same time.
The proposed solution would be to move bubbling over to the runtime thread (possibly in JS) so we can avoid having multiple jobs in the queue for one event.
See my comment at the bottom of TIMOB-7774 for info about the original fail case
It has been decided that this issue should be closed as “Won’t do.” This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.