Bug 379904 - Marble Pysical Memory Setting returns 0 (zero) when setting higher than 2047 MB
Summary: Marble Pysical Memory Setting returns 0 (zero) when setting higher than 2047 MB
Status: CONFIRMED
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.12 (KDE Applications 15.08)
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-16 14:27 UTC by Martin
Modified: 2023-04-23 17:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2017-05-16 14:27:46 UTC 
Marble Pysical Memory Setting returns 0 (zero) when setting higher than 2047 MB
... in program itself and marblerc configuration file after restarting Marble with setting physical memory limit higher than 2047MB (like 2048MB).

Testet several times.

Marble Version: Version 1.12.20 (1.13 development version)
Disro: Xubuntu 16.04 LTS (fully updated)
Comment 1 Axel Schwank 2020-11-01 19:49:59 UTC 
Confirmed for Marble 2.2.20 (2.3 development version) using KDE Frameworks 5.71.0
Comment 2 Torsten Rahn 2023-04-23 17:20:30 UTC 
Ouch, yes this likely results from the fact that the setting is specified using an integer that refers to the bytes. 
I have a refactoring in the works for the FileStorageWatcher which should take this into account.