804010 - firefox/thunderbird triggered DYLD shared region unnest for map

Status: NEW

(Core :: Widget: Cocoa, defect, P3)

Description

[Nomis101]

I'm not sure if this is the correct Component, but since a few weeks (months?) Firefox and Thunderbird are producing the following message in the OS X console everytime I quit the application:


21.10.12 21:57:34,000 kernel[0]: firefox (map: 0xffffff8021d56220) triggered DYLD shared region unnest for map: 0xffffff8021d56220, region 0x7fff88200000->0x7fff88400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.


21.10.12 21:58:53,000 kernel[0]: thunderbird (map: 0xffffff8021d565c0) triggered DYLD shared region unnest for map: 0xffffff8021d565c0, region 0x7fff88200000->0x7fff88400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.



This is on OS X 10.8.2, I see this on beta, aurora and trunk.

Comment 1

[Steven Michaud [:smichaud] (Retired)]

Testing with today's mozilla-central nightly, I see this also on OS X 10.7.5 and 10.6.8.

Here's the regression range:

firefox-2012-08-08-03-05-29-mozilla-central
firefox-2012-08-09-03-05-41-mozilla-central

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e55638d4037a&tochange=3199bc043da4

Comment 2

[Steven Michaud [:smichaud] (Retired)]

Don't know which patch in this range might be the cause/trigger.  I'll need to hg bisect.

Comment 3

[Steven Michaud [:smichaud] (Retired)]

This bug was triggered by the patch for bug 777122:

http://hg.mozilla.org/mozilla-central/rev/119935b8a413

Comment 4

[Nomis101]

(In reply to Steven Michaud from comment #3)
> This bug was triggered by the patch for bug 777122:
> 
> http://hg.mozilla.org/mozilla-central/rev/119935b8a413
Yes, you are right. If I build a build with this patch backed out, than I don't see the console message anymore. So, what can we do about that, how can we fix it?

Comment 5

[Steven Michaud [:smichaud] (Retired)]

I was hoping Rafael might have some ideas.

By the way, this bug doesn't appear to be urgent.  But it does look scary (for being so low-level).  So it'd be nice to get to the bottom of it before too long.

Comment 6

[Rafael Ávila de Espíndola (:espindola) (not reading bugmail)]

Sorry for taking so long. I want to check it out better, but from the log I am almost sure this is just the system complaining when we patch write. If that is the case, the warning would stay with nightly, but will go away for releases when we start calling _exit(0).

Comment 7

[Florian Bender]

Confirming this on Fx Beta 6 on Mac OS X 10.8.2 on every shutdown (AFAICS): 

26.11.12 14:47:25,000 kernel[0]: firefox (map: 0xffffff803ad0f0e8) triggered DYLD shared region unnest for map: 0xffffff803ad0f0e8, region 0x7fff8b800000->0x7fff8ba00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Comment 8

[Florian Bender]

… and Fx 18 b1 (the aforementioned version was Fx *17* b6): 

26.11.12 23:35:53,000 kernel[0]: firefox (map: 0xffffff803d844c18) triggered DYLD shared region unnest for map: 0xffffff803d844c18, region 0x7fff8da00000->0x7fff8dc00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Comment 9

[Rafael Ávila de Espíndola (:espindola) (not reading bugmail)]

An interesting idea that was discussed on a thread about asan is to have the main binary rexect itself setting DYLD_INSERT_LIBRARIES instead of using mach_override. I might take a look at this once I fix some higher priority bugs.

Comment 10

[Rafael Ávila de Espíndola (:espindola) (not reading bugmail)]

Attachment: minimal interpose library

It looks like interpose will work for us! The attached file is a minimal interpose library that captures writes. I will try to plug it in the firefox build tomorrow.

Comment 11

[Steven Michaud [:smichaud] (Retired)]

> I will try to plug it in the firefox build tomorrow.

I'll be very interested to see how you do this!

Comment 12

[Nomis101]

(In reply to Rafael Ávila de Espíndola (:espindola) from comment #10)
> Created attachment 691078 [details]
> minimal interpose library
> 
> It looks like interpose will work for us! The attached file is a minimal
> interpose library that captures writes. I will try to plug it in the firefox
> build tomorrow.
Have you tried, was it successfully?

Comment 13

[Rafael Ávila de Espíndola (:espindola) (not reading bugmail)]

> > It looks like interpose will work for us! The attached file is a minimal
> > interpose library that captures writes. I will try to plug it in the firefox
> > build tomorrow.
> Have you tried, was it successfully?

Sorry, the code review on reporting late writes cleared up and I went back to that as it seemed higher priority. I have been able to plug the example into the firefox build and it correctly replaces writes, but I have not finished the integration.

Comment 14

[pijacque]

kernel	kern	Debug	firefox (map: 0x47aa148) triggered DYLD shared region unnest for map: 0x47aa148, region 0x7fff87000000->0x7fff87200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

This message still exists in 2014 with Firefox 30...

Comment 15

[guigs [:guigs] PST (please needinfo me!)]

For tracking: 
https://support.mozilla.org/en-US/questions/1012997

Comment 16

[Liz Henry (:lizzard) (relman/hg->git project)]

This hang and error message was also just reported in bug 1032809.

Comment 17

[Steven Michaud [:smichaud] (Retired)]

There is no hang associated with this bug (and its error message).

Whatever that hang is, it's unrelated.

Comment 18

[7a9c0016]

I'm getting this error, too. What's the fix?

firefox (map: 0xffffff8028f61658) triggered DYLD shared region unnest for map: 0xffffff8028f61658, region 0x7fff8e800000->0x7fff8ea00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Comment 19

[Mike]

Same error; using Firefox 31 ("Firefox 31.0.dmg" downloaded 07/24/2014; Mac OS 10.7.5 "Lion"):

9/1/14 5:03:15.000 PM kernel: firefox (map: 0xffffff8013729ed0) triggered DYLD shared region unnest for map: 0xffffff8013729ed0, region 0x7fff89a00000->0x7fff89c00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Comment 20

[Mike]

This bug may lead to HFS+ file system errors:

Sep  1 17:18:50 kernel[0]: firefox (map: 0xffffff8013493658) triggered DYLD shared region unnest for map: 0xffffff8013493658, region 0x7fff88600000->0x7fff88800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Sep  1 17:19:39 kernel[0]: firefox (map: 0xffffff8014ab8960) triggered DYLD shared region unnest for map: 0xffffff8014ab8960, region 0x7fff88600000->0x7fff88800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Sep  1 17:20:33 kernel[0]: firefox (map: 0xffffff80134944d8) triggered DYLD shared region unnest for map: 0xffffff80134944d8, region 0x7fff88600000->0x7fff88800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Sep  1 17:21:17 kernel[0]: firefox (map: 0xffffff8014ab8790) triggered DYLD shared region unnest for map: 0xffffff8014ab8790, region 0x7fff88600000->0x7fff88800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Sep  1 17:30:30 kernel[0]: IOSurface: buffer allocation size is zero
Sep  1 17:38:55 kernel[0]: HFS: Very Low Disk: freeblks: 0, dangerlimit: 709

All of those lines are in succession.

Comment 21

[Steven Michaud [:smichaud] (Retired)]

This messages appear every time you quit Firefox.  As best we can tell it's entirely benign -- it has no side effects; it causes no other bugs.

We'll get to it eventually.  But (needless to say) it's not urgent.

Please, no more "me too" comments.

Comment 22

[Mike]

(In reply to Steven Michaud from comment #21)
> This messages appear every time you quit Firefox.  As best we can tell it's
> entirely benign -- it has no side effects; it causes no other bugs.
> 
> We'll get to it eventually.  But (needless to say) it's not urgent.
> 
> Please, no more "me too" comments.

The errors occur every time Firefox 31 is *started.*

The bug seems to lead to HFS+ file system trouble:

Sep  1 17:30:30 kernel[0]: IOSurface: buffer allocation size is zero
Sep  1 17:38:55 kernel[0]: HFS: Very Low Disk: freeblks: 0, dangerlimit: 709

So, my comments are not merely "more 'me too' …" -and- your "not urgent" does not obtain given that the bug is approaching 2 years.

Comment 23

[Steven Michaud [:smichaud] (Retired)]

> The bug seems to lead to HFS+ file system trouble:
>
> Sep  1 17:30:30 kernel[0]: IOSurface: buffer allocation size is zero
> Sep  1 17:38:55 kernel[0]: HFS: Very Low Disk: freeblks: 0, dangerlimit: 709

This is almost certainly unrelated.

Try Firefox on another machine.  On quitting you'll see the DYLD shared region error, but not this one.

Comment 24

[Steven Michaud [:smichaud] (Retired)]

Also, the DYLD shared region error concerns RAM, not hard disk space.

Comment 25

[Steven Michaud [:smichaud] (Retired)]

> The errors occur every time Firefox 31 is *started.*

This I haven't seen before.

It's still almost certainly unrelated to your "low disk" errors -- RAM is not hard disk space.

Comment 26

[7a9c0016]

Yes, the DYLD errors Firefox is causing with the kernel are eating a ridiculous 2GB of RAM on my machine in addition to the RAM Firefox is using 'normally'. This is causing incessant beachballs, icons to not load, memory warnings, hangs, the necessity for Force Quits, etc. 


My Console is absolutely littered with the following anytime FireFox is running:

KERNEL: firefox (map: 0xffffff804b3af878) triggered DYLD shared region unnest for map: 0xffffff804b3af878, region 0x7fff91000000->0x7fff91200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

KERNEL: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT

KERNEL: HFS: Low Disk: Vol: XXX freeblks: 261964, warninglimit: 262144


This is abnormal and should be of much higher priority than it clearly is (not):

process: kernel_task, user: root, cpu %: 0.7, threads: 99, Real Mem: 2.00GB
process: firefox, user: xxxx, cpu %: 13.9, threads: 52, Real Mem: 654.4MB


As mentioned by Mike, the errors begin immediately upon startup of Firefox, not closure.

Comment 27

[Steven Michaud [:smichaud] (Retired)]

Like I said, I haven't seen these errors on Firefox startup.  Nor have they ever been reported before (though it's possible they've been reported without sufficient information).

What's you're seeing does seem more serious.  So let's try to get to the bottom of it.

What version of OS X are you using?

You say you see these errors (on startup) with Firefox 31.  Do you see them with earlier versions of Firefox?

Do you see these errors with a clean profile?

If you have more than one computer to test on, do you also see these errors (on startup) on other machines?

Comment 28

[Steven Michaud [:smichaud] (Retired)]

One more thing:

Whoever sees these errors on startup, please report the amount of available disk space on your bootable partition -- as a number of megabytes and as a percentage of the total.  It's possible that shortage of hard disk space is playing a role here, or is even the cause of the problems.

Comment 29

[7a9c0016]

My boot drive has 75.14GBs available out of 250.14GBs total. I'm running Mt. Lion, 10.8.5. I see these errors on FF 31 through the Nightly builds, but I do not know exactly which version they began with. I do not have time right now to go through the previously posted 3 page process of creating a clean profile, but I can look into doing so later and report back.

Comment 30

[7a9c0016]

As one more thing to rule out, I have 16GBs of RAM.

Comment 31

[Ed Lee :Mardak]

My Firefox Nightly is not starting correctly, and I do see "kernel[0]: firefox (map: 0xffffff8040f2cc30) triggered DYLD shared region unnest for map: 0xffffff8040f2cc30, region 0x7fff96c00000->0x7fff96e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits."

However, I see that message /before/ selecting a profile from the profile manager, so that message is probably unrelated to Firefox being unable to start with a profile.

I believe this started earlier today, but I'll try to find a regression range.

Comment 32

[Ed Lee :Mardak]

People might be running into bug 1062042 and the only guess from looking at Console for errors is this bug.

Comment 33

[Mike]

SeaMonkey 2.29

Sep 18 14:02:59 cptrname kernel[0]: seamonkey (map: 0xd7db5c4) triggered DYLD shared region unnest for map: 0xd7db5c4, region 0x7fff87c00000->0x7fff87e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

The bug in Firefox 31 and now in SeaMonkey 29, seems to lead to an Apple Mac HFS+ problem --- I now keep the Mac's Console running, in order to catch HFS+ file system trouble ASAP (example, as previously reported):

Sep  1 17:38:55 kernel[0]: HFS: Very Low Disk: freeblks: 0, dangerlimit: 709

In addition, the following kernel event showed immediately upon running the SeaMonkey 2.29 installer:

9/18/14 12:53:53 PM	KernelEventAgent[69]	tid 00000000 received event(s) VQ_LOWDISK, VQ_VERYLOWDISK (516)

-----

I tested on 3 separate Mac's.  2 running Mac OS 10.7.5 "Lion", and 1 running Mac OS 10.6.8 "Snow Leopard.  These machines have plenty of RAM and hard drive space.

I returned to using SeaMonkey 2.26.1.  Previously, I reported that I returned to using Firefox 29.0.1.  I consider both of those versions to be reliable: The bug does *not* show in Firefox 29.0.1 and SeaMonkey 2.26.1.

Comment 34

[Mike]

(In reply to Mike from comment #33)
> SeaMonkey 2.29
> 
...
> 
> The bug in Firefox 31 and now in SeaMonkey 29, seems to lead to an Apple Mac

SeaMonkey 2.29 ... duh.

Comment 35

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.