Skip navigation

I just checked in bug 473845 which fixed the last persistent leak in browser chrome tests. It also dropped the leak threshold down to zero for those tests, so leakers will be spotted immediately and properly backed out.



    • Robert O'Callahan
    • Posted January 21, 2009 at 20:04 (8:04 pm)
    • Permalink


    • pd
    • Posted January 22, 2009 at 00:18 (12:18 am)
    • Permalink

    This sounds like huge news but I’m not sure. Could you elaborate? How many leaks were there in the past? What amount of leakage were they causing? Does this mean that all JS that runs the chrome UI is free from memory leaks? If that is the case, where are any remaining leaks, if there are any? Are they in the parser engine or something like that?


    • Ian M
    • Posted January 22, 2009 at 01:38 (1:38 am)
    • Permalink

    I would also like to know the answer to pd’s question.

    • Klaus
    • Posted January 22, 2009 at 01:55 (1:55 am)
    • Permalink

    You checked in a BUG. How about a solution?

  1. It simply means that our tests trigger no leaks. Nothing more, nothing less.

One Trackback/Pingback

  1. […] half-billion-dollar loss, seems okay with that Seven steps to a bootable Windows 7 thumb drive Shawn Wilsher: Browser Chrome Tests No Longer Leak The 10-inch Acer Aspire One takes some beauty shots The Mac at 25 The Mac at 25: Interface design […]

Comments are closed.