Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Surfer memory leak?

Scheduled Pinned Locked Moved Solved Surfer
4 Posts 3 Posters 67 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by
    #1

    08b12719-467a-4122-ac0b-1728e69f568c-image.png

    The graphs seem to indicate something eating more resources over time.

    It's not a busy site, and simply static pages.

    Life of sky tech

    1 Reply Last reply
    0
  • robiR robi marked this topic as a question on
  • girishG girish moved this topic from Support on
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #2

    Most of the VMs like node.js won't garbage collect unless it reached a certain threshold/age and based on heap size. These are tunable using some command line options but 0.25GB is not very significant.

    1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by nebulon
    #3

    Mostly in this case, nodejs will go up to the memory limit and only then trigger the garbage collection. This was one initial reason to add those memory limits as well, to make ruby/nodejs/... not go overboard.

    So I don't think there is anything to solve here to be honest.

    1 Reply Last reply
    2
  • girishG girish has marked this topic as solved on
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by
    #4

    Okay, it's a bit odd since that's the first time I've seen Surfer app crash due to this memory condition, presumably because the GC failed or was started too late with too little overhead available to complete.

    Have tens of other Surfer apps that do not exhibit this behavior.

    Life of sky tech

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.