ERROR:node_controller.cc(585)] Trying to re-add dropped peer

[travishardiman]

Well nuts, I thought I was good but it’s black screen again:

0|MagicMir | 
0|MagicMir | <--- Last few GCs --->
0|MagicMir | 
0|MagicMir | [1:0x2dd94000] 359113688 ms: Scavenge 882.9 (978.3) -> 879.5 (978.5) MB, 4.7 / 0.0 ms  (average mu = 0.974, current mu = 0.583) task 
0|MagicMir | [1:0x2dd94000] 359113908 ms: Scavenge 883.0 (978.5) -> 879.7 (978.8) MB, 5.4 / 0.0 ms  (average mu = 0.974, current mu = 0.583) allocation failure 
0|MagicMir | [1:0x2dd94000] 359114166 ms: Scavenge 883.4 (978.8) -> 880.0 (986.8) MB, 16.4 / 0.1 ms  (average mu = 0.974, current mu = 0.583) allocation failure 
0|MagicMir | 
0|MagicMir | 
0|MagicMir | <--- JS stacktrace --->
0|MagicMir |

[sdetweil]

@travishardiman looks like there may be a module eating storage

what do you have installed beyond the base?

[travishardiman]

@sdetweil MMM-GoogleMapsTraffic, MMM-MyGarbage, and MMM-GooglePhotos

[sdetweil]

@travishardiman hm…not seen problems related to those, but time to run disabling one at a time

add

disabled:true,

after the

  module:

line
and restart mm

[travishardiman]

@sdetweil ok, I’m starting with the google photos module and see how it goes. Are there any other logs that might be helpful for debugging?

[sdetweil]

@travishardiman the console which you know and the browser console

ctrl-shift-i, select the console tab and scroll up
red text is typically errors

[travishardiman]

@sdetweil long term update after trying a few things out, the MMM-GoogleMapsTraffic module was the culprit. I started going down the path of trying to update the javascript issues when I discovered that your fork fixed them already. I uninstalled the original and installed yours and I haven’t had the black screen once since.

https://github.com/sdetweil/MMM-GoogleMapsTraffic

Thanks!

[sdetweil]

@travishardiman cool