Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • dcdb dcdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dcdb
  • dcdbdcdb
  • Issues
  • #18

Closed
Open
Created Jun 05, 2019 by Ghost User@ghostContributor

DCDBPusher segfault on return from main

DCDBPusher will crash with a segmentation fault after returning from main under certain configurations. A wide variety of factors affects how and when the bug occurs, such as:

  • Number of plugins, sensors and sensor groups instantiated;
  • Compilation and execution environment;
  • Minimal, uncorrelated changes to the code.

The bug has been confirmed to occur independently of the REST API, data analytics framework, and the specific pusher plugins being used. A temporary fix has been identified in NOT unloading dynamic libraries when destroying the PluginManager object. However, it is not certain whether this fix only reduced the likelihood of occurrence of the bug, or actually got rid of it.

We suspect the bug might be related to the termination and destruction of objects used by the BOOST ASIO backend (boost::asio::io_service) which might have global scope.

Assignee
Assign to
Time tracking