platform_frameworks_base

First you need full source code of AOSP version.

Then you can build SystemUI with mm command.

These lines are just constructors of struct ResourceId:

You could use GitHub API code search endpoint to get the paths, but then use your wget raw.githubusercontent method to download them:

Workaround only since i couldn't find the actual place to disable it but this worked. In DisplayManager on the public Display[] getDisplays(String category) method i checked. If there's two displays, then ignore whatever display is not the default display. Terrible temporary workaround but this is my solution. Accepting until someone posts a better soltuion!

The more interesting targets are defined in the Android.bp file.

There are multiple targets that gets built from that repository, so take a look at the java_library targets with names starting with "framework", and the comments on the framework target to find what you need.

From the book thegnumakebook, page 126, The Twilight Zone:

It’s possible to take definitions like $( ) and $(\n) and go much further, defining variables with names like =, # or :

I think, = is just some other variable. Here, $= implies, expanding the variable =.

And := is used for simple assignment (Evaluated only once).

As you've found, the only two attributes that .NoActionBar provides are:

That's a great question, and in fact this should be better documented so I created an issue to track that: https://github.com/square/leakcanary/issues/1773

is it really out of my control?

Yes and no. Typically this means the leak isn't caused by a bug in your code or using an API incorrectly, it's caused by a bug in either Android X or the Android SDK. That being said, it's not always out of your controls, there can be tricks / hacks to work around leaks.

might there be something i did to cause it?

The ViewLocationHolder in Android P is an unfortunate bug that happens.. when you use views. So yeah, you didn't really do anything special.

Is there anything i can do to prevent it?

Potentially but no one has come up with a clear hack to work around it yet.

leakcanry sometimes places a link to report this memory leak but i don't see any response, is it something that android normally working on? if so, how such issues normally solved and how to keep track?

Not sure what you mean here. If you mean that the link to the bug report (https://issuetracker.google.com/issues/112792715) stopped working, yes that's because Google decide to prevent access.

if indeed there is nothing i can do to solve or prevent it, is there a way i can ask leakcanary to ignore LIBRARY LEAKS?

There's no way for LeakCanary to know whether a leak is a library leak or not prior to dumping the heap and doing the analysis. It's important to notify developers that the analysis is done (even if it only found a library leak and no app leak) because otherwise they wonder what happened to the analysis.

The answer is in the description of the trace you pasted :)

Description: In Android P, ViewLocationHolder has an mRoot field that is not cleared in its clear() method. Introduced in https://github.com/aosp-mirror/platform_frameworks_base/commit/86b326012813f09d8f1de7d6d26c986a909d Bug report: https://issuetracker.google.com/issues/112792715

This is a known Android bug.