LruCache | A tiny memory cache implementation which uses a LRU policy | Caching library

You should consider decoupling your UI from location logic. You might wrap the location listener with LiveData to use all benefits of lifecycle callbacks instead of handling it manually.
Here is a sample project that demonstrates this technic: https://github.com/Vicrisbeka/LocationMVVM

You need to make standardBottomSheetBehavior nullable then in FragmentTripPlanner.onDestroyView(), you need to clear the reference to standardBottomSheetBehavior since it has a reference to standardBottomSheet

This is a known issue in LeakCanary 2.6, which has been fixed in LeakCanary 2.7

https://square.github.io/leakcanary/changelog/#finer-grained-root-view-watching

In version 2.6, LeakCanary added detection of root views retained after View.onDetachedFromWindow(). This helps find more leaks, but unfortunately some Android widgets keep a detached root view around to reattach it later (e.g. spinner). App developers also sometimes do the same with dialogs, keeping a single instance around and calling show() and hide() as needed. As a result, LeakCanary would report leaks that were actually not leaks.

In version 2.7, the default behavior changed: LeakCanary will continue to detect leaks of toasts, but will ignore root views created by a PopupWindow (which is what Android widgets use). It will also ignore root views created by a dialog by default, and you can turn this back on by setting the leak_canary_watcher_watch_dismissed_dialogs resource boolean to true:

So, after a long search I eventually found the problem. The documentation is not really clear on this but:

As I have posted this question couple of days ago but I was unable to get an answer so I decided to try a few methods of my own to see if I can resolve the problem. In my case solution, I am posting solved the above issue and I am able to connect to localhost:8080 from my browser window. I have to confess I found this solution by flook I still don't know the logic behind what made it work but it is working.

root@Home:/usr/local/tomcat10# ./bin/startup.sh

Output:

Using CATALINA_BASE: /usr/local/tomcat10 Using CATALINA_HOME: /usr/local/tomcat10 Using CATALINA_TMPDIR: /usr/local/tomcat10/temp> Using JRE_HOME: /usr/lib/jvm/java-11-oracle Using CLASSPATH: /usr/local/tomcat10/bin/bootstrap.jar:/usr/local/tomcat10/bin/tomcat->juli.jar Using CATALINA_OPTS: Tomcat started.

at this stage, I know tomcat is installed successfully and services are all up and running therefore there maybe is something wrong with the browser which may be causing a connectivity issue.

So I took the following steps:

Step No:1

I have click on three dots on the top right-hand side of the Chrome browser window (setting) then I click on more tools then click on clear browsing data.

From the Clear browsing, data window clicked the advance tab and select all times from the drop-down list

Tick all options except Password and other sign-in data and Autofill option

After your selection click the Clear data button

Open new browser window and type localhost:8080

Got unable to connect to the server message

Step NO:2

Now open the My account setting page and from here browse to My activity and clear all previously recorded activities log and turn off all active activity recording sliding switches

Web & App Activity Location History YouTube History Ad personalisation

Open the web browser and typed localhost:8080 (Enter) still got the same error message

Step NO:3 Go to add the Ad settings, I turned the Ad personalisation setting OFF in past because I didn't want Google to collect my browsing data In your case it might still be ON so I turned it back on for my browser.

now type localhost:8080 surprisingly tomcat10 index page open in my browser window To test if it was Ad setting which was stoping tomcat10 index page to load in browser window I turned Ad personalisation tab OFF again and type localhost:8080 and press Enter Even the Ad personalisation tab is OFF but this time tomcat10 index page is loaded to the browser window again.

Therefore I am not 100% sure if it was Ad personalisation state which was not allowing the tomcat10 index page to load in the browser window or one of the other previous options which I turned off

To test further I have close all my browsers and then type localhost:8080 in a new browser window and the index page still loading successfully.

This solution is working for me hope it will help other readers too

If someone else is wondering too, as it was said in a comments section, I should have removed listeners right in the OnDetachedFromWindow() method(before the super call of it!!). Also I've cleared onClickListeners in necessary fragments and called this method for my custom view in OnDestroyView(), so now it looks like:

I have fixed the memory leak.

Not using androidx.fragment.app.FragmentContainerView in my XML was the solution.

Instead, I have used a ConstraintLayout.

I think you should not use it if you do not control your fragment using app:navGraph="@navigation/nav_graph" in XML and instead use replace(R.id.fragment_container, null, null) in your activity

The leaktrace indicates that MainActivity was destroyed but is held in memory by MapView which has the activity as its context.

Now, what's really weird here is that the MapView is the parent of a FrameLayout that has the Application as its context, which itself is the parent of a view called 'ac' (obfuscated name) which is held by a field of the "RenderDrive" thread instance.

This definitely is a bug in the Google Maps library. You should report the issue on their bug tracker, feel free to also use this answer that I just posted.

I don't know what bug exactly is causing this leak, but you could fix it by removing all children of MapView when the activity is destroyed.

The underlying code used in Indy SDK is outdated in rust lang 1.48.0+. Downgrade the rust lang version to 1.47.0 and build the indy SDK from the source will solve the issue in reference.