[1.1.4] ADBScreen - crashes if waitAfterAction set to 0 --- fixed 2018-12-12 build #145
Bug #1741764 reported by
Kamil Kliwison
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SikuliX |
Fix Released
|
Critical
|
RaiMan | ||
Bug Description
If waitAfterAction set to 0 on ADBScreen object, after some time application always crashes.
The reason for that is a bug in method ADBDevice.
Calling stdout.close() in finally{} or using Try-with-resources Statement for:
InputStream stdout = device.
There are more not closed InputStreams in ADBDevice that may cause issues.
| Changed in sikuli: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → RaiMan (raimund-hocke) |
| milestone: | none → 1.1.4 |
| summary: |
- [1.1.1] ADBScreen - crashes if waitAfterAction set to 0 + [1.1.4] ADBScreen - crashes if waitAfterAction set to 0 |
| Changed in sikuli: | |
| status: | In Progress → Fix Committed |
| importance: | Medium → Critical |
| summary: |
- [1.1.4] ADBScreen - crashes if waitAfterAction set to 0 + [1.1.4] ADBScreen - crashes if waitAfterAction set to 0 --- fixed + 2018-12-12 build #145 |
| Changed in sikuli: | |
| status: | Fix Committed → Fix Released |
| milestone: | 1.1.4 → 2.0.0 |
To post a comment you must log in.
