Bug 29594 - File: high memory consumption
Summary: File: high memory consumption
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 29586
Blocks:
  Show dependency treegraph
 
Reported: 2021-10-27 00:02 CEST by Marc Krämer
Modified: 2024-08-22 23:02 CEST (History)
0 users

See Also:
Source RPM: file-5.39-4.mga8.src.rpm
CVE:
Status comment:


Attachments

Marc Krämer 2021-10-27 00:03:00 CEST

Depends on: (none) => 29586

Comment 1 Lewis Smith 2021-10-28 20:42:38 CEST
Thanks for the report & the references.

We have 5.40 in Cauldron; "Fixed in Version 5.40" (of 'file')

However, the root of the problem is in fileinfo/libmagic (I can only see it in  php-devel), where the patch applies. The 'depends on' bug cross-referenced is essential reading; the PHP problem is fixed there (with QA).
https://bugs.mageia.org/show_bug.cgi?id=29586#c1

Different packagers commit 'file', so assigning this globally.

Assignee: bugsquad => pkg-bugs
Source RPM: file => file-5.39-4.mga8.src.rpm

Comment 2 Marc Krämer 2021-11-04 10:41:22 CET
@Lewis: that is my opinion too :)
Comment 3 Marja Van Waes 2024-08-22 23:02:58 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.