java.lang.OutOfMemoryError: Could not allocate JNI Env

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by danvinokour
, 1 year ago
Could not allocate JNI Env
via Stack Overflow by Hector
, 1 week ago
via GitHub by baole
, 1 year ago
via Stack Overflow by sum
, 1 year ago
via GitHub by Fgabz
, 1 year ago
via GitHub by AndroidJohnsonWang
, 1 year ago
java.lang.OutOfMemoryError: Could not allocate JNI Env
at java.lang.Thread.nativeCreate(Thread.java)
at java.lang.Thread.start(Thread.java:1063)
at okhttp3.internal.framed.FramedConnection.(FramedConnection.java:173)
at okhttp3.internal.framed.FramedConnection.(FramedConnection.java:55)
at okhttp3.internal.framed.FramedConnection$Builder.build(FramedConnection.java:577)
at okhttp3.internal.io.RealConnection.connectSocket(RealConnection.java:161)
at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:188)
at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:127)
at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:289)
at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:241)
at okhttp3.RealCall.getResponse(RealCall.java:240)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:198)

Users with the same issue

2 times, 3 months ago
19 times, 6 months ago
Once, 1 year ago
47 times, 1 year ago
4 times, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.