VirtualBox

Ticket #9676 (reopened defect)

Opened 3 years ago

Last modified 5 months ago

Virtualbox kernel.log system memory message

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

Description (last modified by frank) (diff)

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

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

Change History

comment:1 Changed 2 years ago by frank

  • Description modified (diff)

Never seen this. Still relevant with VBox 4.1.14?

Changed 23 months ago by oriste

Crash report generated on Mac OS X

comment:2 Changed 23 months ago by oriste

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

Version 0, edited 23 months ago by oriste (next)

comment:3 Changed 20 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if still relevant with VBox 4.1.22.

comment:4 Changed 19 months ago by he8us

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

Changed 19 months ago by he8us

VBox 4.2.1 crash log

Changed 19 months ago by he8us

VBox 4.1.22 crash log

comment:5 Changed 19 months ago by he8us

  • Status changed from closed to reopened
  • Resolution fixed deleted

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 Changed 5 months ago by xdissent

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 Changed 5 months ago by frank

I doubt that.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use