VirtualBox

Ticket #467 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

VBoxVRDP.exe Crashes with FC6 Guest and WinXP Host in VBoxDD.dll

Reported by: dschulz Owned by: sunlover
Priority: major Component: other
Version: VirtualBox 1.4.0 Keywords: crash vrdp NAT
Cc: Guest type: other
Host type: other

Description

I am running a text only FC6 guest install using immutable hda and hdb. Also, I am running VirtualBox as a standard user with no more permissions than a standard user.

Under heavy CPU and Network load the VBoxVRDP.exe process crashes with the message:

Window Title: vboxVRDP.exe - Application Error The instruction at "0x03414391" referenced memory at "0x0497a76e". The memory could not be "read".

If OK is pressed, then the program simply quits. If CANCEL is pressed, another message appears:

The instruction at "0x03414391" referenced memory at "0x0497a76e". The memory could not be "read". Click OK to terminate -- no CANCEL option this time.

Attached is the log for the mache. The error message in event viewer was logged at approximately the same time as the last modification to the machine's log file.

This problem is somewhat intermittent but does happen with some regularity on a number of physically different but similar machines.

Attachments

VBox.log Download (26.6 KB) - added by dschulz 7 years ago.
VBoxLog of version 1.4.0 crash
vboxcrashinfo.txt Download (10.0 KB) - added by dschulz 7 years ago.
Crashdump information of VBox 1.4.0

Change History

comment:1 Changed 7 years ago by sunlover

The VBox.log shows that you are using VirtualBox 1.3.8. Please retry with 1.4.0.

comment:2 Changed 7 years ago by dschulz

oops, I thought that machine was 1.4.0. Well, by the time I received the previous note, my 1.4.0 machine had crashed in nearly the same way. The same message with different addresses:

Application popup: VBoxVRDP.exe - Application Error : The instruction at "0x03d92ca0" referenced memory at "0x44f9059e". The memory could not be "read".

No debug option/second popup message though. But this time it asked to send information to Microsoft which it didn't with 1.3.8 (but I think this is more a factor of possible different windows patch levels even though both machines originate from a common image via sysprep.

I will attach the new vbox.log and the files that were going to be sent to Microsoft.

Changed 7 years ago by dschulz

VBoxLog of version 1.4.0 crash

Changed 7 years ago by dschulz

Crashdump information of VBox 1.4.0

comment:3 Changed 7 years ago by sunlover

Thanks for the information about 1.4.0. Do you use NAT networking in the crashed VM?

comment:4 Changed 7 years ago by dschulz

You're welcome.

Yes I am using the built into VirtualBox NAT, not windows NAT.

comment:5 Changed 7 years ago by sunlover

  • Keywords NAT added
  • Owner set to sunlover
  • Status changed from new to assigned
  • Summary changed from VBoxVRDP.exe Crashes with FC6 Guest and WinXP Host to VBoxVRDP.exe Crashes with FC6 Guest and WinXP Host in VBoxDD.dll

comment:6 Changed 7 years ago by sunlover

  • Status changed from assigned to closed
  • Resolution set to fixed

The crash was in the NAT networking code. The fix will be included in the next VBox version. Please reopen the ticket, if the problem will be still there.

comment:7 Changed 7 years ago by dschulz

WOW! 45 mins to fix! Thanks :) Will try out when new release comes out.

comment:8 Changed 7 years ago by dschulz

Any chance I could "test" the binary for you? :)

comment:9 Changed 7 years ago by sunlover

Please send me an email to vitaly at innotek dot de, I'll reply with the fixed dll.

comment:10 Changed 7 years ago by dschulz

Thanks for the DLL. I have heavily exercised the system using the software that caused the crashes before and it has worked flawlessly for more than 10X longer that it did before.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use