Seriously, 24 Thousand lines of errors (chromium.log) when loading a level

Support Previous Build Reports
1

Not sure where this should go, but I thought it worth mentioning.
Build 2310 x 64bit

Freshly deleted chromium.log to start from scratch each time.

A 10 day game loaded with 23,899 lines with most of it being low level call and poll errors.
A 10 day game save that crashed the game generated 24,900 lines with most of it being low level call and poll errors.
A NEW game with only the planted flag generated 8,400 lines with most of it being the same low level call and poll errors.

Example:
[0312/105453:INFO:CONSOLE(19)] “low level call /r/call?fn=radiant:get_events&long_poll=1 failed.”, source: http://radiant/radiant/js/radiant/core.js (19)
[0312/105453:INFO:CONSOLE(152)] “poll error: (status:undefined error:undefined)”, source: http://radiant/radiant/js/radiant/object.js (152)

This is simply loading (or attempting to load) a game file, then quitting.

Don’t know if these constant errors are trouble, but seems it would put a huge load on the game’s stability.

4 Likes
2

wow… :confounded:

so, would this be a good supplement to the “10 day load game” report (that I am sure I just saw a while back)?

1 Like
3

Not sure. I suspect this has been going on for some time, but who knows. Last time I cleared that log out it was like 175meg!

10 days (actually about 9 for me) seems to be all I can get out of the game at this point, AMD or Intel.

Just wanted to give this some visibility to the devs. Stow as you deem fit…

3 Likes
4

@NonBritGit I have the same problem but assuming you mean 9 days without problems. I can extend the game time with errors just stacking up until I reach day 12 or so at that point it becomes unplayable…
I honestly don’t think i want to know the size of my log file tho.

5

chromium.log fills up with the most useless stuff. It outputs a message whenever it displays a tip:

[0308/111832:INFO:CONSOLE(20)] “showing tip: Click on a wall to build ladders”, source: http://radiant/stonehearth/ui/game/tip_popup/tip_popup.js (20)

It outputs a message whenever Radiant uses bad or outdated habits, as seen here:

[0308/110659:INFO:CONSOLE(15373)] “DEPRECATION: You specified a quoteless path to the {{action}} helper ‘dismiss’ which did not resolve to an actionName. Perhaps you meant to use a quoted actionName? (e.g. {{action ‘dismiss’}}).
at Object.handleRegisteredAction [as handler] (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:20155:21)
at HTMLAnchorElement. (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:38724:27)
at HTMLBodyElement.jQuery.event.dispatch (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.js:5095:9)
at HTMLBodyElement.elemData.handle (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.js:4766:46)”, source: http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js (15373)

and here:

[0308/110726:INFO:CONSOLE(15373)] “DEPRECATION: Usage of state is deprecated, use _state instead.
at deprecate (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:13953:15)
at defineProperty.get (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:13961:31)
at App.View.Ember.View.extend.invokeDestroy (http://radiant/stonehearth/ui/root/js/stonehearth/view.js:66:15)
at http://radiant/stonehearth/ui/game/promotion_tree/promotion_tree.js:359:24”, source: http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js (15373)
[0308/110801:INFO:CONSOLE(15373)] “DEPRECATION: Usage of state is deprecated, use _state instead.
at deprecate (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:13953:15)
at defineProperty.get (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js:13961:31)
at App.View.Ember.View.extend.invokeDestroy (http://radiant/stonehearth/ui/root/js/stonehearth/view.js:66:15)
at http://radiant/stonehearth/ui/game/promotion_tree/promotion_tree.js:359:24”, source: http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.js (15373)

Now, I suppose logging is okay, but the problem is that the file never resets. It just grows and grows, to the point where it would never be useful if I did encounter an error and I wanted to know what went wrong. Mine was 4.3MB, about 10 times the size of my 397KB stonehearth.log.

Also, I’m worried that continuously logging may affect performance a bit, but I may just be paranoid.

1 Like
6

This is what I wondered. Mine was 175 meg at one point!