You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server responds correctly with {"success":{}}. The response is read correctly by the network handling code, and is passed down to the parse method inside VMCommunicator.getBollardsByStreet. Further debugging has shown that the exception is thrown when exiting the finally block in VMCommunicator.readVirtualMonitorData. The method itself never returns.
The text was updated successfully, but these errors were encountered:
Steps to reproduce :
The application crashes with an
OutOfMemoryError
, and leaves the "Busy" dialog running forever.The server responds correctly with
{"success":{}}
. The response is read correctly by the network handling code, and is passed down to theparse
method insideVMCommunicator.getBollardsByStreet
. Further debugging has shown that the exception is thrown when exiting thefinally
block inVMCommunicator.readVirtualMonitorData
. The method itself never returns.The text was updated successfully, but these errors were encountered: