-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
On project creation memory usage reported incorrectly #5665
Copy link
Copy link
Closed
Labels
Good First IssueIndicates issues suitable for newcomers to design or coding, providing a gentle introduction.Indicates issues suitable for newcomers to design or coding, providing a gentle introduction.Type: BugIssues related to software defects or unexpected behavior, which require resolution.Issues related to software defects or unexpected behavior, which require resolution.
Milestone
Metadata
Metadata
Assignees
Labels
Good First IssueIndicates issues suitable for newcomers to design or coding, providing a gentle introduction.Indicates issues suitable for newcomers to design or coding, providing a gentle introduction.Type: BugIssues related to software defects or unexpected behavior, which require resolution.Issues related to software defects or unexpected behavior, which require resolution.
To Reproduce
Steps to reproduce the behavior:
Current Results
Memory usage is shown as consuming millions of percent of the available memory
Expected Behavior
A relative accurate (or at least possible!) indication of memory usage is expected
Screenshots
Screenshot from a recent forum posting

Source: https://forum.openrefine.org/t/large-csv-loading/478
Additional context
I think this commit is the problem 6a70463
I suspect the order of calculation for the memory means that only the Runtime.getRuntime().freeMemory() is divided by 1048576 to get the value in MB, leaving the Runtime.getRuntime().totalMemory() in bytes - which then leaves the percentage calculation as wildly inaccurate