unpushed

firewalld-0.8.5-1.fc33

FEDORA-2021-79c3efde9e created by erig0 4 years ago for Fedora 33

rebase package to v0.8.5

This update has been submitted for testing by erig0.

4 years ago

This update's test gating status has been changed to 'ignored'.

4 years ago

This update's test gating status has been changed to 'waiting'.

4 years ago

This update's test gating status has been changed to 'ignored'.

4 years ago
User Icon g6avk commented & provided feedback 4 years ago
karma

Works for me..

This update has been pushed to testing.

4 years ago

After upgrading to v0.8.5, firewalld process started to use around 110MB memory. v0.8.4 was using around 40MB. Is this expected? I am using public zone if it makes any difference.

User Icon bojan commented & provided feedback 4 years ago
karma

Works.

This update can be pushed to stable now if the maintainer wishes

4 years ago

@ersen, it's not expected. The changes between v0.8.4 and v0.8.5 1 are very minimal. The only functional change is to address non-printable characters in rich rules 2. It now generates a table/dictionary entry for every non printable unicode character, but I don't think that would cause a 70MB increase in memory usage.

Are you sure you have made changes to your configuration? ipsets for example can cause a significant increase in memory usage.

User Icon cserpentis commented & provided feedback 4 years ago
karma

works for me

This update has been submitted for stable by bodhi.

4 years ago

@erig0 it is standard firewalld installation, no config changes made by me. Memory usage goes up/down after post transaction scriptlets are run when upgrading/downgrading. I am trying to figure out what is causing that but couldn't find anything yet.

I just downgraded firewalld to test and see the same as @ersen To be honest though I would never of noticed this. It is a standard config here, the only change is a rule for kdeconnect.

Revoking this upgrade until I can verify what @erson is reporting.

erig0 edited this update.

4 years ago

Firewall is working but memory usage is rising from 40MB to around 110MB as well.

Confirmed. I'm dropping this update until it can be fixed upstream. Thanks everyone!

This update has been unpushed.

Firewall is workind but I agree with @ersen about ram.

Same here. From 40MB to 110MB after update.


Please log in to add feedback.

Metadata
Type
bugfix
Karma
3
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Thresholds
Minimum Karma
+2
Minimum Testing
14 days
Dates
submitted
4 years ago
in testing
4 years ago
modified
4 years ago

Automated Test Results