What steps will reproduce the problem?
1. Use stock OLV 1.2, choose "tail log with type detection". Choose log4j log
that is continuesly growing.
2. Wait until it reaches heap limit.
3. When it reaches memory threshold, application crashes with
"java.lang.OutOfMemoryError: Java heap ...". Sometimes even error boxes are not
drawed. (so cannot include exact error currently), application is unusable from
this point. Nothing at screen gets repainted, nothing reacts to clicks.
What is the expected output? What do you see instead?
a) Expected output usual application behavior tailing logs. (preffered)
b) Grid with log lines cleared to free up memory. Notification is shown
somewhere (which would NOT require to click ok to proceed) about error cause.
This needed when log watching is left for overnight. It should not crash.
What version of the product are you using? On what operating system?
OLV 1.2,
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
Windows 7x64 (Microsoft Windows [Version 6.1.7601])
Please provide any additional information below.
Problem could be repeated on Windows Server 20xx OS.
Desired fix is to be able to select option in settings: default size of
"current log window".
That is number of lines that are actually created in grid and occupies memory.
That is if window is 1000 lines, then when it comes 1002 line, first two lines
(1,2) are deleted from "current window" and freed from memory. if i use scroll
bar to go to the begining of the file, then "current window" is lines 1-1000,
if i go to the last lines, than "current window" becomes 3-1002 lines.
Original issue reported on code.google.com by jaun...@gmail.com on 5 Nov 2014 at 7:30
Original issue reported on code.google.com by
jaun...@gmail.comon 5 Nov 2014 at 7:30