The thing is you, the user, has to properly describe and identify the problem in the first place before you know where to properly address an information he thinks to be of value to.
The 3.2 release thread and even more so GitHub aren’t for problems as long as it is unclear what your problem really is about in terms of code, i.e. which component misbehaves.
The common understanding problem on this starts very early in the communication process:
Most what users consider to be a problem does not match those criteria.
I understand this can be frustrating to users because they are looking for help they do not get or to someone like you that wants to help but does not know where to turn to.
Then again, only when you identify a problem (in terms of code, not from the user’s point of view) and what component it is with, you will know where to address it, and you will also get the appropriate attention. The crux is about identifying problems without knowing enough of the inner workings of openHAB and that there’s noone to guide you through that.
Here for instance, when Java is spitting out of mem errors, this is NOT an OH problem because Java wants to use more mem than it is configured to use at most.
There might be a mem leak in OH as the underlying problem but as long as you have not properly identified that leak exists, it is not a problem in terms of code.
So for now you shouldn’t be asking for help on either of these channels because that might be annoying and hindering the volunteers over there.
Most of the time Java-out-of-mem is a user-caused problem because the limit depends on hardware, JVM, OS configuration, which are any user’s own responsibility to get right
openHABian defines a standard limit, too (right, you can set in EXTRA_JAVA_OPTS as mentioned above) and it’s not impossible that this default does not work for everybody.
But given the number and size of working installation with openHABian it is highly unlikely that you are the first user this is insufficient for.
So return to analysis and look for a mem leak instead.
Please pay attention to being helpful in the first place. You may not expect anyone to read your post to know the context of your system so comprehensively state it in the first place and keep repeating to state that whenever the information might be useful to an unknown or new-to-the party person that might want to help you.
Remember #1 from the post below: this is not a help desk, and there’s no ticket system.
There’s only this thread, and you should not spread information. Update post #1 of a thread when there’s relevant news.
Noone wants to waste his time digging through older posts just to get the current context right.
How to ask a good question / Help Us Help You - Tutorials & Examples - openHAB Community