Author Topic: VFB crashes right after the start  (Read 2404 times)

2019-01-15, 10:52:29

schlasse

  • Active Users
  • **
  • Posts: 5
    • View Profile
After launching Cinema 4D and VFB, VFB crashes every time. Message: The plugin libwx_osx_cocoa.dylib has crashed.

If I delete the file libwx_osx_cocoa.dylib and then start Cinema 4D, Corona works without problems. The file is newly created. Before starting Cinema 4D again, we just have to remember to delete the file.

We use the official, finished version of the homepage with two paid licenses.

Computer # 1
macOS High Sierra
Version 10.13.6
Mac Pro (late 2013)
Processor 2.7 GHz 12-core
Memory 64 GB 1866 MHz DDR3
Graphics card AMD FirePro D500 3072 MB
Cinema 4D R20.030

Computer # 2
macOS High Sierra
Version 10.13.6
iMac Retina 4K 21.5 inch (end of 2015)
Processor 3.3 GHz Intelcore i7
Memory 16 GB 1867 MHz DDR3
Graphics card Intel Iris Pro Graphics 6200 1536 MB
Cinema 4D R20.030

Full-speed non-debug version
Build timestamp: Jan 6 2019 17:30:37
Version: 3.0 (core 3)
Cinema Version: CINEMA 4D Studio R20.030 S
Plugin status: initialized successfully

FairSaaS license active.
Activated until: 2019-02-14 (extends automatically)

Bug-Report uploaded with Private Uploader: 1547546035_BugReport.txt

2019-01-15, 12:22:49
Reply #1

beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 1363
  • Bengamin
    • View Profile
    • Cormats
Hi there, can you please supply us with the bugreport that is mentioned in the error message? Thx

2019-01-15, 13:42:10
Reply #2

schlasse

  • Active Users
  • **
  • Posts: 5
    • View Profile
Sure, of course!

I had already uploaded the bug report via https://corona-renderer.com/upload.

2019-01-15, 15:43:29
Reply #3

beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 1363
  • Bengamin
    • View Profile
    • Cormats
Thanks for the file, so this is happening on every attempt no matter the scene? When you say the file was newly created, can you elaborate on this? Sorry I'm not a Mac user :D

2019-01-15, 16:34:24
Reply #4

schlasse

  • Active Users
  • **
  • Posts: 5
    • View Profile
Hi =)

No problem.

I will use Google Translate. Hope it's all understandable =)

So it began sometime with the Daily Build 2018-12-06 or -14 that Corona just crashed when starting the VFB. I deleted the entire Corona Plugin folder and installed an older version. I think 2018-09-25. With that I could work again until the next start of Cinema 4D. After that Corona crashed again and again.

Cinema 4D start, Corona VFB open, error message. Every time.

Until I came to compare the files. I noticed that the installed files are supplemented with additional files when Corona is first opened. From then on I had to delete only the libwx_osx_cocoa.dylib and was able to use Cinema 4D and Corona quite normally. Meanwhile, I use a script that first deletes the file and then Cinema 4D starts, so I can work reasonably normal =)

A Google search has also brought me no further, because apparently no one else has the same error. My colleague with the iMac has exactly the same mistake. So it's not my MacPro.

If I search the file libwx_osx_cocoa.dylib individually, I find only entries concerning MacOS. Can it be that the file comes from the system and Apple may have screwed up there? Or is this a "corona file"?

2019-01-22, 12:45:54
Reply #5

beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 1363
  • Bengamin
    • View Profile
    • Cormats
Hi there, can you try the latest hotfix 1 release to see if this solves your error? Keep us posted. Thx

2019-01-22, 14:25:01
Reply #6

schlasse

  • Active Users
  • **
  • Posts: 5
    • View Profile
Hi and Nope :(

I've even recorded a video in which I have the hotfix 1 freshly installed and a bit with Cinema 4D messing around.

As long as the additional files in the plugin folder have not yet been created, I can close Cinema, reopen and also use the VFB as normal.
After the second opening, the additional files and also the libwx_osx_cocoa.dylib appeared (Video 01:31). The files also sometimes appear during the first use of Cinema. I have not figured out yet, when exactly the data will be created.

The next launch of Cinema (Video 01:57) and VFB brings the program to crash (Video 02:03). :(

2019-01-25, 17:03:53
Reply #7

beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 1363
  • Bengamin
    • View Profile
    • Cormats
Okay thanks, I'll add your via to our internal bug report.

2019-01-28, 10:44:13
Reply #8

schlasse

  • Active Users
  • **
  • Posts: 5
    • View Profile
Mea culpa, mea maxima culpa!!

I'm soooo sorry, but I'm afraid I found the mistake. It was a synchronization and backup tool. The tool syncs, among other things every 10 minutes our plugin folder from Cinema and then have repeatedly mixed old BETA files under the current version, which then led to errors.

It should have done with it and Corona everything works as before! I thank you for your support!

Yours sincerely
Tobi

2019-01-28, 11:23:41
Reply #9

houska

  • Corona Team
  • Active Users
  • ****
  • Posts: 1400
  • Cestmir Houska
    • View Profile
Hi Tobi,

we're glad that you found the issue! No need to be sorry, we're happy to help you any time, whatever the cause of the issue is.

I'm moving this to resolved.

Cestmir