Eigen::internal::aligned_free bug

[xq198109]

I installed the PCL-1.12.0-AllInOne-msvc2019-win64 and test the fliter function of PCL using the following code "test3", a memory problem occured when the function return and the local variable release , the debug information prompt the problem is in the function Eigen::internal::aligned_free(void *)
void test3()
{

pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new pcl::PointCloud<pcl::PointXYZ>);
pcl::PointCloud<pcl::PointXYZ>::Ptr cloud_filtered(new pcl::PointCloud<pcl::PointXYZ>);

// Fill in the cloud data
pcl::PLYReader reader;
// Replace the path below with the path where you saved your file
reader.read<pcl::PointXYZ>("E:/zhanjiang/bun_zipper.ply", *cloud);

std::cerr << "Cloud before filtering: " << std::endl;
std::cerr << *cloud << std::endl;

// Create the filtering object
pcl::StatisticalOutlierRemoval<pcl::PointXYZ> sor;
sor.setInputCloud(cloud);
sor.setMeanK(50);
sor.setStddevMulThresh(1.0);
sor.filter(*cloud_filtered);

std::cerr << "Cloud after filtering: " << std::endl;

// std::cerr << *cloud_filtered << std::endl;

pcl::PCDWriter writer;
writer.write<pcl::PointXYZ>("table_scene_lms400_inliersX.pcd", *cloud_filtered, false);

sor.setNegative(true);
sor.filter(*cloud_filtered);
writer.write<pcl::PointXYZ>("table_scene_lms400_outliersX.pcd", *cloud_filtered, false);

}

• OS: [WINDOW 10]
• Compiler: [VS 2019]
• PCL Version [1.12]

[larshg]

Could you enable AVX for the downstream project, I think this is the reason.
Its being fixed in #4698

[mvieth]

@xq198109 Would also be good to know where exactly the problem happens, ideally with a stack trace or the output of a debugger

[xq198109]

Could you enable AVX for the downstream project, I think this is the reason.
Its being fixed in #4698

thanks, the problem is solved by enabling AVX

[larshg]

Could you enable AVX for the downstream project, I think this is the reason.
Its being fixed in #4698

thanks, the problem is solved by enabling AVX

Thanks for feedback 👍

[larshg]

@xq198109 I think @kunaltyagi would like this issue to remain open, until a proper fix is merged to master, so please let it be open for now.