Fusion 6.0.2 XP Windows crash report

[ChipMcK]

1. Shutdown XP Windows
2. Window: Preparing to copy
3. Clicked on X to cancel
4. Crash report

Attach the crash report

[YingFeng_Ou]

Hi ChipMck,

     So sorry for the latency and there's still no any progress here. I really very appreciate your patience and I've update your information to the internal bug but there's truly no progress yet.

     I assure you will be informed once there's progress. 

     For the workaround, did you ever try to reinstall the VMware tools by click menu Virtual Machine->Install VMware Tools?

     Another choice is to install a new customized Windows XP VM and choose the vmdk file in your issue WinXP VM bundle when ask for create a new virtual disk or choose existing virtual disk.

[ChipMcK]

Tried both and still  .  .  . 

1. All VMs shutdown
2. Quit VMware Fusion
3. Up pops dialog "Preparing to copy . . .", which closes
4. Crash Report for VMware Fusion

Syslog shows XP VM was exited and then again exited for the quit.

[ChipMcK]

v6.0.3 and the crash still occurs

1. Shutdown all VMs
2. Quit VMWare Fusion
3. dialog "Preparing to copy", which closes
4. Crash report from VMWare Fusion

[ChipMcK]

First opened 2013-11-11

Reported progress: none

Reported on r602, also fails r603

Any Progress?

Message was edited by: Charles B. Mc Kennie

[ChipMcK]

Bump 3

[wila]

Hi ChipMcK

While I understand that you are getting frustrated.. the forums are not the official support channel.

Strange but true. If you want support the correct way is to open a support ticket, the forums are for peer support, aka other users helping each other out.

FWIW, I have never seen the problem you are describing nor do I see it reported by others (at least not common enough for me to remember it). It is likely that there's something specific to your  setup or environment that triggers this problem.

Somewhere in your replies you mention that it happens when an iPod is connected? It only happens if the iPod is connected? I notice that you have a lot of things connected on a few USB hubs, that might play a role.

It is crucial for the Fusion team to be able to reproduce your issue, without that they cannot fix it.

So trying to find what is different in your setup on triggering the crash helps a lot in order to get help.

If you create a new Windows XP VM, no special settings, just install VMware Tools, can you still reproduce the issue?

--

Wil

[ChipMcK]

wila wrote:

If you create a new Windows XP VM, no special settings, just install VMware Tools, can you still reproduce the issue?

Been there, done  that: Yes

iPod is bit red herring. Use of any USB device (and removal) seems to be involved.

1. prepare to quit VF, release USB attachments, etc.

2. shut down all VM (none suspended)

3. Quit VF

4. Dialog box "Preparing to copy", which closes

5. Crash Report

[mudaltsov]

Hi ChipMcK,

I apologize for the extremely long delay before looking into this issue.

I'm not sure why using USB devices would trigger this problem for you. The "Preparing to copy" dialog that you're seeing is only used for Copy and Paste & Drag and Drop functionality between Tools and Fusion.

Could you try disabling File Copy and Paste to see if it avoids the problem?

To do this, shut down the VM and quit Fusion, then add these lines to the .vmx file:

isolation.tools.copyPaste.File.disable = "TRUE"

isolation.tools.copyPaste.FileContent.disable = "TRUE"

If that still doesn't help, try to disable File Drag and Drop also:

isolation.tools.dnd.File.disable = "TRUE"

isolation.tools.dnd.FileContent.disable = "TRUE"

Alternatively, Virtual Machine -> Settings... -> Isolation allows turning off the full Copy and Paste & Drag and Drop functionality, although it may limit the usability too much.

[ChipMcK]

I will try this, but  .  .  .

2. shut down all VM (none suspended)

3. Quit VF

With all VM shut down, File Copy and Paste  should not  be active/involved.

[mudaltsov]

I agree that it should not be involved, but the crash log shows otherwise. It's likely that the issue occurs if Fusion somehow fails to clear the pasteboard after the VM shuts down/suspends. I would like to confirm this to narrow down the problem and also help you avoid the crash for now.

Copy and Paste (as well as Drag and Drop) for large files between guest and host is implemented using a "file promise" pasteboard type. This means that the file data is not available immediately as with other file types, such as a file path on the host or data directly within the pasteboard. Instead, the file promise is resolved when the paste command is actually issued, and the application that created the pasteboard item is asked to create the promised file.

The crash log shows that the system explicitly requests the promised pasteboard data while Fusion is quitting, probably to ensure that any copied data is still available for pasting after Fusion quits. And the crash occurs because the VM is no longer available. I'll be investigating fixing the crash as well as ensuring that the pasteboard is cleared when the VM is no longer available.

[ChipMcK]

Curious.  What is name of the VM in the dump/crash ?

Quick abbreviated test: success.

I will do full test later today.

[mudaltsov]

The Apple crash logs don't have any information about which VM was in use, but the last vmware-vmfusion.log file you uploaded on April 4th has the path "/Volumes/Virtuals/Virtual Machines/XP Pro 22507 MYM.vmwarevm/XP Pro 22507 MYM.vmx"

Instead of editing each .vmx file manually, you can also apply config options to all VMs, by creating/editing the user-global config file: ~/Library/Preferences/VMware\ Fusion/config

There should already be a 'preferences' file in the same directory, but the config file usually has to be created.

If an individual .vmx file contains the same config options as the global file, the .vmx file will take precedence.

[ChipMcK]

Did a full test: success - no crash report.

This is the pair added to the .vmx file

isolation.tools.copyPaste.File.disable = "TRUE"

isolation.tools.copyPaste.FileContent.disable = "TRUE"

[mudaltsov]

Thanks for the confirmation, and glad to hear that the config options helped. Hopefully your VMs are still usable without file copy/paste between guest and host (drag and drop should still work).

I was able to reproduce the issue and will look into fixing it in a future version of Fusion.

[ChipMcK]

mudaltsov wrote:

I was able to reproduce the issue and will look into fixing it in a future version of Fusion.

That's good!  I need not be prepared to gather more documentation. The circumvention/workaround is easy to propagate to additional VM's, as needed.