search

mohan-nishit / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 0 forks source link

Aggregate v 1.0 beta rev. 2 Browser stuck in refresh #245

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi folks,

I installed Aggregate 1.0 and the installation worked well (using the
template) but when i run in my appspot the pages not works as well,
looks like always in refresh and i can't use.

Someone had this problem?

thanks a lot

--
Renan A. Kamimura

Original issue reported on code.google.com by mitchellsundt@gmail.com on 29 Jun 2011 at 5:51

GoogleCodeExporter commented 9 years ago 
I've confirmed that the Timer scheduling interval is just that -- a scheduling 
interval.  If the computer is bogged down or the browser does a garbage 
collection in javascript, the timer queue can get backlogged with timer 
callbacks that are in the past.  On a sufficiently slow computer, this can 
leave you perpetually refreshing.

This could also happen if the update action takes an excessive amount of time 
(e.g., long timeout on a synchronous call to the server -- but we shouldn't be 
doing that anywhere except perhaps on establishing the first socket 
connections???).

Original comment by mitchellsundt@gmail.com on 29 Jun 2011 at 6:00

GoogleCodeExporter commented 9 years ago 
And -- it could also occur if other browser tabs have a lot of update 
activities running in the background (animations, background IRC fetches, etc.) 
or if they are allocating and releasing a lot of javascript objects (triggering 
a lot of garbage collection sweeps).

Original comment by mitchellsundt@gmail.com on 29 Jun 2011 at 6:27

GoogleCodeExporter commented 9 years ago 
Found a number of issues with the beta 2 that also caused many unnecessary 
interactions with the server.  The biggest of these was the duplicated creation 
of the top-level frame, which could cause two timer instances to run.  Changes 
are in 
http://code.google.com/p/opendatakit/source/detail?r=9a869c0a7d893586a6c80cc9dae
82731e0936ef2&name=uiexperiment&repo=aggregate

Original comment by mitchellsundt@gmail.com on 30 Jun 2011 at 10:35

GoogleCodeExporter commented 9 years ago 
requested Renan give the issue 212 verification build a try to see if the 
problems are resolved.

Original comment by mitchellsundt@gmail.com on 1 Jul 2011 at 8:52

GoogleCodeExporter commented 9 years ago 
I can reproduce this behavior by installing an Aggregate 1.0 beta 2 build on 
top of an existing Aggregate 1.0 alpha or beta 1 appengine instance.  The 
screen keeps flashing.

The log on Appspot shows that there is a schema change on one of the 
fundamental tables within Aggregate.

Original comment by mitchellsundt@gmail.com on 16 Jul 2011 at 2:54