ngscopeclient v0.2.1 release notes
This is a hotfix release for v0.2.1 that addresses a race condition in the PicoScope and ThunderScope drivers leading to GPU memory leaks and out-of-memory crashes if a new waveform arrives before driver processing of the previous waveform has finished, as well as a few other minor bugs.
There are no new features in this release.
New features since v0.2
- None
Breaking changes since v0.2
We try to maintain compatibility with older versions of ngscopeclient but occasionally we have no choice to change the interface of a block in a way that requires old filter graphs to be updated.
NOTE: This section only list changes which are potentially breaking to an end user. Prior to the version 1.0 release, there is no expectation of API/ABI stability and internal software interfaces may change at any time with no warning.
- None
Bugs fixed since v0.2
- PicoScope: fixed race condition where if waveform conversion took too long a buffer could leak
- ThunderScope: fixed race condition where if waveform conversion took too long a buffer could leak (#1023)
- Core: progress display would incorrectly show disabled channels as downloading (ngscopeclient/scopehal#1108)
- Core: Fixed race condition in SCPITransport::FlushCommandQueue that could lead to hangs or dropped commands
Other changes since v0.2
- None
Known issues
- Deletion of a filter by pressing "delete" with the node selected in the filter graph editor is not always possible, since not all possible consumers are tracked in the filter graph yet. If you try to delete a block and it doesn't go away, stdout and the log viewer dialog should show a message about X unresolved dangling references; you will need to find and close these windows manually. Export-to-file filters have a known reference leak and are currently impossible to delete once added to a session.