New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 636699 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Problem loading content using promises (angularjs)

Reported by rafael.c...@gmail.com, Aug 11 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Example URL:
http://212.227.143.28:8081/

Steps to reproduce the problem:
1. Enter the app on specified URL
2. Try to filter using box "Find issue" (for example, try to filter by user john.doe)
3. It "freezes" on "Please wait"

What is the expected behavior?
Ends loading and show only rows that contains words used in "Find issue" text field (for example, if john.doe was used on filter, we'll see 5 rows instead of initial 6).

What went wrong?
Since 52.0.2743.116 it keeps showing "Please wait" message and never ends loading (it also fails on Canary and all releases after 52.0.2743 which I've tested).

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes It works on 51.0.2704.103 and previous

Does this work in other browsers? Yes 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0

As I've said it works perfectly on Firefox, IE11 and Edge (basically on all other browsers which I've tested). I've uploaded source code of this example project to github: https://github.com/rafaelcastillolopez/issues (but I have more webapps with the same problem)
 
Cc: tkonch...@chromium.org
Labels: -Type-Bug Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Tested the same on win8.1 chrome version 52.0.2743.116 and canary 54.0.2827.0 -  It "freezes" on "Please wait"

This is working fine on win chrome version 51.0.2704.103. Hence this is regression

This is working fine in Firefox browser as well
Labels: Needs-Bisect
Cc: joh...@chromium.org
Labels: -Needs-Bisect M-54
Owner: japhet@chromium.org
Status: Assigned (was: Untriaged)
Below is the bisect Info:

Good Build: 52.0.2733.0 
Bad Build: 52.0.2734.0

Bisect Tool Info:
You are probably looking for a change made after 393034 (known good), but no later than 393044 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/dfad350a05c0affd2819a8e5b8025d50c7aa5508..fe8a72da89b1941cccdd54a0da548540360286a6

Possible suspect : https://codereview.chromium.org/1923003002

Please reassign if this is not related to your change.

Comment 4 by joh...@chromium.org, Aug 16 2016

Cc: -joh...@chromium.org
Not related to r393041. I agree that r393042 (https://codereview.chromium.org/1923003002) looks likely.
Components: -Blink Blink>Loader
Cc: hirosh...@chromium.org yhirano@chromium.org
Is  issue 633696  related?
I'm not sure if it's related with 633696 or not but I've tried the workaround suggested on this other issue, disabling ETags on express with app.set('etag', false), and it works perfectly (so it seems to be related). But I'm pretty sure that the problem is not only with http 304 (because it was one of my first tests: I tried to return always http 200 instead 304 and it didn't fix the problem).

Comment 8 by japhet@chromium.org, Sep 21 2016

This is working for me on dev channel (55.0.2859.0) and trunk. Are others still seeing this in recent builds?

Comment 9 by japhet@chromium.org, Oct 27 2016

Status: WontFix (was: Assigned)
Having heard nothing, I'm going to mark this WontFix. I'll reopen if there are additional complaints.

Sign in to add a comment