[Webkit-unassigned] [Bug 137692] [EFL] REGRESSION(r173394): MiniBrowser stucked in an infinite loop if NETWORK_CACHE is disabled

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 3 02:33:30 PST 2015


https://bugs.webkit.org/show_bug.cgi?id=137692

Csaba Osztrogonác <ossy at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[EFL] REGRESSION(r173394):  |[EFL] REGRESSION(r173394):
                   |MiniBrowser stucked in an   |MiniBrowser stucked in an
                   |infinite loop on            |infinite loop if
                   |http://index.hu if          |NETWORK_CACHE is disabled
                   |NetworkProcess is enabled   |

--- Comment #5 from Csaba Osztrogonác <ossy at webkit.org> ---
(In reply to comment #4)
> (In reply to comment #3)
> > just to note: https://trac.webkit.org/changeset/192994 skipped all wpt tests.
> > They should be unskipped once somebody fixes this very old regression.
> 
> To fix it, I file a new bug - https://bugs.webkit.org/show_bug.cgi?id=151801

Common, why do we need a new bug report for the same bug?

REGRESSION(r192994): imported/w3c/web-platform-tests has been timeout since r192994
https://bugs.webkit.org/show_bug.cgi?id=151801

Otherwise the name of the new bug is misleading, because r192994 only
made NetworkProcess mandatory, it isn't the real culprit. It is a 15
months old bug caused by r173394. But it was hidden, because EFL
didn't use NetworkProcess at all until it became mandatory.


https://bugs.webkit.org/show_bug.cgi?id=151801#c2 pointed out
that the problem occurs only if NETWORK_CACHE is disabled.

So one possible fix can be to enable NETWORK_CACHE on EFL port too
similar to Apple Mac and GTK port. In this case can we get rid
NETWORK_CACHE guards since all ports enabled it? And we see that
networking is broken with disabled NETWORK_CACHE long time ago.
Is there any reason to keep this broken configuration in the tree?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151203/aeb50ff6/attachment.html>


More information about the webkit-unassigned mailing list