I have some LAS Lidar point cloud files that are of version 1.4 of the LAS format that cause ParaView to crash. For the moment I have the ability to down-covert these files to version 1.3 (or 1.2) of the file format, and ParaView handles these. So I’m just reporting this as a bug because ParaView should do something other than crashing when encountering these files. Ideally it should handle the newer format, but at the very least just report that the format isn’t handled and use an earlier LAS format in the console window.
This is tested on Linux, MS-Windows and MacOS.
Here’s the relevant part of the crash output when running on Linux:
[load 1.4 LAS file]
terminate called after throwing an instance of ‘std::out_of_range’
what(): version minor out of range
Loguru caught a signal: SIGABRT Stack trace: 62 0x40772d paraview() [0x40772d]
the “version minor out of range” message probably comes from the LAStools, or whatever LAS library is being used.