Bug 125073
| Summary: | Web Inspector: [EFL] The remote inspector stuck in infinite loop. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | László Langó <llango.u-szeged> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | gyuyoung.kim, inspector-bugzilla-changes, j.isorce, mcatanzaro, m.morais, obzhirov, ossy, vivek.vg, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
László Langó
The remote inspector does not work on EFL correctly. After start with this command: "WEBKIT_INSPECTOR_SERVER=127.0.0.1:2999 ./MiniBrowser"
When I try to connect to "http://localhost:2999/Main.html?page=1", it stuck in an infinite loop and print this error message to the console:
ERR<13143>:ecore ecore_main.c:1531 _ecore_main_fd_handlers_bads_rem() Removing bad fds
ERR<13143>:ecore ecore_main.c:1573 _ecore_main_fd_handlers_bads_rem() No bad fd found. Maybe a foreign fd from glib?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16070880>
Anton Obzhirov
It seems like the problem is still there so if nobody is working on it at the moment I can have a look.
Csaba Osztrogonác
just a note: https://trac.webkit.org/changeset/172438 disabled
the zillion of warnings. Maybe it affected this bug too.
László Langó
(In reply to comment #2)
> It seems like the problem is still there so if nobody is working on it at
> the moment I can have a look.
Unfortunatly I don't have time for that, so if you can dig into this, that would be great.
Anton Obzhirov
(In reply to comment #3)
> just a note: https://trac.webkit.org/changeset/172438 disabled
> the zillion of warnings. Maybe it affected this bug too.
Well, _ecore_main_fd_handlers_bads_rem() warnings are removed in the latest WebKit but it still gets stuck. Got some time to investigate today.
Michael Catanzaro
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.