animation plugin crashes

[ospeleo]

Hi,

I've discovered and have been using cloudcompare for more than a hundred hours now, on 2 old computers (intel core2duo, 4gb ram, osx 10.6.8 / osx 10.11.5). It's amazing how CC can handle big files and point numbers. Thank you for this amazing software.

While beginning to discover the qAnimation plugin, I get consistent crashes on 3 differents clouds (small 10k points / medium 1m points).

OSX 10.11.5 CC 2.7.0
2 viewports, launch the animation plugin
The preview works fine but when I hit "render", CC crashes immediately

Any hint of how I can manage to have this plugin work?

error generated:

Code: Select all

Process:               CloudCompare [617]
Path:                  /Applications/CloudCompare.app/Contents/MacOS/CloudCompare
Identifier:            ???
Version:               2.7.0 (2.7.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           CloudCompare [617]
User ID:               501

Date/Time:             2016-06-23 16:02:51.656 +0200
OS Version:            Mac OS X 10.11.5 (15F34)
Report Version:        11
Anonymous UUID:        FB8C2017-0DB2-C452-0752-F9AD32F8F239

Time Awake Since Boot: 2400 seconds
System Integrity Protection: enabled
Crashed Thread:        Unknown

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
  rax: 0x0000000010c91820  rbx: 0x0000000010c73d28  rcx: 0x0000000000000000  rdx: 0x0000000010c8e8b8
  rdi: 0x0000000010c73d28  rsi: 0x00007fff5fbfab18  rbp: 0x00007fff5fbfa7c0  rsp: 0x00007fff5fbfa708
   r8: 0x0000000000000002   r9: 0x00000000ffff0000  r10: 0x0000000011204201  r11: 0x000000001015a0ad
  r12: 0x00000000000003b0  r13: 0x0000000000064000  r14: 0x0000000000000001  r15: 0x00007fff5fbfab18
  rip: 0x0000000010384c74  rfl: 0x0000000000010246  cr2: 0x0000000010384c6b
  
Logical CPU:     1
Error Code:      0x00000000
Trap Number:     6


Binary images description not available


External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 19
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 91521
    thread_create: 0
    thread_set_state: 0

Model: Macmini3,1, BootROM MM31.00AD.B00, 2 processors, Intel Core 2 Duo, 2,53 GHz, 4 GB, SMC 1.35f1
Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB

[daniel]

Yep, can you try to change the output file format from mp4 to mpg?

[ospeleo]

Changing the extension name doesn't change anything : still an immediate crash when clicking "render".

It is not linked with the hardware, since rebooting the computer and launching CloudCompare 2.7.0 on Windows10 (dual boot, same computer), I am able to use the qAnimation plugin at high frame rate and high bitrate without any problem.

Maybe a problem in the port of qAnimation/CC on OSX ?

My personnal problem is solved (using windows), but I can continue to investigate on OSX if you give me some leads.

(ps: back from holiday + reply notification should make me more active)

[daniel]

Ah, OS X seems to be quite mysterious.

For what I know Andy (the Mac OS guy ;) could generate video files on his own config... It would be good to have feedback from other Mac OS users to understand if it's a general issue or not.

[TheOrdinaryMan]

Hey,

I'm having the same problem on my Macbook Pro 2012 (Retina). High Sierra Version 10.13.4. Immediately crashes when I click render. Changing file formats does not help. Changing from Super Resolution to Zoom and vice versa did not help. Changing to an older version of cloudCompare did not help. I tried using the fix from the other thread:

http://www.danielgm.net/cc/forum/viewto ... =17&t=2917

But all that did for me was completely remove the animation plugin button from the menu. Is there any progress towards a fix, or did anyone else have any luck getting it to run?