Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 779
    • Issues 779
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #1607
Closed
Open
Created Jun 28, 2019 by akwizgran@akwizgranOwner

OOM errors

Recently we've had four crash reports with OOM errors. Three of the errors had the Rome RSS library in the stacktrace; the fourth happened in UI code but the log showed that Rome had recently thrown a parsing exception. We upgraded Rome from 1.7.3 to 1.10.0 in ccbeee60 (included in Briar 1.1.3).

I suspect the problem is this bug, which was fixed in Rome 1.12.0, so upgrading may fix the issue.

Upgrading Rome didn't fix the issue. We've had 23 OOM reports with various stacktraces in versions 1.1.7 to 1.2.3 beta.

Edited Nov 04, 2019 by akwizgran
Assignee
Assign to
Time tracking