Age | Commit message (Collapse) | Author |
|
|
|
Caused a crash in 19, see ERL-171.
Data was never reset so the number of schedulers didn't match the
previous collected data.
|
|
Could crash if interval was updated before node was set.
|
|
Bug introduced in bde2d01506a63, does work on linux but not on
the other OS's.
|
|
|
|
|
|
By allowing changes to the number of minutes displayed and update
frequency, we need to optimize the drawing of the graphs as it can
no longer recalculate everything in each frame drawn.
Only recalculate the changed entries, takes more memory but far less
cpu usage.
While updating the gui, increase the frame-rate a bit so it updates
smoother and decrease pen size for graphs to 1 pixel as it looks better
according to an office voting.
|
|
|
|
|
|
Easier to the see memory usage and utilization as charts instead of
values that is updating during runtime.
Remove from system page and create a separate allocator tab.
|
|
Fix app viewer crash
|
|
wxWidgets-2.9 seg faults if you try to create a graphics context
before the window is shown.
With bad timing this can happen.
So change the haveGC test to check if the functionality is available
without creating the GraphicsContext.
|
|
On wxWidgets 2.9 they seem to have fixed font sizes in GC's
|
|
|
|
It is confusing we have total and system is total - processes
|
|
DC's and GC's is not double buffered by default on windows,
and there is a separate erase event which causes awful flickering
when constant updating a window.
Hack around wx (to be able to use wxBufferPaintDC),
to avoid flickering on windows.
This works on windows because there (and only there)
wxGC:create/1 also takes a memoryDC as argument.
|
|
Sigh, seems that Suse-11 does not default deliver wxWidgets with wxGRAPHICS_CONTEXT enabled,
add fallback to use wxDC again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|