You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
The application encountered an error:
The server has exited with an error code of: 0
Most functions in AGI are unavailable without a server.
You can restart the server, exit AGI, or close the dialog to continue without a server.
Please check the logs for details.
Reproduction steps
Steps to reproduce the behavior:
Stacktrace
Please paste a stacktrace here if it's available.
com.google.gapid.Server$GapisInitException: Failed to initialize the graphics debugger
at com.google.gapid.Server.connect(Server.java:85)
at com.google.gapid.Main$UI.startup(Main.java:150)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.TimeoutException: Waited 3000000000 nanoseconds (plus 74968410 nanoseconds delay) for com.google.common.util.concurrent.SettableFuture@51f09465[status=PENDING, setFuture=[com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture@373178de[status=PENDING, info=[inputFuture=[io.grpc.stub.ClientCalls$GrpcFuture@21c06cd8[status=PENDING, info=[GrpcFuture{clientCall=HeaderAttachingClientCall{delegate=ClientCallImpl{method=MethodDescriptor{fullMethodName=service.Gapid/GetServerInfo, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@4a3f2c1b, responseMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@1fb9da85, schemaDescriptor=com.google.gapid.proto.service.GapidGrpc$GapidMethodDescriptorSupplier@23f2a624}}}}]]], function=[com.google.gapid.server.Client$$Lambda$61/1817365648@1f6b82e]]]]]
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:495)
at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:98)
at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:307)
at com.google.gapid.rpc.Rpc.get(Rpc.java:54)
at com.google.gapid.Server.fetchServerInfo(Server.java:129)
at com.google.gapid.Server.connect(Server.java:77)
... 8 more
Screenshots
If applicable, add screenshots to help explain your problem.
Additional debugging information
Please attach the generated gapis.log and gapic.log files you will find in the temp folder (e.g. /tmp/ on linux).
If using Android: Please attach a full logcat dump (adb logcat -d > logcat-full.txt) that contains logs since AGI was started.
The text was updated successfully, but these errors were encountered:
@Asmot this bug has been stuck for your feedback for more than 30 days so we're closing it. Please re-open if you can provide more information, thank you!
Environment information:
If tracing on Android:
Bug description
The application encountered an error:
The server has exited with an error code of: 0
Most functions in AGI are unavailable without a server.
You can restart the server, exit AGI, or close the dialog to continue without a server.
Please check the logs for details.
Reproduction steps
Steps to reproduce the behavior:
Stacktrace
Please paste a stacktrace here if it's available.
com.google.gapid.Server$GapisInitException: Failed to initialize the graphics debugger
at com.google.gapid.Server.connect(Server.java:85)
at com.google.gapid.Main$UI.startup(Main.java:150)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.TimeoutException: Waited 3000000000 nanoseconds (plus 74968410 nanoseconds delay) for com.google.common.util.concurrent.SettableFuture@51f09465[status=PENDING, setFuture=[com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture@373178de[status=PENDING, info=[inputFuture=[io.grpc.stub.ClientCalls$GrpcFuture@21c06cd8[status=PENDING, info=[GrpcFuture{clientCall=HeaderAttachingClientCall{delegate=ClientCallImpl{method=MethodDescriptor{fullMethodName=service.Gapid/GetServerInfo, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@4a3f2c1b, responseMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@1fb9da85, schemaDescriptor=com.google.gapid.proto.service.GapidGrpc$GapidMethodDescriptorSupplier@23f2a624}}}}]]], function=[com.google.gapid.server.Client$$Lambda$61/1817365648@1f6b82e]]]]]
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:495)
at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:98)
at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:307)
at com.google.gapid.rpc.Rpc.get(Rpc.java:54)
at com.google.gapid.Server.fetchServerInfo(Server.java:129)
at com.google.gapid.Server.connect(Server.java:77)
... 8 more
Screenshots
If applicable, add screenshots to help explain your problem.
Additional debugging information
adb logcat -d > logcat-full.txt
) that contains logs since AGI was started.The text was updated successfully, but these errors were encountered: