search

rstudio / chromote

Chrome Remote Interface for R
https://rstudio.github.io/chromote/
155 stars 20 forks source link

Chromote: timed out waiting for response to command Runtime.evaluate #148

Open saleforecast1 opened 6 months ago

saleforecast1 commented 6 months ago

After 3-4 minutes, I encounter an error when using the chromote package on shinyapps.io.

2024-02-20T07:09:54.329205+00:00 shinyapps[11193889]: Warning: Error in : Chromote: timed out waiting for response to command Runtime.evaluate 2024-02-20T07:09:54.334345+00:00 shinyapps[11193889]: [No stack trace available] 2024-02-20T07:09:54.339393+00:00 shinyapps[11193889]: From earlier call: 2024-02-20T07:09:54.345122+00:00 shinyapps[11193889]: 15: 2024-02-20T07:09:54.350193+00:00 shinyapps[11193889]: 13: fn 2024-02-20T07:09:54.355138+00:00 shinyapps[11193889]: 8: retry 2024-02-20T07:09:54.359999+00:00 shinyapps[11193889]: 7: connect$retryingStartServer 2024-02-20T07:09:54.364792+00:00 shinyapps[11193889]: 6: eval 2024-02-20T07:09:54.369868+00:00 shinyapps[11193889]: 5: eval 2024-02-20T07:09:54.377205+00:00 shinyapps[11193889]: 4: eval 2024-02-20T07:09:54.382227+00:00 shinyapps[11193889]: 3: eval 2024-02-20T07:09:54.386992+00:00 shinyapps[11193889]: 2: eval.parent 2024-02-20T07:09:54.392106+00:00 shinyapps[11193889]: 1: local

gadenbuie commented 6 months ago

Hi @saleforecast1, which version of chromote are you using? Is this a new error with code that previously worked with chromote 0.1.2? How does your app use chromote? Do you think you could create a small, reproducible example?

alex-silverman commented 1 month ago

Getting this same error. Originally, we noticed when trying to run shinytest2, which was working until a couple hours ago, but then started producing this error. The only thing that changed in between was that the server was restarted with additional memory and cpu.

I can reproduce the issue now simply by entering the following into the R console: b <-ChromoteSession$new()

Version of Chromote: 0.2.0 Meets all dependency requirements. Some other OS info: image

jj-9 commented 2 weeks ago

Hi all,

having a very similar problem here whithout shinytest2, but it only happens when using the targetId parameter. Also, if it can help, it seems to happen on linux but not windows box.

Erreur : Chromote: timed out waiting for response to command Runtime.evaluate 13. stop(value) at synchronize.R#138 12. doTryCatch(return(expr), name, parentenv, handler) 11. tryCatchOne(expr, names, parentenv, handlers[[1L]]) 10. tryCatchList(expr, classes, parentenv, handlers) 9. tryCatch({ result <- force(expr) if (is.promising(result)) { value <- NULL ... at synchronize.R#112 8. force(expr) at synchronize.R#94 7. domain$wrapSync(expr) at domains.R#134 6. with_promise_domain(domain, { tryCatch({ result <- force(expr) if (is.promising(result)) { ... at synchronize.R#111 5. synchronize(p, loop = private$child_loop) at chromote.R#156 4. self$parent$wait_for(p) at chromote_session.R#475 3. self$wait_for(p) at chromote_session.R#127 2. initialize(...) at new.R#156 1. ChromoteSession$new(parent = default_chromote_object(), targetId = accueil_id)

Regards JJ

jj-9 commented 3 days ago

Hello again,

this message to add that this error occurs since update to latest edge version (128 (ubuntu)). With a version number 126, the problem does not occur. Same thing for windows, after upgrading to edge 128

So I read the changelog of chromote 0.3 and saw there were a specific point for version 128.

After upgrade to chromote 0.3.1, it works good on windows and linux.

Regards JJ