sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #49700
[Bug 1741764] Re: [1.1.4] ADBScreen - crashes if waitAfterAction set to 0
** Changed in: sikuli
Status: In Progress => Fix Committed
** Changed in: sikuli
Importance: Medium => Critical
** Summary changed:
- [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
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1741764
Title:
[1.1.4] ADBScreen - crashes if waitAfterAction set to 0 --- fixed
2018-12-12 build #145
Status in Sikuli:
Fix Committed
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.captureDeviceScreenMat() - InputStream stdout is left unclosed.
Calling stdout.close() in finally{} or using Try-with-resources Statement for:
InputStream stdout = device.executeShell("screencap") fixes that issue.
There are more not closed InputStreams in ADBDevice that may cause
issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1741764/+subscriptions
References