StackOverflowError in WorkManager on KitKat [129091233]

Fixed

Bug

Status Update

No update yet.

Description

ka...@gmail.com

created issue #1

Mar 22, 2019 02:16PM

Component used: android.arch.work:work-runtime
Version used: 1.0.0-rc01
Devices/Android versions reproduced on: We've seen it on 4.4.4 and 4.4.2

We haven't been able to reproduce this ourselves, but we're seeing it show up in our tracking. There's a StackOverflowError caused somewhere inside WorkManager. Here's the stack trace we get:

Fatal Exception: java.lang.StackOverflowError
at java.util.HashMap.secondaryHash(HashMap.java:350)
at java.util.LinkedHashMap.get(LinkedHashMap.java:251)
at android.util.LruCache.get(LruCache.java:118)
at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:1100)
at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:689)
at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
at android.database.sqlite.SQLiteProgram.(SQLiteProgram.java:58)
at android.database.sqlite.SQLiteQuery.(SQLiteQuery.java:37)
at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1433)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1408)
at android.arch.persistence.db.framework.FrameworkSQLiteDatabase.query(myapp:161)
at android.arch.persistence.room.RoomDatabase.query(myapp:233)
at androidx.work.impl.model.DependencyDao_Impl.getDependentWorkIds(myapp:117)
at androidx.work.impl.WorkerWrapper.recursivelyFailWorkAndDependents(myapp:503)
<snip ~50 recursive frames>
at androidx.work.impl.WorkerWrapper.recursivelyFailWorkAndDependents(myapp:503)
at androidx.work.impl.WorkerWrapper.setFailedAndResolve(myapp:488)
at androidx.work.impl.WorkerWrapper.runWorker(myapp:242)
at androidx.work.impl.WorkerWrapper.run(myapp:127)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

#0. Crashed: WorkManager-WorkManagerTaskExecutor-thread-0
at java.util.HashMap.secondaryHash(HashMap.java:350)
at java.util.LinkedHashMap.get(LinkedHashMap.java:251)
at android.util.LruCache.get(LruCache.java:118)
at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:1100)
at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:689)
at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
at android.database.sqlite.SQLiteProgram.(SQLiteProgram.java:58)
at android.database.sqlite.SQLiteQuery.(SQLiteQuery.java:37)
at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1433)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1408)
at android.arch.persistence.db.framework.FrameworkSQLiteDatabase.query(myapp:161)
at android.arch.persistence.room.RoomDatabase.query(myapp:233)

Comments

su...@google.com <su...@google.com> #2Mar 22, 2019 06:32PM

Hi. We are also experiencing the same behavior since several days ago.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.

If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.

Please advice.

ka...@gmail.com <ka...@gmail.com> #3Mar 22, 2019 07:31PM

Hello,

As the example shown in the video is testing the connection multiple times in a row, has it happened by testing the connection once (or until it succeeds), then running the code and queries needed and after a while trying to connect again? Is it still failing?

Regards.

su...@google.com <su...@google.com> #4Mar 22, 2019 08:25PM

hi. it is happening randomly. the user uses the same credentials and same scenario each time.
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.

Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?

ka...@gmail.com <ka...@gmail.com> #5Mar 22, 2019 08:40PM

I have the same problem, since in this last month my script is executed by many users.

It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.

I tell my users to try to run the code over and over again, until they finally connect.

[Deleted User] <[Deleted User]> #6Mar 24, 2019 01:23PM

Hello,

Thank you for your comments, this has been forwarded internally.

Regards.

su...@google.com <su...@google.com> #7Mar 28, 2019 08:09PM

Marked as fixed, reassigned to su...@google.com.

Hi Team,

I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.

We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8

Please fix this issue ASAP

ka...@gmail.com <ka...@gmail.com> #8Mar 28, 2019 08:38PM

Hi team,

Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.

After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).

I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.

Thanks

su...@google.com <su...@google.com> #9Mar 28, 2019 09:11PM

Hello,

In order to move this investigation forward our product engineering team may need sensitive data, therefore Issue Tracker is not the best environment (public) to do so.

This is why I strongly encourage you to reach out to your admin to open a ticket to Google Workspace Support. You can also mention this issue tracker link so they are aware.

If you have any additional questions, please feel free to reach out.

Kind regards.

ka...@gmail.com <ka...@gmail.com> #10Mar 29, 2019 11:44AM

Is there any update on this ticket?
We are getting frequently below error and unable to use the application -
Error : Failed to establish a database connection. Check connection string, username and password.

Issue 129091233

Description

Issue summary

Comments

su...@google.com <su...@google.com> #2Mar 22, 2019 06:32PM

ka...@gmail.com <ka...@gmail.com> #3Mar 22, 2019 07:31PM

su...@google.com <su...@google.com> #4Mar 22, 2019 08:25PM

ka...@gmail.com <ka...@gmail.com> #5Mar 22, 2019 08:40PM

[Deleted User] <[Deleted User]> #6Mar 24, 2019 01:23PM

su...@google.com <su...@google.com> #7Mar 28, 2019 08:09PM

ka...@gmail.com <ka...@gmail.com> #8Mar 28, 2019 08:38PM

su...@google.com <su...@google.com> #9Mar 28, 2019 09:11PM

ka...@gmail.com <ka...@gmail.com> #10Mar 29, 2019 11:44AM

Add comment

Issue metadata