| Summary: | [EFL] REGRESSION(r183907): It made all inspector-protocol test crash | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | gyuyoung.kim, jh718.park, joepeck, mcatanzaro, ossy |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 144714 | ||
|
Description
Csaba Osztrogonác
2015-05-07 03:11:23 PDT
The EFL bot exited early due to this bug, so we can't catch any new regression now. I skipped inspector-protocol tests on EFL to make it a little bit happier - https://trac.webkit.org/changeset/183923 (I had to comment out existing inspector-protocol expectations to avoid ambiguous expectations. This comments should be removed once this bug is fixed.) I won't have time in the near future to work on this bug, so feel free to pick it up if you are interested in working inspector on EFL. And please unskip the tests with the proper fix in the same patch. (In reply to comment #0) > STDERR: 1 0x7fbf48d13ff8 > STDERR: 2 0x7fbf4456bd40 > STDERR: 3 0x7fbf46bbf7b0 > WebKit::WebInspectorProxy::attachAvailabilityChanged(bool) > STDERR: 4 0x7fbf46d6667b > WebKit::WebInspectorProxy::didReceiveMessage(IPC::Connection&, > IPC::MessageDecoder&) Err, sorry for the breakage. Those top two frames are mysterious, are there normally unnamed frames in crash logs, and if so what might they mean? The added code in WebInspectorProxy::attachAvailabilityChanged was: > if (!m_underTest) > m_inspectorPage->process().send(Messages::WebInspectorUI::SetDockingUnavailable(!m_canAttach), m_inspectorPage->pageID()); I would expect m_inspectorPage to be valid, but I don't see us crashing otherwise =(. Are you still seeing this? Currently EFL Skips all inspector tests =( cc-ing EFL guys, I don't have time to investigate/validate this bug nowadays Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this. |