double free or corruption (out)，Aborted (core dumped)

[1329938644]

Hello, I have successfully installed key libraries such as PCL 1.10 and GTSAM-4.2a9, and the compilation passed. However, when running the program, I keep encountering the following error:

double free or corruption (out)
Aborted (core dumped)

What could be the reason for this?

[qiaozhijian]

Could you print some messages in your code and find where this error occur?

[1329938644]

Could you print some messages in your code and find where this error occur?

Issue Report: Heap-buffer-overflow in sphericalProjection() with Apollo Dataset

Environment Details

• OS: Ubuntu 18.04
• PCL Version: 1.10.0 (compiled from source)
• GTSAM Version: 4.2a9 (commit 4f66a491)
• Compiler: GCC 8.4.0
• Build Flags:

  -DGTSAM_DIR=/usr/local/gtsam-fixed/lib/cmake/GTSAM \
  -DPCL_DIR=/usr/local/pcl-1.10/share/pcl-1.10 \
  -DCMAKE_BUILD_TYPE=RelWithDebInfo \
  -DCMAKE_CXX_FLAGS="-DEIGEN_MAX_ALIGN_BYTES=64 -fsanitize=address"
  

When processing Apollo dataset with Velodyne64 configuration:
./bin/demo_seg configs/apollo_lc_bm/gem_pagor.yaml examples/data/velodyne/source.pcd
AddressSanitizer reports:
==7530==ERROR: AddressSanitizer: heap-buffer-overflow
READ of size 4 at 0x611000034800 (256-byte region ends at 0x611000034800)
Call Stack:
#0 in travel::ObjectClusterpcl::PointXYZ::sphericalProjection()
#1 in travel::Clusterpcl::PointXYZ()
#2 in g3reg::PLCExtractor::ExtractFeature()
HIT Dataset configs/hit_ms/gem_pagor.yaml ✅ Works
Apollo Dataset configs/apollo_lc_bm/gem_pagor.yaml ❌ Fails
Debugging Attempts：
1、Verified input PCD files are valid using pcl_viewer

2、Confirmed no mixed library versions via:
ldd ./bin/demo_seg | grep -E 'pcl|gtsam'
3、Checked memory initialization in related classes

Error Context
Occurs during spherical projection of Velodyne64 point cloud
Full error log shows memory was allocated at:
0x611000034700-0x611000034800 (256 bytes)
Shadow memory indicates overflow at end of this region
Could you help identify:
Why this occurs specifically with Apollo+Velodyne64 configuration?
Whether this is a configuration issue or code bug in sphericalProjection()?
Recommended fixes for the memory boundary issue?