Crash at start

[ClementDoca]

Hi, I am currently having a really troublesome bug with VirtualBox on my Mac. I can't actually be sure on the point but I think it started when I updated to Yosemite.

The problem is the following : whenever I try to start VirtualBox, the program just close itself directly (sometimes I can just see the window for a second).
I actually found out where the crash was saved and join it as an attachment.

I already tried things like removing the folder VirtualBox VMs where my virtuals are but the application was even more buggy afterwards. I also tried to completely uninstall (using a tool to completely uninstall) and install it again but the result was the same. I am currently trying to install the lastest version I could found : VirtualBox-4.3.26-98988-OSX.

Thanks a lot for your help.
Best regards.

[ADodd]

This looks a lot like an issue I'm seeing. Did you manage to fix it?

[loukingjr]

This looks a lot like an issue I'm seeing. Did you manage to fix it?

"a lot like" doesn't help much.
Minimum information needed for assistance.

[ADodd]

Np, I can provide my full info.

Host: Macbook Pro - Mid 2015

I have tried installing and running the following versions of VirtualBox:
- VirtualBox-5.0.0-101573-OSX
- VirtualBox-4.3.30-101610-OSX
- VirtualBox-4.3.26-98988-OSX

My symptom is that I open virtualbox, the virtualbox 'management' screen appears and then if I wait between 5-15 seconds (without touching anything) the application crashes.

I do not have any VMs (this is new computer and I'm trying to setup my old VMs etc, but can't get to the point of even loading them in).

I am getting errors like this in all of the crash logs:
"Application Specific Information:
abort() called
*** error for object 0x117439cb0: pointer being freed was not allocated

I will attach the full crash log files too.

Any help would be great

[loukingjr]

FWIW, I don't see anything that I know is causing a crash. VB 5.0 btw is the one you should be trying to use. As a guess, are you running any third party apps or anti-virus programs?

[ADodd]

I'm not exactly sure what you mean by third-party apps, so I'm guessing that's a no from me? And, no I don't have any anti-virus software on this computer.

This Mac is 'brand new' (both fresh from Apple and the 'new' model), so I was wondering if it might be anything in the latest hardware that that might be causing this problem?

Do you have any other ideas for me to investigate?

[loukingjr]

Third party software just means not from Apple. Sometimes programs that are designed to run in the background. The only thing I can think of right now is to run Disk Utility and repair disk permissions then see if VB 5.0 will install*. The only hardware issue I am aware of recently was a problem with Broadwell chips but that was fixed.

*I meant install and run correctly. Sometimes I don't type out what I had in mind to say.

[loukingjr]

Can you post the model of the CPU? I have a 2015 MacBook but it has the Broadwell chip which was fixed. Maybe there is a newer, different Intel CPU than the Broadwells.

[ADodd]

This command (sysctl -n machdep.cpu.brand_string) returns:
> Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz

The Intel info page for this CPU is here: ark DOT intel DOT com/products/83504/Intel-Core-i7-4870HQ-Processor-6M-Cache-up-to-3_70-GHz (I cannot post URLs yet)

Poking around wikipedia indicates that this is a Haswell CPU, not one of the new Broadwell CPUs. I hope that helps.

I have tried the fixing file permissions / uninstalling reinstalling VB trick a number of times, all with no luck.

Any other things I should try?

[loukingjr]

Actually it is a Crystal Well CPU released Q3'14. I don't know if that's an issue or not. You also have an Intel® Iris™ Pro Graphics 5200 which may be an issue as well. Maybe not. I think one of the developers will have to see. At this point i'm out of ideas.

[ADodd]

Do you think I should raise a bug report?

[loukingjr]

Can't hurt.

[ADodd]

I think I found that my issue only occurs when I have a proxy running. At the place I'm working we are behind a NTLM proxy, so I have been using the cntlm deamon. The crash only occurs if I start VirtualBox while it is running.

Win!

[loukingjr]

Sounds very plausible. You may still want to file a ticket so the developers can take a look at it.