Hi,
Yes, the server.com part was a dummy url - the actual url is a protected
server.
As it turns out this is a Chrome issue. It has problems when multiple HTTP
streams are opened that remain open for a long time. In my case, the server
was constantly pushing new jpeg data over the open http socket (its
basically a security camera monitor that keeps pushing new frames to the
same url)

Chrome gets stuck when I open multiple such connections.

I posted my analysis here
http://stackoverflow.com/questions/29996051/using-img-ngsrc-in-android-for-large-dynamic-images-is-causing-future-http-reque




On Sun, May 3, 2015 at 9:10 PM, Xu, Xing <[email protected]> wrote:

>  Hi,  I am trying to reproduce your issue. But server.com seems is not a
> valid online site.
>
> Could you please help to provide a detail online link or an offline html
> page for us to reproduce it?
>
> You can also file a bug at  https://crosswalk-project.org/jira .
>
>
>
>
>
> *From:* Crosswalk-help [mailto:
> [email protected]] *On Behalf Of *Arjun
> Roychowdhury
> *Sent:* Saturday, May 2, 2015 10:59 PM
> *To:* [email protected]
> *Subject:* [Crosswalk-help] Problem with pending HTTP Gets using Crosswalk
>
>
>
>
>
>
>
> I am developing an Angular JS application using ionic. For android, I am
> using crosswalk for better performance.
>
> I've noticed that when running on Android, I am facing problems with http
> requests getting stuck when trying to load large images - if any request
> gets "stuck" -- i.e. no error, but in my chrome developer inspector, I see
> the http request as "pending" -- then all subsequent requests go into
> "pending" state too. This problem does not exist in iOS
>
> The code is pretty simple:
>
>  <span ng-repeat="monitor in monitors">
>
>       <img ng-src="http://server.com/monitorId=monitor?view=jpg"; />
>
> </span>
>
>  This results in around 6 GETs of images of size 600x400 and the images
> keep changing (the server keeps changing the image)
>
> What I've observed specifically with Android is after a few successful
> tries , the network HTTP GET behind this img ng-src gets stuck in pending
> like I said above and then all subsequent HTTP requests also get into
> pending and none of them ever get out of that state.
>
> I am guessing there is some sort of limit for network queue that is
> getting filled up.
>
> So how do I solve this issue?
>
> a) One way I could think of is to put a timeout -- To work around this I
> wrote a global http interceptor via directives and forced a timeout after
> 10 seconds. While this works for all requests, those that are in "pending"
> state don't get affected, so this solution was a fail
>
> b) I tried switching crosswalk browsers and no cigar -- 13.41.318.0, 
> 12.41.296.5
> etc.
>
> c) I tried adding random timestamps thinking its a caching issues, again
> made no difference
>
> Any thoughts?
>
> thanks
>
>
>
>
>



-- 
Arjun Roychowdhury
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help

Reply via email to