[MAGNOLIA-6984] memory limit message can sometimes be misleading Created: 20/Mar/17 Updated: 29/Aug/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 5.5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Description |
|
Sometimes, the memory limit message is shown, from SystemMonitor, although the JVM has enough free heap memory. This is, because Runtime.getRuntime().freeMemory() can't guarantee to return the right value. (Before the Java GC runs, there may be not enough "freeMemory") See http://stackoverflow.com/questions/3571203/what-are-runtime-getruntime-totalmemory-and-freememory |