Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8699

Closed
Open
Created Jan 30, 2015 by Administrator@rootOwner

Large snippet leads to high cpu load and ultimately timeout

Created by: DapperTayra

Hello,

I saved a 1.7 MB assembler file as a public snippet. Now whenever someone opens the snippet's URL the server hogs the CPU until gilt shows error 502. I cannot delete the large snippet anymore. Is there a way to manually delete it?

Cheers

GitLab 7.7.0 GitLab Shell 2.4.1 GitLab API v3 Ruby 2.1.4p265 Rails 4.1.1

==> /var/log/gitlab/unicorn/unicorn_stderr.log <== E, [2015-01-30T23:18:29.635465 #12011] ERROR -- : worker=1 PID:12333 timeout (61s > 60s), killing E, [2015-01-30T23:18:29.657546 #12011] ERROR -- : reaped #<Process::Status: pid 12333 SIGKILL (signal 9)> worker=1

Assignee
Assign to
Time tracking