Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
engine
engine
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pulse Physiology Suite
  • engineengine
  • Issues
  • #28

Closed
Open
Created Dec 11, 2020 by marinier@marinierDeveloper

JVM crash when advancing time

I have a scenario with a massive hemorrhage (intended to mimic a leg amputation) that typically runs for ~2.5 mins before negative volume occurs (this is with pulse 3.1.0 using severity for the hemorrhages).

Specifically, starting at time 0:

  • Hemorrhage, external, LeftLeg, Severity=0.2
  • Hemorrhage, external, VenaCava, Severity=0.2
  • Hemorrhage, external, RightLeg, Severity=0.01

I've run this many times without anything special happening, but today I got a JVM crash: hs_err_pid17052.log

Not a critical issue for me as apparently it doesn't happen very often.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None