VirtualBox

Opened 8 years ago

Closed 7 years ago

#16657 closed defect (duplicate)

VB 5.1.18 update crashes on MacOSX 10.12.4

Reported by: andreabafile Owned by:
Component: other Version: VirtualBox 5.1.18
Keywords: Cc:
Guest type: Windows Host type: Mac OS X

Description

Frequent crashes on macosx 10.12.4 after updating to VB 5.1.18. Crashes experienced on both Win 7 and Win 10 guest. See attached log.

Attachments (2)

VBox.log (270.6 KB ) - added by andreabafile 8 years ago.
log
VBox.png (2.3 KB ) - added by andreabafile 8 years ago.
png

Download all attachments as: .zip

Change History (6)

by andreabafile, 8 years ago

Attachment: VBox.log added

log

by andreabafile, 8 years ago

Attachment: VBox.png added

png

comment:1 by Socratis, 8 years ago

  1. Duplicate of #15693, #15790, #15801, #15969, #16171, #16274, #16418, #16556, #16569.
  1. Please read: 5.1.x Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED.
  1. It's usually better and faster, if problems get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is already reported several times and someone from the developers has to deal with it and close it as "Duplicate".

comment:2 by andreabafile, 7 years ago

Dear Socratis,

thank you very much for your comments. Frankly speaking I was expecting a warmer welcome from the community. The warning pop-up I got from VB was asking to report a defect to the community and then I opened this ticket thinking I was doing something good for VirtualBox since it is my first time. I'd never expected such a complaint, also in light of the fact that I can't understand what the issue is and I'd never been able to look for that string into the forum. From my point of view this kind of task is not end-user related, but it's key user or developer. As said, I just followed the pop-up request to log a defect and attach the logs. If this is not what you expect from an end user every time he/she experience a crash, I'd really encourage you to review the pop-up instructions and guide the end user trough a different process.

comment:3 by Socratis, 7 years ago

Frankly speaking I was expecting a warmer welcome from the community.

It was a neutral reply, it wasn't a welcome or anything close to that. Would a canned "Dear andreabafile, welcome to the VirtualBox community" opening line would be preferable, more suitable? To me it would not be an honest one, but that's just me.

I'd never expected such a complaint

Complaint? Really? Part 1 was for your information, but mainly for the developers. Part 2 was for your own information/education/partial solution, and part 3 was a general remark that I copy/paste in similar cases. I didn't see the complaint, honestly. An indirect hint that you should have done your homework perhaps? Maybe, but it was so slightly hinted and it was as gentle as possible.

From my point of view this kind of task is not end-user related, but it's key user or developer.

I'm sorry, but in an open-source project, you are seeing the problem, you are supposed to report it so that the developers can tackle it. If the end-users don't report it, the developers are not going to fix it. Simple as that.

Frankly speaking as well, I wasn't expecting that reaction from you either. I would expect something more in the lines of:

"Thank you for looking at my problem and for your reply. You're right, I didn't search the forums or the bug reports before I opened the ticket. The workaround of downgrading to 5.0.x seems to work for now. I will keep in mind the forums option, thanks for pointing it out. You can close the ticket as a 'Duplicate'."

comment:4 by Frank Mehnert, 7 years ago

Resolution: duplicate
Status: newclosed

I agree with socratis. Thanks for your report but please also read the hints on this page.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette