sikuli-driver team mailing list archive

[Kamil Kliwison <1741764@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: sikuli
     Importance: Undecided
         Status: New

-- 
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.1] ADBScreen - crashes if waitAfterAction set to 0

Status in Sikuli:
  New

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