Bug 701585

Summary: [abrt] meshlab-1.2.2-5.fc14.1: vcg::BestDim<float>: Process /usr/bin/meshlab was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: cstent <stedchris>
Component: meshlabAssignee: Eric Smith <spacewar>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: spacewar
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:57d1fdbc526f8dd28b8a91bcb304a3d6d4abc632
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-06 05:05:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description cstent 2011-05-03 09:43:41 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 29987 bytes
cmdline: meshlab
component: meshlab
Attached file: coredump, 115785728 bytes
crash_function: vcg::BestDim<float>
executable: /usr/bin/meshlab
kernel: 2.6.35.11-83.fc14.i686
package: meshlab-1.2.2-5.fc14.1
rating: 4
reason: Process /usr/bin/meshlab was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304414252
uid: 500

How to reproduce
-----
1.load an asc file (X Y Z) to meshlab 
2.tried to use remeshing,simplification,reconstruction menu on point cloud
3.
Comment 1 cstent 2011-05-03 09:43:45 UTC 
Created attachment 496470 [details]
File: backtrace
Comment 2 Eric Smith 2011-11-10 08:53:31 UTC 
Please try 1.3.1-2, which is in rawhide and has been pushed as an update to f14, f15, and f16.  If it still happens, please provide a file that demonstrates the problem.