VirtualBox

Opened 12 years ago

Closed 5 years ago

#9676 closed defect (wontfix)

Virtualbox kernel.log system memory message

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

Description (last modified by Frank Mehnert)

VIrtualbox 4.1.2 causes the following message to appear in kernel.log on my OS X 10.7.1 system:

VirtualBox (map: 0xffffff8010455c08) triggered DYLD shared region unnest for map: 0xffffff8010455c08,
 region 0x7fff8d000000->0x7fff8d200000. While not abnormal for debuggers, this increases system memory
 footprint until the target exits.

Is this normal?

Attachments (3)

VirtualBox_2012-05-30-192948_localhost.crash (42.0 KB ) - added by oriste 12 years ago.
Crash report generated on Mac OS X
VirtualBox_2012-09-25-153033_MacBook-Pro-de-Cedric.hang (419.2 KB ) - added by he8us 12 years ago.
VBox 4.2.1 crash log
VirtualBox_2012-09-25-151448_MacBook-Pro-de-Cedric.hang (475.2 KB ) - added by he8us 12 years ago.
VBox 4.1.22 crash log

Download all attachments as: .zip

Change History (13)

comment:1 by Frank Mehnert, 12 years ago

Description: modified (diff)

Never seen this. Still relevant with VBox 4.1.14?

by oriste, 12 years ago

Crash report generated on Mac OS X

comment:2 by oriste, 12 years ago

Hmmm, my comment disappeared. I'm getting the same error with VBox 4.1.16 on the latest MBP with 8GB memory, Mac OS X 10.7.4 after which the application quits, generating a crash report (included).

Last edited 12 years ago by oriste (previous) (diff)

comment:3 by Frank Mehnert, 12 years ago

Resolution: fixed
Status: newclosed

Please reopen if still relevant with VBox 4.1.22.

comment:4 by he8us, 12 years ago

Hello,

I have the same problem:

VirtualBox (map: 0xffffff801b576a48) triggered DYLD shared region unnest for map: 0xffffff801b576a48, region 0x7fff8c800000->0x7fff8ca00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

The only option I have is a force quit. Sometimes when I reboot, it works fine, most of time not.

I updated from 4.1.22 to 4.2.1 without success (the install worked fine).

I attached 2 reports, one with 4.1.22 and one with 4.2.1

by he8us, 12 years ago

VBox 4.2.1 crash log

by he8us, 12 years ago

VBox 4.1.22 crash log

comment:5 by he8us, 12 years ago

Resolution: fixed
Status: closedreopened

I forgot to mention that, when my computer goes to sleep (10+ minutes), when I log back, VirtualBox is launched and working fine.

comment:6 by xdissent, 10 years ago

This message has started appearing for me on Mavericks with VBox 4.3. Maybe relevant to #12241?

Nov 19 13:24:18 Crow kernel[0]: VirtualBox (map: 0xffffff801a6432d0) triggered DYLD shared region unnest for map: 0xffffff801a6432d0, region 0x7fff89400000->0x7fff89600000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

comment:7 by Frank Mehnert, 10 years ago

I doubt that.

comment:8 by aeichner, 8 years ago

Resolution: obsolete
Status: reopenedclosed

Please reopen if still relevant with a recent VirtualBox release.

comment:9 by hchumpitaz, 5 years ago

Resolution: obsolete
Status: closedreopened

Hello, I am presented with the following error in OS X 10.10 Yosemite:

VirtualBox (map: 0xffffff8039ed8d20) triggered DYLD shared region unnest for map: 0xffffff8039ed8d20, region 0x7fff92e00000->0x7fff93000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Thanks in advance.

comment:10 by aeichner, 5 years ago

Resolution: wontfix
Status: reopenedclosed

This message is actually harmless and not an error. It happens because we have to patch instructions from a loaded library for our hardening efforts. You can disable the message with the following command:

sudo sysctl -w vm.shared_region_unnest_logging=0

To make this permanent you have to add vm.shared_region_unnest_logging=0 to /etc/sysctl.conf

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use