Community Q&A

Where Wwise users help each other out!

Audiokinetic's Community Q&A is the forum where Wwise users ask and answer questions within the Wwise community. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Unity Crash 2019.3.15f1 with latest WWise plugin

+1 vote

Hi folks, wondering if you could help me? We've just integrated the latest Unity release into our project and discovered post integration that it's crashing the mac editor.

We're using Unity 2019.3.15f1 (and have to use Unity 2019.3 for platform support reasons). Any ideas?

[MODES] Loading mode Default (0) for mode-current-id-Anonymous-game

2020-06-18 17:05:18.432 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.435 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.439 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.440 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.441 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.442 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:18.442 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

Adding genesis user token Adding genesis user token Adding genesis user token Adding genesis user token Adding genesis user token Adding genesis user token 2020-06-18 17:05:19.420 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.421 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.421 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.421 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.422 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.422 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

2020-06-18 17:05:19.422 Unity[717:7591] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000

[Project] Loading completed in 58.807 seconds

Project init time: 3.311 seconds

Template init time: 0.000 seconds

Services packages init time: 0.000 seconds

Package Manager init time: 0.000 seconds

Asset Database init time: 0.000 seconds

Global illumination init time: 0.000 seconds

Assemblies load time: 0.000 seconds

Unity extensions init time: 0.003 seconds

Asset Database refresh time: 0.000 seconds

Scene opening time: 6.266 seconds

Subscribe to USB device events

Adding genesis user token Refreshing native plugins compatible for Editor in 44.22 ms, found 33 plugins.

[warn] kqueue: Too many open files

[err] evsignal_init: socketpair: Too many open files

Obtained 7 stack frames.


Native stacktrace:


Obtained 10 stack frames.

Obtained 10 stack frames.

Obtained 9 stack frames.

Obtained 10 stack frames.

0   libmonobdwgc-2.0.dylib              0x000000014fb2a656 mono_handle_native_crash + 242

1   libmonobdwgc-2.0.dylib              0x000000014fa8b32d mono_sigsegv_signal_handler + 220

2   libsystem_platform.dylib            0x00007fff730f35fd _sigtramp + 29

3   libCommonPreferences.dylib          0x0000000123771760 _ZL9Demangled + 5288

4   Chromium Embedded Framework         0x000000011bdd716c cef_zip_reader_create + 133612

5   Chromium Embedded Framework         0x000000011bdd6d52 cef_zip_reader_create + 132562

6   Chromium Embedded Framework         0x000000011bdd63c5 cef_zip_reader_create + 130117

7   libsystem_c.dylib                   0x00007fff72fa413c __cxa_finalize_ranges + 319

8   libsystem_c.dylib                   0x00007fff72fa4412 exit + 55

9   Chromium Embedded Framework         0x000000011beda24e cef_time_delta + 748878

10  Chromium Embedded Framework         0x000000011bedb33d cef_time_delta + 753213

11  Chromium Embedded Framework         0x000000011beda6c1 cef_time_delta + 750017

12  Chromium Embedded Framework         0x000000011bed8f6e cef_time_delta + 744046

13  Chromium Embedded Framework         0x000000011be614a1 cef_time_delta + 253857

14  Chromium Embedded Framework         0x000000011bea2cca cef_time_delta + 522186

15  Chromium Embedded Framework         0x000000011becdae6 cef_time_delta + 697830

16  Chromium Embedded Framework         0x000000011bec964b cef_time_delta + 680267

17  libsystem_pthread.dylib             0x00007fff730ff109 _pthread_start + 148

18  libsystem_pthread.dylib             0x00007fff730fab8b thread_start + 15

Obtained 14 stack frames.

Thread 0x70000dc36000 may have been prematurely finalized


Debug info from gdb:


(lldb) command source -s 0 '/tmp/mono-gdb-commands.CXgbfO'

Executing commands in '/tmp/mono-gdb-commands.CXgbfO'.

(lldb) process attach --pid 717

Obtained 7 stack frames.

Obtained 16 stack frames.

Thread 0x70000d81e000 may have been prematurely finalized

Obtained 7 stack frames.

error: attach failed: Error 1


=================================================================

Got a SIGSEGV while executing native code. This usually indicates

a fatal error in the mono runtime or one of the native libraries 

used by your application.

=================================================================
asked Jun 18 in General Discussion by Kieran N. (110 points)

1 Answer

0 votes
I have also gotten the same thing on a fresh wwise project install.

Unity version: 2019.3.14f1

Wwise version: 2019.2.5.7349

Edit:

Uninstalled from 2019.2.5 and used 2019.2.4.7329.1806 and error still occurs.

I can integrate it into another empty project so the problem occurs only with the existing project.

We have quite a few assets that it might be loading up so the problem could be there?

Edit again:

Restarting kind of fixes the issue I guess?
answered Aug 26 by Max K. (160 points)
...