VirtualBox

Ticket #18011 (new defect)

Opened 13 months ago

Last modified 13 months ago

Video capture doesn't work after upgrade from 5.1.38 to 5.2.18

Reported by: liuqunrui Owned by:
Component: other Version: VirtualBox 5.2.18
Keywords: Cc:
Guest type: other Host type: Mac OS X

Description

Hello, I upgrade virtualbox from 5.1.38 to 5.2.18 in macOS,When I select video capture, the logo in circling as usual,but when I select the video capture menu to stop record, virtualbox accidental exit, and report error logs:

Process: VirtualBoxVM [2415] Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM Identifier: org.virtualbox.app.VirtualBoxVM Version: 5.2.18 (5.2.18) Code Type: X86-64 (Native) Parent Process: VBoxSVC [2398] Responsible: VirtualBoxVM [2415] User ID: 501

Date/Time: 2018-09-26 17:53:06.105 +0800 OS Version: Mac OS X 10.14 (18A391) Report Version: 12 Anonymous UUID: C4C75F89-7917-7BF9-E78F-33B91F94813E

Sleep/Wake UUID: 675035FF-A6C2-4DF2-989F-A72F323ED416

Time Awake Since Boot: 29000 seconds Time Since Wake: 3300 seconds

System Integrity Protection: enabled

Crashed Thread: 4 nspr-2

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [2415]

Change History

comment:1 Changed 13 months ago by socratis

Duplicate of #17307.

See there for workarounds, mainly about installing the Development snapshots.

comment:2 Changed 13 months ago by liuqunrui

installed the Development snapshots, virtualbox crash again when stop video capture:

Process: VirtualBoxVM [3699] Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM Identifier: org.virtualbox.app.VirtualBoxVM Version: 5.2.97 (5.2.97) Code Type: X86-64 (Native) Parent Process: VBoxSVC [3690] Responsible: VirtualBoxVM [3699] User ID: 501

Date/Time: 2018-09-29 08:57:08.959 +0800 OS Version: Mac OS X 10.14 (18A391) Report Version: 12 Anonymous UUID: C4C75F89-7917-7BF9-E78F-33B91F94813E

Sleep/Wake UUID: 7613168E-72FB-46EF-8271-4DC588253691

Time Awake Since Boot: 73000 seconds Time Since Wake: 1200 seconds

System Integrity Protection: enabled

Crashed Thread: 2 nspr-2

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000004 Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [3699]

comment:3 Changed 13 months ago by socratis

Can you please open a new thread in the  VirtualBox on Mac OS X Hosts section of the forums, and discuss the problem there? There are a lot more eyes/users there that could have a similar setup as you (I assume 10.13.x) that could verify/refute what you're seeing.

Please be sure to mention that you came from the bug tracker and include the ticket number.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use