Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
GHC
GHC
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,254
    • Issues 4,254
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 394
    • Merge Requests 394
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #15010

Closed
Open
Opened Apr 06, 2018 by ramirez7@trac-ramirez7

Application (warp) server crashing periodically with "TSO object entered"

We are seeing one of our warp servers periodically crash with the following error:

Apr 06 10:44:28 stdouterr.log: binary-name-elided: internal error: TSO object entered!
Apr 06 10:44:28 stdouterr.log:     (GHC version 8.0.2 for x86_64_unknown_linux)

We are sometimes seeing CPU/memory spikes concurrently with this error, but not always.

We are running very similar servers for other applications and they are not experiencing this error. But this server is one of our highest-load ones.

Other tickets I found with this error:

  • #12383
  • #8316

But these seem to be happening in ghci and ghc itself, not in a binary compiled by ghc.

Questions I have:

  • What exactly is this error?
  • Is there anything else we can do on our side to help debug? Any artifacts that should be produced upon crash?
  • Should we consider upgrading our GHC version from 8.0.2 to get a bugfix?
Trac metadata
Trac field Value
Version 8.0.2
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Runtime System
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ghc/ghc#15010