This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
Pastebin link to your Config (I will ignore your ticket if it doesn't contain this:http://pastebin.com/43DzPjY1
What steps will reproduce the problem?1.Wait until the ram reaches or exceeds the limit in the ram-meter section2.Note that the limit is exceeded and the ram-meter module does not start commands to purge the ram (/lagg gc and /lagg unloadchunks)3.The server ends up crashing when rams are saturated 6GB
What is the expected output? What do you see instead?Understanding why the limit is exceeded without triggering commands and especially that this function works again
What version of the product are you using?2.8.3 for CB 1.7.9-R0.2 (actually installed)But same result with:2.8.3 for 1.8.12.9.0 for CB 1.7.9-R0.22.9.0 for 1.8.1
Do you have an error log of what happened?Nothing
Please provide any additional information below.I had this problem when the 2.9.0 version installed automatically, and since I can not restore this function. Even reinstalling earlier versions of Clearlagg. Yet I deleted Clearlagg.jar and the config file without result
ram-meter running *(ram-limit = 500, used-ram = 338
ram-meter running *(ram-limit = 500, used-ram = 597
ram-meter is running commands...
ram-meter running *(ram-limit = 500, used-ram = 149
ram-meter running *(ram-limit = 500, used-ram = 225
ram-meter running *(ram-limit = 500, used-ram = 248
ram-meter running *(ram-limit = 500, used-ram = 263
ram-meter running *(ram-limit = 500, used-ram = 296
The module runs perfectly for me. If your memory limit is 6,000mb, then i highly recommend you set the ram limit to at least 200-500mb lower. Also changing the interval lower has no negative effect on performance aside from possibly running those commands twice.
To post a comment, please login or register a new account.