A SQLiteConnection object was leaked

Despite the problem of Account already exists, what bothers me is the A SQLiteConnection object was leaked, is it possible to fix it?

Log:

[ 07-10 20:23:25.697  3295: 9568 D/GmsAuthLoginBrowser ]
JSBridge: getAndroidId 3877171728247230356

[ 07-10 20:23:26.182  3295: 9568 D/GmsAuthLoginBrowser ]
JSBridge: getAndroidId 3877171728247230356

[ 07-10 20:23:26.221  3295: 3295 D/GmsAuthLoginBrowser ]
pageFinished: https://accounts.google.com/EmbeddedSetup/signinconsent?source=android&xoauth_display_name=Android%20Device&lang=it&cc=it&langCountry=it_it&hl=it-IT&tmpl=new_account&flowName=EmbeddedSetupAndroid&TL=*****************&cid=1#close

[ 07-10 20:23:26.290  3295: 9582 D/GmsHttpFormClient ]
-- Request --
add_account=1&androidId=***************&app=com.google.android.gms&client_sig=********************************&callerPkg=com.google.android.gms&callerSig=*****************************&device_country=it&get_accountid=1&google_play_services_version=17785000&ACCESS_TOKEN=1&lang=it_IT&operatorCountry=it&sdk_version=25&service=ac2dm&Token=oauth2_4%2F****************************

[ 07-10 20:23:26.494  3295: 3306 W/SQLiteConnectionPool ]
A SQLiteConnection object for database '/data/user/0/com.google.android.gms/databases/gcmstatus' was leaked!  Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.

[ 07-10 20:23:26.755  3295: 3306 W/SQLiteConnectionPool ]
A SQLiteConnection object for database '/data/user/0/com.google.android.gms/databases/gcmstatus' was leaked!  Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.

[ 07-10 20:23:26.851  3295: 9582 D/GmsHttpFormClient ]
-- Response --
***************************

[ 07-10 20:23:26.888  2367: 7624 W/AccountManagerService ]
insertAccountIntoDatabase: Account {name=*******************@gmail.com, type=com.google}, skipping since the account already exists

[ 07-10 20:23:26.889  3295: 9582 W/GmsAuthLoginBrowser ]
Account NOT created!

Start by reproducing the account-add flow shown in the log and trace the code that accesses the gcmstatus SQLite database. Identify which connection or transaction remains open during the flow. Done means the leak warnings no longer appear and the account-add behavior can be verified without introducing regressions.