Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • L Lima
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LimaGroupLimaGroup
  • Lima
  • Issues
  • #115
Closed
Open
Issue created Jun 08, 2020 by Alejandro Homs Puron@alejandro.homsOwner

Memory corruption error after using CtControl::ImageStatusCallback

The test_int_trig_mult.py program systematically shows memory corruption errors with the Simulator, Eiger, and SlsDetector plugins:

Valid ranges: 
  min_exp_time=0.0000000,  max_exp_time=1000000.0000000
  min_lat_time=0.0000000,  max_lat_time=1000000.0000000
Starting acquisition ...
Sending start #0
Sending start #1
Sending start #2
Sending start #3
Sending start #4
Sending start #5
Sending start #6
Sending start #7
Sending start #8
Sending start #9
Average trigger_delay=0.078 (0.010 + 0.068)
Acquisition finished -0.000 sec after trigger sequence
[2020/06/08 17:31:48.478623] 7fe06f1de740     *Control*Control::Control::unregisterImageStatusCallback (/users/opid00/esrf/sls_detectors/Lima/control/src/CtControl.cpp:1260)-Always: Unregistering 0x557bb770bc40
double free or corruption (out)
Assignee
Assign to
Time tracking