Project

Profile

Help

Issue #9406

closed

Trivial OOM on sync for a particular Microsoft repo

Added by dalley over 2 years ago. Updated over 2 years ago.

Status:
CLOSED - NOTABUG
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 111
Quarter:

Description

Syncing https://packages.microsoft.com/rhel/8/prod/ results in an OOM even on a box with ~10gb of available memory


Related issues

Related to RPM Support - Issue #9399: sync error: invalid memory alloc request sizeCLOSED - NOTABUGdalleyActions
Actions #1

Updated by dalley over 2 years ago

  • Subject changed from Triviai OOM on sync to Trivial OOM on sync
Actions #2

Updated by dalley over 2 years ago

  • Related to Issue #9399: sync error: invalid memory alloc request size added
Actions #3

Updated by dalley over 2 years ago

  • Subject changed from Trivial OOM on sync to Trivial OOM on sync for a particular Microsoft repo
Actions #4

Updated by dalley over 2 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 105
Actions #5

Updated by dalley over 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dalley

In a non-Pulp reproducer that merely calls parses the metadata with createrepo_c using the same code as Pulp RPM, it's clear that for some reason in this case there is a pathological behavior with the custom hybrid iterative parser.

The traditional "all at once" parsing peaks at 900mb, the new iterative parser peaks around 600mb, but our custom parser blows through the 15.5gb available on my VM and triggers the OOM killer.

Actions #6

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 105 to Sprint 106
Actions #7

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 106 to Sprint 107
Actions #8

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 107 to Sprint 108
Actions #9

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 108 to Sprint 109
Actions #10

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 109 to Sprint 110
Actions #11

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 110 to Sprint 111
Actions #12

Updated by dalley over 2 years ago

Yeah this is not our fault. I reported it upstream to Microsoft.

https://github.com/dotnet/core/issues/6706#issuecomment-986330681

Actions #13

Updated by dalley over 2 years ago

  • Status changed from ASSIGNED to CLOSED - NOTABUG

Also available in: Atom PDF