{"push_id":1392485666,"size":79,"distinct_size":79,"ref":"refs/heads/master","head":"fd25e8398cf600c73594b88ca85676f44b207efa","before":"8dd24f9480cbfbd950827c6fcf0b8cdc1eab60a8","commits":[{"sha":"e7886de9e860bac867bf6e029d8c6f2a0431a7b7","author":{"name":"sky","email":"076cd1c87fce5b5cd21593afdded430a33fc4dd2@chromium.org"},"message":"Fix leak in FocusManager tests\n\nThey create a widget and never destroy it.\n\nBUG=660994, 663418\nTEST=test only change\nR=ben@chromium.org\n\nCommitted: https://crrev.com/402f62030eda12d30ad6341e2774d9af2208bee1\nReview-Url: https://codereview.chromium.org/2483083002\nCr-Original-Commit-Position: refs/heads/master@{#430457}\nCr-Commit-Position: refs/heads/master@{#430657}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/e7886de9e860bac867bf6e029d8c6f2a0431a7b7"},{"sha":"87f634f6b9b2339cbef11a21a8f40eae2a884487","author":{"name":"dpranke","email":"7798396f6bf7f0c798b6f7f8fbb12e7951f93123@chromium.org"},"message":"Fix abspath references in md_browser.\n\nI thought I had fixed this in the patch to support opening files\ndirectly in md_browser, but I got my merges confused.\n\nR=jsbell@chromium.org\n\nReview-Url: https://codereview.chromium.org/2488553002\nCr-Commit-Position: refs/heads/master@{#430658}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/87f634f6b9b2339cbef11a21a8f40eae2a884487"},{"sha":"fe00b4cbd1222caec678662685314a6aa8a032cd","author":{"name":"twellington","email":"eb27ab807510bd3efdaaaa93c83970a0edc41d10@chromium.org"},"message":"Check if the merged instance task is still running in #isStartedUpCorrectly()\n\nIf ChromeTabbedActivity's task is killed, e.g. when closing all incognito tabs\nthrough the notification, and the process doesn't die completely before the user\nattempts to restart Chrome, then sMergedInstanceTaskId will still be set to the old\ntask id that is no longer alive. Check if the merged instance task is still running\nbefore returning false in ChromeTabbedActivity#isStartedUpCorrectly().\n\nBUG=663259,657418\n\nReview-Url: https://codereview.chromium.org/2486843002\nCr-Commit-Position: refs/heads/master@{#430659}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/fe00b4cbd1222caec678662685314a6aa8a032cd"},{"sha":"e20a6fdd7a74a53b83a8be5a1db0119e77f8cacc","author":{"name":"maksim.sisov","email":"400b2ace76922c55213cbe5c6d94aae8bd3b2174@intel.com"},"message":"Make callers of FromUTC(Local)Exploded in google_apis/ use new time API.\n\nUse new time conversion API in accordance with\nhttps://codereview.chromium.org/1988663002/\n\nBUG=601900\n\nReview-Url: https://codereview.chromium.org/2091663002\nCr-Commit-Position: refs/heads/master@{#430660}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/e20a6fdd7a74a53b83a8be5a1db0119e77f8cacc"},{"sha":"072d435f6ff710649cec831aab912693bf5fc573","author":{"name":"rdevlin.cronin","email":"81cd5103f8a1d86ba367d4f0c9c846c36bae60aa@chromium.org"},"message":"[Extensions Binding] Add an APIBindingTest class\n\nUp until this point, APIBinding tests were piggy-backing on\ngin::V8Test; this worked reasonably well, but led to a bit more\nverbosity than necessary. With the change to garbage-collect v8 at the\nend of the test in order to collect all objects, the implementation is\nfar enough apart that it warrants its own test class.\n\nBUG=653596\n\nReview-Url: https://codereview.chromium.org/2481363002\nCr-Commit-Position: refs/heads/master@{#430661}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/072d435f6ff710649cec831aab912693bf5fc573"},{"sha":"3fdd951cdccbd48de88767e6156bad40ff52738d","author":{"name":"foolip","email":"ac1aa42b1e0dab9624ff0cfb3a5c64bfdfa4b715@chromium.org"},"message":"Measure usage of RTCSessionDescription's type and sdp attributes\n\nAlso measure missing members in the init dict, that is how the members\nwould end up as null, and will show how often adding required would\nthrow a TypeError due to missing type.\n\nBUG=662898\nR=guidou@chromium.org\n\nReview-Url: https://codereview.chromium.org/2490543002\nCr-Commit-Position: refs/heads/master@{#430662}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/3fdd951cdccbd48de88767e6156bad40ff52738d"},{"sha":"c6f247ed04bc2e28157968a9f7e8f195012ae614","author":{"name":"peter","email":"6214814a67b9688a08e8c6dc7fa5dee076dddc8d@chromium.org"},"message":"Create and use BlinkInterfaceProvider WeakPtrs on the same thread\n\nA race condition seems to be occurring where the reference to\nWeakReference::Flag in WeakReferenceOwner is in process of being destroyed\nwhile a new reference is being added. This happens when a document having\nWeb Workers is being destroyed (due to a reload) while, on the thread\nspecific to a worker, an API is used that binds to a Mojo Interface\nProvider.\n\nCreating the weak pointers on arbitrary threads, even though they\nconsistently get dereferenced on the main thread, seems to be unsafe\nin this situation.\n\nInstead, create a single WeakPtr<> on the main thread during construction,\na copy of which can be made on the worker threads. This will increase the\nreference count of the WeakReference::Flag, which is a thread-safe ref\ncounted object.\n\nBUG=649645\n\nReview-Url: https://codereview.chromium.org/2476543003\nCr-Commit-Position: refs/heads/master@{#430663}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/c6f247ed04bc2e28157968a9f7e8f195012ae614"},{"sha":"e62f7381e964829070b166127bffb8c1a742c2e0","author":{"name":"thestig","email":"f37b68741aa3bbb42c899bf497ab6a1bd6b89325@chromium.org"},"message":"Fix some nits in content frame code.\nCQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation\n\nReview-Url: https://codereview.chromium.org/2490553002\nCr-Commit-Position: refs/heads/master@{#430664}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/e62f7381e964829070b166127bffb8c1a742c2e0"},{"sha":"14f8baa8902bdaa721fb680b81982c9140a080f4","author":{"name":"kundaji","email":"bcb33b4bd7c3b03d390da7eca47ee4d371febea1@chromium.org"},"message":"Set up DataUseWebContentsObservers for ChromeVox.\n\nSet up DataUseWebContentsObservers for the purpose of ascribing all\ndata use in Chrome to respective page load. All possible WebContents\nin Chrome that can use network data should have a\nDataUseWebContentsObserver.\n\nBUG=645188\n\nReview-Url: https://codereview.chromium.org/2486463003\nCr-Commit-Position: refs/heads/master@{#430665}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/14f8baa8902bdaa721fb680b81982c9140a080f4"},{"sha":"d6da33fd77e168bce08dfe17685e63785d4fb38f","author":{"name":"piman","email":"9d67b4c6abdacb16acdfce611657a6e65aaa1773@chromium.org"},"message":"Make SurfaceFactory lifetime match frame_sink_id_ registration in DelegatedFrameHostAndroid\n\nThis will allow further simplification/refactoring.\n\nBUG=657959\n\nReview-Url: https://codereview.chromium.org/2476303004\nCr-Commit-Position: refs/heads/master@{#430666}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/d6da33fd77e168bce08dfe17685e63785d4fb38f"},{"sha":"ba306aec9d9b09a427c4f95f095a8c039c56691a","author":{"name":"piman","email":"9d67b4c6abdacb16acdfce611657a6e65aaa1773@chromium.org"},"message":"Make SurfaceFactory lifetime match frame_sink_id registration in OffscreenCanvasCompositorFrameSink\n\nThis will allow further simplification/refactoring.\n\nBUG=657959\n\nReview-Url: https://codereview.chromium.org/2485543004\nCr-Commit-Position: refs/heads/master@{#430667}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/ba306aec9d9b09a427c4f95f095a8c039c56691a"},{"sha":"c7afa74be6ebd1f084a0c1a356fe25347e4528c8","author":{"name":"msarett","email":"ee71770266349c70ea206c942668eaa368b9cab7@google.com"},"message":"Delete qcms dependency from WebKit core and platform\n\nThis dependency is unused.  Reduces ChromePublic.Apk\nsize on Android about 50KB.\n\nBUG=660416\n\nReview-Url: https://codereview.chromium.org/2472003005\nCr-Commit-Position: refs/heads/master@{#430668}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/c7afa74be6ebd1f084a0c1a356fe25347e4528c8"},{"sha":"32f5238cedacdaacd30b01617814494f3a461d75","author":{"name":"jdonnelly","email":"8bada6add0c891215bc52fe3228ad87407eadf7c@chromium.org"},"message":"Remove legal messages from save card bubble before offering local save.\n\nBefore this change, if upload is offered and then local save is offered,\nthe legal messages associated with the upload are still present and\nincorrectly shown to the user for the local save.\n\nBUG=662169\n\nReview-Url: https://codereview.chromium.org/2488743002\nCr-Commit-Position: refs/heads/master@{#430669}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/32f5238cedacdaacd30b01617814494f3a461d75"},{"sha":"aaeeef1bb01f6ff4154652e0999ae4a8834324ca","author":{"name":"floppymaster","email":"f50225ef343ba719af3f0a12107e0f111f35d541@gmail.com"},"message":"gn: bootstrap: add base/task_scheduler/task_tracker_posix.cc to sources\n\nReview-Url: https://codereview.chromium.org/2480253005\nCr-Commit-Position: refs/heads/master@{#430670}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/aaeeef1bb01f6ff4154652e0999ae4a8834324ca"},{"sha":"daa8ffc109069ede17d1d6c313355011b972ec89","author":{"name":"dewittj","email":"f0466ff1881aec9553c6147ab996d238dc3d8b17@chromium.org"},"message":"[Offline Pages] Remove a debugging feature and a misleading flag.\n\nThe flag called \"IsBackgroundLoadingEnabled\" was being used to gate\na debug feature for saving a linked page as MHTML.  This is no longer\nneeded with the various testing tools we've built so removing the\nmisleading flag and the feature itself.\n\nSince the associated string is removed, change the existing string\nfor NTP to the one approved by UX.\n\nBUG=\n\nReview-Url: https://codereview.chromium.org/2477943002\nCr-Commit-Position: refs/heads/master@{#430671}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/daa8ffc109069ede17d1d6c313355011b972ec89"},{"sha":"56ef246026d69de2002f0068c64fb54000207bce","author":{"name":"eugenebut","email":"85177464411b54bbceca3708eccbef65e029527d@chromium.org"},"message":"Reland: [ios] Refactored back-forward navigation in CRWSessionController.\n\nNotable changes:\n - Added public -[CRWSessionController indexOfEntryForDelta:] which will\n   be used in future BF navigation refactorings (crbug.com/661858). This\n   API will allow to tell the future navigation index w/o making an\n   actual navigation and pass that future entry to\n   |isSameDocumentNavigationBetweenEntry:andEntry:| call.\n - Made goDelta: no-op if delta is out of bounds. This make\n   CRWSessionController  implementation better conform to w3 spec:\n   https://www.w3.org/TR/html5/browsers.html#the-history-interface\n - Added public canGoDelta: API and use it in canGoBack/canGoForward.\n - goBack and goForward now implemented by calling goDelta:-1 and\n   goDelta:1. This way the implementation is more efficient (no extra\n   calls of |discardNonCommittedEntries| and |discardTransientEntry|)\n   and cleaner.\n - Do not change previousNavigationIndex if navigation did not happen.\n - Added more unit tests.\n\nFurther cleanups (like reusing indexOfEntryForDelta: and\nisRedirectTransitionForEntryAtIndex:) will be done in separate CLs.\n\nBUG=661820\n\nReview-Url: https://codereview.chromium.org/2470913007\nCr-Commit-Position: refs/heads/master@{#430435}\n(cherry picked from commit 44dc0832429cf6754c254739d4939382e5ee3b71)\n\nReview-Url: https://codereview.chromium.org/2482983003\nCr-Commit-Position: refs/heads/master@{#430672}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/56ef246026d69de2002f0068c64fb54000207bce"},{"sha":"ab87a374dd800813751d405a6fdf3a4c4b3066f7","author":{"name":"qyearsley","email":"b153b088c14a637d44b240d95a22771a73fae427@chromium.org"},"message":"Update references to linux_precise_blink_rel in src.\n\nReason: We're planning to drop support for Linux Precise for layout tests.\n\nBUG=660580\nCQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel\n\nReview-Url: https://codereview.chromium.org/2470243002\nCr-Commit-Position: refs/heads/master@{#430673}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/ab87a374dd800813751d405a6fdf3a4c4b3066f7"},{"sha":"a6bdfc7c128e0e51b3717c52c113d8dcff30bcb9","author":{"name":"rsleevi","email":"b83a38e36964ae9176ee2c06099c46c13b2409f2@chromium.org"},"message":"Distrust publicly trusted SHA-1 certs\n\nReject all publicly trusted SHA-1 certificates, as announced\nSeptember 2014 at\nhttps://security.googleblog.com/2014/09/gradually-sunsetting-sha-1.html\nand\nhttps://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html\n\nTo avoid too much disruption, enterprise SHA-1\nis still allowed for M56; in M57, it will be\ndisabled unless the EnableSha1ForLocalAnchors policy is\nset, as described at\nhttps://www.chromium.org/Home/chromium-security/education/tls/sha-1\n\nAs with other TLS deprecations, an emergency 'undeprecate'\nswitch is kept around in the event of unexpected breakage,\nto allow rapid reverting to the previous behaviour.\n\nBUG=653691\n\nReview-Url: https://codereview.chromium.org/2483783003\nCr-Commit-Position: refs/heads/master@{#430674}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/a6bdfc7c128e0e51b3717c52c113d8dcff30bcb9"},{"sha":"ee88cfeecda2a6fbc58ac7d2635e048ed39f28cf","author":{"name":"xlai","email":"4d337bb981f69e1bb09c391848bc54e2c0d08b54@chromium.org"},"message":"Revert of Remove MessageLoop destruction observer from mojo::Watcher. (patchset #2 id:20001 of https://codereview.chromium.org/2475273003/ )\n\nReason for revert:\nI'm suspecting that this CL is causing these two\nlayout tests to crash on WebKit Linux Precise Leak bot:\nbroadcastchannel/blobs.html\nbroadcastchannel/workers.html\n\nbecause they are crashing on mojo::SyncHandleRegistry in a check for watcher pointer.\n\nhttps://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Precise%20Leak/builds/1578\n\nAnd this CL is the only CL in the build that touches on mojo watcher.\n\nOriginal issue's description:\n> Remove MessageLoop destruction observer from mojo::Watcher.\n>\n> mojo::Watcher currently registers itself as a destruction observer\n> of the MessageLoop on which it is instantiated. When it is notified\n> that the MessageLoop is being destroyed, it invokes its callback\n> with MOJO_RESULT_ABORTED.\n>\n> This CL removes the MessageLoop destruction observer from\n> mojo::Watcher. This allows mojo::Watcher to be instantiated on a\n> thread that doesn't run a MessageLoop (e.g. TaskScheduler threads).\n> No existing code depends on the MOJO_RESULT_ABORTED notification.\n>\n> BUG=604762\n>\n> Committed: https://crrev.com/da6bd89a95fc8c444720f3d76ac67b91dfd70280\n> Cr-Commit-Position: refs/heads/master@{#430637}\n\nTBR=rockot@chromium.org,yzshen@chromium.org,fdoray@chromium.org\n# Skipping CQ checks because original CL landed less than 1 days ago.\nNOPRESUBMIT=true\nNOTREECHECKS=true\nNOTRY=true\nBUG=604762\n\nReview-Url: https://codereview.chromium.org/2480153004\nCr-Commit-Position: refs/heads/master@{#430675}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/ee88cfeecda2a6fbc58ac7d2635e048ed39f28cf"},{"sha":"ff0a4a3f4f165290c3da7902a67d98434a49e7e3","author":{"name":"ryansturm","email":"ac718e1c2127fc88e1bc5d946a9a3c2656320e78@chromium.org"},"message":"Defer DRP start up until after the context getter is created\n\nDRP initialization will be defered until the main request context is\ncreated. Currently, DRP will force the create of the context getter\ncausing unneccesary early evaluation.\n\nBUG=662488\n\nReview-Url: https://codereview.chromium.org/2475143002\nCr-Commit-Position: refs/heads/master@{#430676}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/ff0a4a3f4f165290c3da7902a67d98434a49e7e3"}]}
{"actor":{"display_login":"dstockwell"}}