VirtualBox

Opened 13 years ago

Closed 9 years ago

#8083 closed defect (obsolete)

Virtualbox-4.0.0-69151-OSX.dmg fails to install, but installs anyway? — at Version 6

Reported by: Penelope Fudd Owned by:
Component: installer Version: VirtualBox 4.0.0
Keywords: failed Cc:
Guest type: Linux Host type: Mac OS X

Description (last modified by Frank Mehnert)

This MacOSX Snowleopard 10.6.6 (just updated) system had VirtualBox-3.2.4-62467-OSX.dmg installed, and today I attempted to upgrade to VB 4.0.0-69151. Downloaded the dmg, opened it, double-clicked on VirtualBox.mpkg, clicked next,next,next until it got to the last step (Summary), where it said:


There were errors with the installation. You may want to try installing again.

<!>

The installation failed.

The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.


In /var/log/system.log, I found this: Jan 14 10:17:51 shechinah VirtualBoxVM[364]: VirtualBoxVM(364,0x111901000) malloc: * error for object 0x10380ce08: incorrect checksum for freed object - object was probably modified after being freed.\n* set a breakpoint in malloc_error_break to debug Jan 14 10:17:55 shechinah ReportCrash[367]: Saved crash report for VirtualBoxVM[364] version 3.2.4 (3.2.4) to /Library/Logs/DiagnosticReports/VirtualBoxVM_2011-01-14-101755_shechinah.crash

I've attached the crash report.

However, when I started VB to report what version I was upgrading from, it claimed 4.0.0!

This successful "failure" is not the way things are supposed to work; it makes the product look bad.

Change History (7)

by Penelope Fudd, 13 years ago

Crash log of installation program for VirtualBox4.0.0-69151-OSX.dmg

comment:1 by Frank Mehnert, 13 years ago

According to your messages it looks like your previous version was VirtualBox 3.2.4, is that correct?

comment:2 by Penelope Fudd, 13 years ago

Yes.

comment:3 by Frank Mehnert, 13 years ago

Hmm, but you did not have a running VM while you updated, did you? Did the same happen when you updated from 4.0 to 4.0.2?

comment:4 by Penelope Fudd, 13 years ago

I don't believe I had a running VM when I updated from 3.2.4 to 4.0.0. Is 4.0.2 available now? I'll have to go try it, if so.

comment:5 by Penelope Fudd, 13 years ago

I've upgraded to 4.0.4, and the error message still occurs. No VMs were running at the time. So far, it occurs with 4.0.0, 4.0.2 and 4.0.4.

comment:6 by Frank Mehnert, 9 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use