|
|
Created:
4 years, 5 months ago by jochen (gone - plz use gerrit) Modified:
4 years, 1 month ago CC:
blink-reviews, blink-reviews-html_chromium.org, chromium-reviews, dglazkov+blink Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionSprinkle some release asserts over HTMLFrameElementBase
It appears to be difficult to get this right, but it's quite bad if we
get it wrong, so rather crash.
BUG=628942
R=dcheng@chromium.org
Committed: https://crrev.com/b9e3d96067ff8c016d2505ab2a1f6b9d985c6b35
Cr-Commit-Position: refs/heads/master@{#407430}
Patch Set 1 #Patch Set 2 : updates #Patch Set 3 : updates #
Messages
Total messages: 25 (14 generated)
The CQ bit was checked by dominicc@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_android on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
The CQ bit was checked by jochen@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by jochen@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
ptal - now with less redness
This is a bit subtle but I guess LGTM, seems like a way to find out more about the problem and have crashing is a safer failure mode.
The CQ bit was unchecked by jochen@chromium.org
The CQ bit was checked by jochen@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Sprinkle some release asserts over HTMLFrameElementBase It appears to be difficult to get this right, but it's quite bad if we get it wrong, so rather crash. BUG=628942 R=dcheng@chromium.org ========== to ========== Sprinkle some release asserts over HTMLFrameElementBase It appears to be difficult to get this right, but it's quite bad if we get it wrong, so rather crash. BUG=628942 R=dcheng@chromium.org Committed: https://crrev.com/b9e3d96067ff8c016d2505ab2a1f6b9d985c6b35 Cr-Commit-Position: refs/heads/master@{#407430} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/b9e3d96067ff8c016d2505ab2a1f6b9d985c6b35 Cr-Commit-Position: refs/heads/master@{#407430}
Message was sent while issue was closed.
> Patchset 3 (id:??) landed as https://crrev.com/b9e3d96067ff8c016d2505ab2a1f6b9d985c6b35 > Cr-Commit-Position: refs/heads/master@{#407430} I'm afraid this made telemetry_perf_unittests crashy. https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel... https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel... DevtoolsTargetCrashException: Devtools target crashed ******************************************************************************** (e:\b\swarm_slave\w\irkqrqwp\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py:410 _AddDebuggingInformation) Received a socket error in the browser connection and the tab no longer exists. The tab probably crashed. ******************************************************************************** (e:\b\swarm_slave\w\irkqrqwp\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py:411 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:54787/devtools/page/5ab50a25-2804-451f-9b78-4979a95c0be7 Found Minidump: True Stack Trace: ******************************************************************************** ChildEBP RetAddr Args to Child 0018c54c 67ef2af8 0018caa0 67ef58c7 0018c66c chrome_child!base::debug::BreakDebugger+0x9 0018c554 67ef58c7 0018c66c 6a4114b8 5f72ca48 chrome_child!logging::InitChromeLogging+0x2f7 0018caa0 68aa8e37 5f72ca48 0018cca8 00000003 chrome_child!logging::LogMessage::~LogMessage+0x1c7 0018cbb4 68a5c656 5f72ca48 0018ccb8 689f018f chrome_child!blink::HTMLFrameElementBase::isURLAllowed+0xd6 0018cbc0 689f018f 3954d738 0018cca8 5f72ca48 chrome_child!blink::HTMLIFrameElement::layoutObjectIsNeeded+0xb 0018cbd4 68972daa 5f72ca48 5f72ca48 00000000 chrome_child!blink::LayoutTreeBuilderForElement::shouldCreateLayoutObject+0x93 0018ccb8 68aa8c08 0018ccd8 5f72ca48 0018cce0 chrome_child!blink::Element::attachLayoutTree+0xad 0018ccc8 6894873c 0018ccd8 5f72ca48 3954d738 chrome_child!blink::HTMLFrameElementBase::attachLayoutTree+0xe 0018cce0 6897373f 0018ccf4 3954d738 00000000 chrome_child!blink::Node::reattach+0x44 0018ccfc 68979927 3954d738 00000004 5f72ca48 chrome_child!blink::Element::buildLayoutTree+0x3f
Message was sent while issue was closed.
A revert of this CL (patchset #3 id:40001) has been created in https://codereview.chromium.org/2175313005/ by jochen@chromium.org. The reason for reverting is: Unflake bots.
Message was sent while issue was closed.
On 2016/07/26 at 09:55:38, jochen wrote: > A revert of this CL (patchset #3 id:40001) has been created in https://codereview.chromium.org/2175313005/ by jochen@chromium.org. > > The reason for reverting is: Unflake bots. This is tracked in Issue 631330
Message was sent while issue was closed.
esprehn@chromium.org changed reviewers: + esprehn@chromium.org
Message was sent while issue was closed.
lgtm
Message was sent while issue was closed.
On 2016/11/12 09:46:53, esprehn wrote: > lgtm Did you look at https://codereview.chromium.org/2497133002/ as well, which is the proposed reland? It's a bit more narrowly scoped, but in all the UXSSes I've seen, the contentFrame() assert is the important one: that's why my reland only includes it. |