Skip to content

Memory leak with Stream2 #102

@MarkRivers

Description

@MarkRivers

When using the Stream2 interface there is a very significant memory leak.

Test conditions:

  • Eiger2 1M
  • BSLZ4 compression selected
  • All plugins disabled
  • Data source = Stream
  • Stream version = Stream2
  • Stream decompress disabled
  • TriggerMode = Internal Series
  • NumImages = 1
  • AcquireTime = 0.1 second

The detector dimensions are 1028 x 1062. In 32-bit mode each array is 4366944 bytes or 4265 KB.

I ran the Linux "top" program and noted the VIRT memory usage as I collected 5 images. VIRT increased by exactly 8788 KB with each image.

Conclusions:

  • The memory leak is very close to twice the size of the decompressed images.
  • The data delivered over Stream2 is BSLZ4 compressed, and because there are no X-rays on the detector the compression is very high, and the compressed data is only 26 KB.
  • Because decompression is disabled in the driver, and the Codec plugins are disabled, the data is never being decompressed.
  • Need to figure out what the memory leak is twice the size of the decompressed data.
  • This only happens with Stream2, there is no memory leak with the Stream interface.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions