Summary: | Marble Pysical Memory Setting returns 0 (zero) when setting higher than 2047 MB | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | Martin <endor81> |
Component: | general | Assignee: | marble-bugs |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | axel, rahn |
Priority: | NOR | ||
Version: | 1.12 (KDE Applications 15.08) | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Martin
2017-05-16 14:27:46 UTC
Confirmed for Marble 2.2.20 (2.3 development version) using KDE Frameworks 5.71.0 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. |