Open GoogleCodeExporter opened 9 years ago
I'm half way in Water II and it keeps checking quest page while in Idle,
endless looping. Even though not enough energy to do quest will keep looking
there.
Original comment by blm...@gmail.com
on 18 Apr 2011 at 4:22
This issue persists in r1090
Original comment by alozovik
on 22 Apr 2011 at 4:59
1090 STILL gets stuck on Quests when running IDLE, even when quests are turned
off. Am in Water II.
Original comment by blm...@gmail.com
on 25 Apr 2011 at 8:31
Have had several instances where pc crashes due to excessive code build up
while this idle Quest check is hung up. I found if I turn the quest row to
NEVER in the IDLE worker it fixes the hang up and it runs smoothly. it is
definitely in IDLE the quest check is stuck. I can even see the page loading
Quest every second if left to anything other than never (daily/weekly/hourly
etc). This is only way i can even get my gifting done.
Original comment by blm...@gmail.com
on 26 Apr 2011 at 9:37
This still happens in r1094
Original comment by alozovik
on 5 May 2011 at 4:04
Don't know if this helps or not but managed to capture this:
[r1103] [19:53:54] Page: BAD_FUNCTION_USE in Page.to(["battle.php",null,true]):
Not allowed to use Page.to() outside .work(true)
->Page._update({"type":"reminder","self":true,"id":"retry","worker":"Page"},"run
")
->Page.update_reminder({"type":"reminder","self":true,"id":"retry","worker":"[worker Page]"},["[object Object]"])
->Page.update({"type":"reminder","self":true,"id":"retry","worker":"[worker Page]"})
->Page.retry()
->Page.to("battle.php",null,true)
chrome-extension://onfncfheocnidgnejgnlcnfiifoidemg/worker_+debug.js:231[19:54:2
0] Queue->Idle->Page: Navigating to quests.php?land=13
chrome-extension://onfncfheocnidgnejgnlcnfiifoidemg/worker_+debug.js:231[r1103]
[19:54:35] Page: Page load timeout, retry 1...
chrome-extension://onfncfheocnidgnejgnlcnfiifoidemg/worker_+debug.js:231[r1103]
[19:54:35] Page: BAD_FUNCTION_USE in Page.to(["quests.php?land=13",null,true]):
Not allowed to use Page.to() outside .work(true)
->Page._update({"type":"reminder","self":true,"id":"retry","worker":"Page"},"run
")
->Page.update_reminder({"type":"reminder","self":true,"id":"retry","worker":"[worker Page]"},["[object Object]"])
->Page.update({"type":"reminder","self":true,"id":"retry","worker":"[worker Page]"})
->Page.retry()
->Page.to("quests.php?land=13",null,true)
/fbml/fbjs_ajax_proxy.php?__a=1Failed to load resource: the server responded
with a status of 504 (Gateway Time-out)
187188_1641204847_79008_q.jpgFailed to load resource: the server responded with
a status of 504 (Gateway Time-out)
41365_1214498471_8206_q.jpgFailed to load resource: the server responded with a
status of 504 (Gateway Time-out)
161426_503200715_2184248_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
186974_1027310305_1139747_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
161195_1322383927_3791536_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
157263_1070951195_7908407_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
/ajax/presence/update.php?__a=1Failed to load resource: the server responded
with a status of 504 (Gateway Time-out)
211314_1816505533_4127180_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
48573_1334095675_9121_q.jpgFailed to load resource: the server responded with a
status of 504 (Gateway Time-out)
187068_100000872066395_946529_q.jpgFailed to load resource: the server
responded with a status of 504 (Gateway Time-out)
49915_592934843_7998360_q.jpgFailed to load resource: the server responded with
a status of 504 (Gateway Time-out)
41397_100000404670341_768_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
186112_1633299661_1225342_q.jpgFailed to load resource: the server responded
with a status of 504 (Gateway Time-out)
1.68.channel.facebook.com/pFailed to load resource: the server responded with a
status of 504 (Gateway Time-out)
1.68.channel.facebook.com/pFailed to load resource: the server responded with a
status of 504 (Gateway Time-out)
/ajax/presence/reconnect.php?__a=1&reason=112&iframe_loaded=true&post_form_id=9a
762a7fda060b2d49848bf17049b908Failed to load resource: the server responded
with a status of 504 (Gateway Time-out)
/ajax/apps/usage_update.php?__a=1Failed to load resource: the server responded
with a status of 504 (Gateway Time-out)
/ajax/presence/reconnect.php?__a=1&reason=112&iframe_loaded=true&post_form_id=9a
762a7fda060b2d49848bf17049b908Failed to load resource: the server responded
with a status of 504 (Gateway Time-out)
Original comment by karbonst...@gmail.com
on 9 May 2011 at 3:45
That BAD_FUNCTION_USE issue is a known one, to do with the way Golem retries
timed out pages. I'm not sure if making that go away will help the situation,
but I think improvements to the page parsing and a different way to handle page
timeouts and retries in combination should sort out the Quest cycling issue.
I think all of those 504 errors are just something going wrong with either some
blocking software you are running, or Facebook or CA scripts getting themselves
into trouble with scripts running across domains. None of those files appear to
be directly related to Golem or the parts of CA that Golem deals with.
Original comment by lur...@hotmail.com
on 9 May 2011 at 6:51
Original issue reported on code.google.com by
alozovik
on 15 Apr 2011 at 7:21