New versions of Adlink Edge SDK are released on a regular basis. This page lists all the known issues for Adlink Edge SDK V1
You may also want to read the following:
Edge SDK Known Issues
|THINGAPI-623||A Python Listener class defining a constructor may cause a Segmentation Fault/Access Violation
A Python Listener class that defines a constructor (that is, a __init__ method) must call the super class's __init__ method, otherwise a Segmentation Fault/Access Violation will occur when a listener instance is added via a call to one of the Python API's add_listener methods.
Workaround: See the Python API User's Guide for an example of a well formed listener class with a constructor.
|THINGAPI-775||Security Composer on Debian 9 does not start when using default Debian OpenSSL libraries
In this release, Security Compose dynamically links to OpenSSL 1.0.2 LTS libraries. Previous releases used statically linked OpenSSL v1.0.2o. By dynamically linking OpenSSL libraries, customers may incorporate any OpenSSL security updates by downloading, building and installing the latest Openssl 1.0.2 release. However, on Debian 9, the default Debian-provided link libraries are named inconsistently with then OpenSSL libraries create from openssl.org source code. Debian names the libraries libssl.so.1.0.2 and libcrypto.so.1.0.2 while libraries built from OpenSSL source code have the names libssl.so.1.0.0 and libcrypto.so.1.0.0. The Security Composer links against the latter, and, on Debian 9, will not start, producing an error such as:
/opt/ADLINK/EdgeSDK/1.1.1/tools/securitycomposer: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
Customer's can resolve this issue in one of two ways:
make symbolic links to the 1.0.2 Debian libraries:
sudo ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
sudo ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
download, build and install the latest OpenSSL 1.0.2 source. See the Release Highlights document, issue THINGAPI-718 for more information on updating OpenSSL.
|THINGAPI-438||Control-C not received by Python applications during blocking read/read_next
During a blocking call to Thing.readIotNvp, Thing.readNextIotNvp, Selector.readIotNvp and Selector.readNextIotNvp, any Ctrl-C interrupt will not be received by the Python engine.
|THINGAPI-533||Excessive cpu-load for ThingAPI read-operations on large (e.g. multi-megabyte video-)samples
When applicable: if cpu-monitoring tools such as 'top' shows about equal amount of system-time and user-time for read-operations
Work-around: to reduce the cpu-load create 2 environment variables with appropriate values:
export MALLOC_TRIM_THRESHOLD_=-1 (which causes 'mmap' to be used rather than malloc for large memory-chunks
export MALLOC_MMAP_THRESHOLD_=4000000 (a value greater than the sample/video-size)
Consequence: increased memory-usage of a process which decreases the amount of available RAM for all other processes
Operating System/Platform Related Issues
- As of ADLINK Edge SDK version 1.0.1, Ubuntu 14.04 is not supported.
- As of ADLINK Edge SDK version 1.1, Ubuntu 18.04 support has been added.