Bug 2308642

Summary: App crash due to memory leakage
Product: [Fedora] Fedora Reporter: Trung Lê <8>
Component: chromiumAssignee: Than Ngo <than>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 40CC: spotrh, suraj.ghimire7, than, yaneti
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-04 12:47:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Trung Lê 2024-08-30 07:10:52 UTC 
The program would run but would be slowly leaking memory in one of the spawned processes. One the process has reached around 5GB of RAM, the app would crash due to OOM.

Reproducible: Always

Steps to Reproduce:
1. Open the app
2. Observe the process with htop for 5 minutes
Actual Results:  
App crash

Expected Results:  
No crash

I've had a chat with Timothy Pearson (the maintainer of the PPC64LE patchset). He said there might be issue that is related to 64k pagesize partition alloc code. He added that his patch runs fine on 4k page size kernel (which Debian is using).

I think it is LIKELY related to the fact that `partition-alloc-4k-detect.patch` was commented out (see https://src.fedoraproject.org/rpms/chromium/blob/rawhide/f/chromium.spec#_1197).

I would like to propose that we should enable that patch because in theory 64k pagesize kernel can still function with 4k pagesize app.
Comment 1 Than Ngo 2024-09-10 09:50:34 UTC 
i checked the Timothy Pearson's git branch chromium-128 and saw that partition-alloc-4k-detect.patch was removed.

Does this problem also occur with the latest version of chromiuim 128.0.6613.119?
Comment 2 Than Ngo 2024-10-04 12:47:43 UTC 
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.
Comment 3 Red Hat Bugzilla 2025-02-02 04:25:03 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days