Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 679
    • Issues 679
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1607

Closed
Open
Opened Jun 28, 2019 by akwizgran@akwizgranOwner
  • Report abuse
  • New issue
Report abuse New issue

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
Android 1.2
Milestone
Android 1.2
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1607