Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playing a bag recorded with file compression segfaults #412

Closed
audrow opened this issue May 15, 2020 · 4 comments · Fixed by #417
Closed

Playing a bag recorded with file compression segfaults #412

audrow opened this issue May 15, 2020 · 4 comments · Fixed by #417
Assignees
Labels
bug Something isn't working
Milestone

Comments

@audrow
Copy link
Member

audrow commented May 15, 2020

Description

When I try to play a bag that has been recorded with the compression mode zstd and format file, I receive a segmentation fault when I try to play that bag.

Expected Behavior

I expect to have the bag play.

Actual Behavior

The bag seems to open and then a segmentation fault occurs. Here is the printout.

[INFO] [1589568927.962724388] [rosbag2_storage]: Opened database 'compressed_bag/compressed_bag_0.db3' for READ_ONLY.
Segmentation fault (core dumped)

To Reproduce

  1. In one terminal, create a publisher:

    ros2 topic pub /foo std_msgs/msg/String data:\ \'Hi\'\ 
    
  2. In another terminal, record a bag:

    ros2 bag record --compression-format zstd --compression-mode file --output compressed_bag /foo
    
  3. Hit Ctrl+C to stop recording the bag.

  4. Try to play the bag:

    ros2 bag play compressed_bag
    

System

  • OS: Ubuntu Focal
  • ROS 2 Distro: Foxy
  • Version: 0.2.7-1focal.20200514.041002
@audrow audrow added the bug Something isn't working label May 15, 2020
@emersonknapp emersonknapp added this to the Sprint #19 milestone May 18, 2020
@emersonknapp
Copy link
Collaborator

I am starting to look into this now. Thanks for reporting.

@Karsten1987
Copy link
Collaborator

@zmichaels11 what changed in between that you closed this ticket? Same for #413

@zmichaels11
Copy link
Contributor

@Karsten1987 our team reviewed the work done and verified that the problem was solved.
@emersonknapp can you add a comment here explaining why?

@emersonknapp
Copy link
Collaborator

This was resolved with #417 but our internal process had blocked actually closing the issue pending team review/demo. We're going to be modifying that process though. Sorry for any confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants