Re: Fusion 6 and Apogee Duet Crash

nitro_jawt · ‎09-04-2013

Hi, I just installed Fusion 6, and if I have my Apogee Duet USB audio interface connected Fusion 6 crashes. If I unplug the interface then Fusion 6 runs fine... until I plug the interface in and Fusion 6 crashes. To get past the enter key screen when installing Fusion 6 I had to have the Duet disconnected - that's the point it crashed. I've used AppCleaner to completely wipe Fusion (had 5.x) off my system (which I rebuild from scratch and re-setup apps - no import of old data - about 2 weeks ago) a couple of times and rebooted in between etc - behaviour is very consistent - soon as I plug in the Duet Fusion goes boom.

Very sad, I have to chose between music and VMware fusion Please don't make me choose!!!

Crash dump attached.

changhai · ‎09-05-2013

Nitro_jawt,

I filed an internal ticket (1089144) to track this issue. meanwhile, please help upload fusion support log bundle,spanning the outage time.

1. Click VMware Fusion menu > Help > Collect Support Information to generate the .zip file on the desktop.

2. Upload .zip file to this thread through click "Use advanced editor" on the right-top of editor.

Thanks a lot for your help again!

Best Regards,

changhai

nitro_jawt · ‎09-05-2013

Hi changhai, thanks for your response. I've attached the support information as requested.

I should also note that I've connected other USB devices without problems - just the Duet seems to cause the problem.

changhai · ‎09-06-2013

Nitro_jawt,

received your uploaded file and we are evaluating this issue.

thanks a lot for your help and patience.

Best Regards,

changhai

salzo · ‎09-06-2013

USB Issues... I have a similar issue with a device my company manufactures. I work for VeriFone. We have a device that, if plugged in, or if I plug it in, VMWARE crashes. It was fine with VMWARE Fusion 5. But with Fusion 6, it crashes even if there is no VM running. HELP. I opened a problem but I don't feel there is a proactive effort to figure this out. I will even SEND YOU a device to test with. The problem is real. I've totally cleaned/reinstalled twice.

This is one of the devices:

Trident USB Device 1.1:

Product ID: 0x0217

Vendor ID: 0x11ca

Version: 1.00

Serial Number:

Speed: Up to 12 Mb/sec

Manufacturer: VeriFone Inc

Location ID: 0xfd145300 / 16

Current Available (mA): 500

Current Required (mA): 50

And this is another:

Trident USB Device 1.1:

Product ID: 0x0241

Vendor ID: 0x11ca

Version: 1.00

Serial Number:

Speed: Up to 12 Mb/sec

Manufacturer: VeriFone Inc

Location ID: 0xfd145300 / 15

Current Available (mA): 500

Current Required (mA): 50

Please take a hard look. There's something amiss with the handling of USB devices in Fusion 6. It's not me nor my installation. Fusion is fine with all my other USB device including drives, garmin, hubs, serial ports, smart card reader, etc. Just these two VeriFone devices cause Fusion to crash - with or without a VM actually running.

My customer number: 6109557859

Support confirmation number: 13370292509

THANKS!

Tom salzmann

tom@salzo.com

salzo · ‎09-06-2013

Supporting crash files:

changhai · ‎09-08-2013

saizo,

Thanks a lot for your feedback and I get your log and send to our developer.

Best Regards,

changhai

nitro_jawt · ‎09-08-2013

Any further news on this? It's driving me nuts!!!

changhai · ‎09-09-2013

nitro_jawt and saizo,

sorry to response you late and this issue is in investigation.

according to our Dev's request, please follow the steps below to collect new logs and thanks a lot for your help.

Action Plan

========

1. Disconnect the Apogee Duet USB audio device from the system.

2. On one of their VMs open Settings and check that USB is enabled. If not, click Add Device and add a USB controller to the VM.

3. Go to Settings -> Advanced and change Troubleshooting to Hang/Crash.

4. Power on the VM.

5. Connect the device to the system.

6. While the crash report dialog box is being shown go into /Library/Logs/VMware and copy out all files starting with "vmware-usbarb".

7. Upload these files.

Best Regards,

changhai

salzo · ‎09-10-2013

Here you go - 2 files - latest one was from this morning's crash but I put both in the zip file anyhow.

salzo · ‎09-10-2013

Here's the device in question:

2013-09-10T08:50:07.779-05:00| usbArb| I125: USBArb: Device 10:name:VeriFone\ Inc\ Trident\ USB\ Device\ 1.1 vid:11ca pid:0217 path:13/15/1/4/5/3 speed:full family:comm serialnum: disconnected:1 arbRuntimeKey:c version:2 id:c11ca0217 owner:(null) disconnected

This device works fine, as reported earlier, in Fusion 5.

changhai · ‎09-10-2013

saizo,

thanks a lot for our help collect logs!

will response you soon.

Best Regards,

changhai

tyronehowe · ‎09-11-2013

I have an Apogee Duet and am experiencing the same problem.

The install of Fusion 6 crashes every time at the “Welcome to VMware Fusion!” licence page (have tried several times).

If I UNPLUG the duet, then all works as expected.

The Apple crash log also specifically mentions a USB issue (first few entries listed below)

Best regards

Process: VMware Fusion [2715]

Path: /Applications/VMware Fusion.app/Contents/MacOS/VMware Fusion

Identifier: com.vmware.fusion

Version: 6.0.0 (1296151)

Code Type: X86-64 (Native)

Parent Process: launchd [171]

User ID: 501

Date/Time: 2013-09-10 09:37:59.820 +0100

OS Version: Mac OS X 10.8.4 (12E55)

Report Version: 10

Interval Since Last Report: 62815 sec

Crashes Since Last Report: 3

Per-App Interval Since Last Report: 31 sec

Per-App Crashes Since Last Report: 3

Anonymous UUID: 4CCD9F50-1F3B-70DE-2072-406A502A3C6E

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff91aa9d46 __kill + 10

1 libvmwarebase.dylib 0x0000000108ed0422 0x108a3f000 + 4789282

2 libvmwarebase.dylib 0x0000000108ecf7e7 0x108a3f000 + 4786151

3 libvmwarebase.dylib 0x0000000108ecf70b Sig_CoreDump + 11

4 libvmwarebase.dylib 0x0000000108a84f37 Panic_Panic + 151

5 libvmwarebase.dylib 0x0000000108a85082 Panic + 130

6 libvmwareui.dylib 0x00000001094d874d cui::USBDeviceRule::USBDeviceRule(unsigned int, long long, utf::string const&, utf::string const&, utf::string const&) + 1389

7 libvmwareui.dylib 0x00000001094d5ac4 cui::USBDeviceMgr::USBArbRuleEnumCallback(unsigned int, unsigned int, unsigned int, long long, char const*, char const*, char const*, UsbArbLibHandle*, void*) + 228

8 libvmwarebase.dylib 0x0000000108d50b53 0x108a3f000 + 3218259

9 libvmwarebase.dylib 0x0000000108aff597 AsyncSocketFillRecvBuffer + 247

10 libvmwarebase.dylib 0x0000000108b01001 0x108a3f000 + 794625

11 com.vmware.fusion 0x00000001079dccac 0x1078cf000 + 1105068

12 com.vmware.fusion 0x00000001079dcb63 0x1078cf000 + 1104739

13 com.apple.CoreFoundation 0x00007fff862b6fa5 __CFSocketPerformV0 + 1045

14 com.apple.CoreFoundation 0x00007fff86277b31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

15 com.apple.CoreFoundation 0x00007fff86277455 __CFRunLoopDoSources0 + 245

16 com.apple.CoreFoundation 0x00007fff8629a7f5 __CFRunLoopRun + 789

17 com.apple.CoreFoundation 0x00007fff8629a0e2 CFRunLoopRunSpecific + 290

18 com.apple.HIToolbox 0x00007fff879c4eb4 RunCurrentEventLoopInMode + 209

19 com.apple.HIToolbox 0x00007fff879c4c52 ReceiveNextEventCommon + 356

20 com.apple.HIToolbox 0x00007fff879c4ae3 BlockUntilNextEventMatchingListInMode + 62

21 com.apple.AppKit 0x00007fff87fa5533 _DPSNextEvent + 685

22 com.apple.AppKit 0x00007fff87fa4df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

23 com.apple.AppKit 0x00007fff881ef659 -[NSApplication _realDoModalLoop:peek:] + 485

24 com.apple.AppKit 0x00007fff881ef91e -[NSApplication runModalForWindow:] + 120

25 com.vmware.fusion 0x00000001078f4f5f 0x1078cf000 + 155487

26 com.vmware.fusion 0x00000001078dc0fc 0x1078cf000 + 53500

27 com.apple.CoreFoundation 0x00007fff862aaeda _CFXNotificationPost + 2554

28 com.apple.Foundation 0x00007fff8ea1b7b6 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64

changhai · ‎09-11-2013

Hello, nitro_jawt/saizo/tyronehowe,

our Dev have found the root cause for this issue:

Actually, the Apogee device's serial number is the empty string "" that cause Fusion fails to get/parse some strings which lead to Fusion UI crashed finally.

We are positively trying to deliver a fix to address this issue.

Thanks a lot for your patience!

Best Regards,

changhai

tyronehowe · ‎09-12-2013

Great news!

frogworth · ‎09-12-2013

I'm having the same problem here, only once Fusion has crashed, it crashes even after the Duet has been unplugged - only a reboot fixes it.

This is a pretty major problem for me, as I swap the soundcard in and out fairly regularly. I can try quitting Fusion whenever I need to use it, but having to reboot every time isn't ideal.

Is there any way, having purchased an upgrade from Fusion 5.x to 6.x, of downgrading until this has been fixed?

Or alternatively, any workaround?

Thanks.

nitro_jawt · ‎09-12-2013

Hi Frogworth - I downgraded back to Fusion 5.x because of these issues. What I did was use AppCleaner to remove Fusion 6.0 (making sure it didn't remove any VM's), then re-install Fusion 5.0.3 using my original key. In my case I mostly use my bootcamp partition, so I had to re-create the bootcamp VM using the wizard in Fusion 5. The bootcamp wizard did try to install VMware tools into my bootcamp partition and failed saying "newer version already installed", which makes sense, but I haven't had any problems with the Fusion 6 VMware tools in my bootcamp VM - it all works just the same as before.

And I'm very happy to say that back on Fusion 5.x the Duet works no problems

frogworth · ‎09-13-2013

Ah cool, thanks. The tricky thing is that I'm not using BootCamp, so it's a VM image and it's been upgraded to version 6 itself, so I don't know whether it'll "just work" with Fusion 5.

I guess I'll give it a go... Fingers crossed!

admin · ‎09-30-2013

This issue should be fixed in Fusion 6.0.1. Please upgrade and let me know.

nitro_jawt · ‎09-30-2013

Hi, I upgraded back to 6.0.1 last week when it came out and it's all good now with the Apogee Duet - no more crashes.

Thanks.

All

Fusion 6 and Apogee Duet Crash