boundary.cpp:294] Check failed: region_id != segment.right_region (194 vs. 194)

kmsquire commented 10 years ago

When running seg_tree_sample on the input file in the video_example directory (and on other files), I'm getting

$ seg_tree_sample --input_file=test_video.MOV  --logging
...
I0708 19:09:34.188959 18009 region_segmentation.cpp:360] Region output frame 0
I0708 19:09:34.198417 18009 region_segmentation.cpp:360] Region output frame 1
I0708 19:09:34.209580 18009 region_segmentation.cpp:360] Region output frame 2
I0708 19:09:34.221459 18009 region_segmentation.cpp:360] Region output frame 3
I0708 19:09:34.232307 18009 region_segmentation.cpp:360] Region output frame 4
I0708 19:09:34.243295 18009 region_segmentation.cpp:360] Region output frame 5
F0708 19:09:34.249639 18009 boundary.cpp:294] Check failed: region_id != segment.right_region (194 vs. 194) 
*** Check failure stack trace: ***
    @     0x7f2b6701cdaa  (unknown)
    @     0x7f2b6701cce4  (unknown)
    @     0x7f2b6701c6e6  (unknown)
    @     0x7f2b6701f687  (unknown)
    @           0x4896e0  segmentation::BoundaryComputation::TraceBoundary()
    @           0x488335  segmentation::BoundaryComputation::ComputeBoundary()
    @           0x4834dd  segmentation::Segmentation::RetrieveSegmentation3D()
    @           0x479287  segmentation::RegionSegmentation::SegmentAndOutputChunk()
    @           0x47759e  segmentation::RegionSegmentation::ProcessFrame()
    @           0x45470f  segmentation::RegionSegmentationUnit::ProcessFrame()
    @           0x458b74  video_framework::VideoUnit::ProcessFrameFromSender()
    @           0x4950b9  video_framework::VideoUnit::ProcessFrameImpl()
    @           0x4a796f  video_framework::VideoPipelineSource::Run()
    @     0x7f2b64fb8a4a  (unknown)
    @     0x7f2b65853182  start_thread
    @     0x7f2b621ed30d  (unknown)
    @              (nil)  (unknown)
Aborted

This is on linux (Ubuntu 14.04), with video_segment compiled with gcc-4.8.

grundman commented 10 years ago

Interesting, I replicated that as well. We haven't had any crash on videosegmentation.com, strange stuff. Looking into it.

Matthias

(810) 643-1383 www.mgrundmann.com

On Tue, Jul 8, 2014 at 7:11 PM, Kevin Squire notifications@github.com wrote:

When running seg_tree_sample on the input file in the video_example directory (and on other files), I'm getting

... I0708 19:09:34.188959 18009 region_segmentation.cpp:360] Region output frame 0 I0708 19:09:34.198417 18009 region_segmentation.cpp:360] Region output frame 1 I0708 19:09:34.209580 18009 region_segmentation.cpp:360] Region output frame 2 I0708 19:09:34.221459 18009 region_segmentation.cpp:360] Region output frame 3 I0708 19:09:34.232307 18009 region_segmentation.cpp:360] Region output frame 4 I0708 19:09:34.243295 18009 region_segmentation.cpp:360] Region output frame 5 F0708 19:09:34.249639 18009 boundary.cpp:294] Check failed: region_id != segment.right_region (194 vs. 194) * Check failure stack trace: * @ 0x7f2b6701cdaa (unknown) @ 0x7f2b6701cce4 (unknown) @ 0x7f2b6701c6e6 (unknown) @ 0x7f2b6701f687 (unknown) @ 0x4896e0 segmentation::BoundaryComputation::TraceBoundary() @ 0x488335 segmentation::BoundaryComputation::ComputeBoundary() @ 0x4834dd segmentation::Segmentation::RetrieveSegmentation3D() @ 0x479287 segmentation::RegionSegmentation::SegmentAndOutputChunk() @ 0x47759e segmentation::RegionSegmentation::ProcessFrame() @ 0x45470f segmentation::RegionSegmentationUnit::ProcessFrame() @ 0x458b74 video_framework::VideoUnit::ProcessFrameFromSender() @ 0x4950b9 video_framework::VideoUnit::ProcessFrameImpl() @ 0x4a796f video_framework::VideoPipelineSource::Run() @ 0x7f2b64fb8a4a (unknown) @ 0x7f2b65853182 start_thread @ 0x7f2b621ed30d (unknown) @ (nil) (unknown) Aborted

This is on linux (Ubuntu 14.04), with video_segment compiled with gcc-4.8.

Reply to this email directly or view it on GitHub https://github.com/videosegmentation/video_segment/issues/4.

kmsquire commented 10 years ago

Cool, thanks!

On Thursday, July 10, 2014, grundman notifications@github.com wrote:

Interesting, I replicated that as well. We haven't had any crash on videosegmentation.com, strange stuff. Looking into it.

Matthias

(810) 643-1383 www.mgrundmann.com

On Tue, Jul 8, 2014 at 7:11 PM, Kevin Squire <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

When running seg_tree_sample on the input file in the video_example directory (and on other files), I'm getting

... I0708 19:09:34.188959 18009 region_segmentation.cpp:360] Region output frame 0 I0708 19:09:34.198417 18009 region_segmentation.cpp:360] Region output frame 1 I0708 19:09:34.209580 18009 region_segmentation.cpp:360] Region output frame 2 I0708 19:09:34.221459 18009 region_segmentation.cpp:360] Region output frame 3 I0708 19:09:34.232307 18009 region_segmentation.cpp:360] Region output frame 4 I0708 19:09:34.243295 18009 region_segmentation.cpp:360] Region output frame 5 F0708 19:09:34.249639 18009 boundary.cpp:294] Check failed: region_id != segment.right_region (194 vs. 194) * Check failure stack trace: * @ 0x7f2b6701cdaa (unknown) @ 0x7f2b6701cce4 (unknown) @ 0x7f2b6701c6e6 (unknown) @ 0x7f2b6701f687 (unknown) @ 0x4896e0 segmentation::BoundaryComputation::TraceBoundary() @ 0x488335 segmentation::BoundaryComputation::ComputeBoundary() @ 0x4834dd segmentation::Segmentation::RetrieveSegmentation3D() @ 0x479287 segmentation::RegionSegmentation::SegmentAndOutputChunk() @ 0x47759e segmentation::RegionSegmentation::ProcessFrame() @ 0x45470f segmentation::RegionSegmentationUnit::ProcessFrame() @ 0x458b74 video_framework::VideoUnit::ProcessFrameFromSender() @ 0x4950b9 video_framework::VideoUnit::ProcessFrameImpl() @ 0x4a796f video_framework::VideoPipelineSource::Run() @ 0x7f2b64fb8a4a (unknown) @ 0x7f2b65853182 start_thread @ 0x7f2b621ed30d (unknown) @ (nil) (unknown) Aborted

This is on linux (Ubuntu 14.04), with video_segment compiled with gcc-4.8.

Reply to this email directly or view it on GitHub https://github.com/videosegmentation/video_segment/issues/4.

— Reply to this email directly or view it on GitHub https://github.com/videosegmentation/video_segment/issues/4#issuecomment-48660458 .

grundman commented 10 years ago

Fixed.

kmsquire commented 10 years ago

Cool, thanks!

videosegmentation / video_segment

boundary.cpp:294] Check failed: region_id != segment.right_region (194 vs. 194) #4