Replies: 3 comments
-
the very outdated standalone-chrome-debug:3.141.59 does seem work. but that was last updated 2 years ago and is deprecated in favour of the image i was trying to use that does not work with changedetect |
Beta Was this translation helpful? Give feedback.
-
that older chrome driver image that the wiki recomended also seems to have a few issues. it worked for about an hour and then changedetect was giving some error about not being able to find chrome and it kept doing that until i restarted the container |
Beta Was this translation helpful? Give feedback.
-
It seems like there might be an issue with the interaction between the Chrome driver and changedetection.io. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
DO NOT USE THIS FORM TO REPORT THAT A PARTICULAR WEBSITE IS NOT SCRAPING/WATCHING AS EXPECTED
This form is only for direct bugs and feature requests todo directly with the software.
Please report watched websites (full URL and any settings) that do not work with changedetection.io as expected IN THE DISCUSSION FORUMS or your report will be deleted
CONSIDER TAKING OUT A SUBSCRIPTION FOR A SMALL PRICE PER MONTH, YOU GET THE BENEFIT OF USING OUR PAID PROXIES AND FURTHERING THE DEVELOPMENT OF CHANGEDETECTION.IO
THANK YOU
Describe the bug
When trying to scrape pages using the chrome driver docker image "selenium/standalone-chrome:109.0" i just get the following error
Message: disconnected: unable to connect to renderer (failed to check if window was closed: disconnected: unable to connect to renderer) (Session info: chrome=109.0.5414.119) Stacktrace: #0 0x5589a96b9303 <unknown> #1 0x5589a948dd37 <unknown> #2 0x5589a94756bb <unknown> #3 0x5589a9469b84 <unknown> #4 0x5589a9469fac <unknown> #5 0x5589a951527f <unknown> #6 0x5589a95157c5 <unknown> #7 0x5589a94ea982 <unknown> #8 0x5589a950288c <unknown> #9 0x5589a94ea753 <unknown> #10 0x5589a94bda14 <unknown> #11 0x5589a94beb7e <unknown> #12 0x5589a970832e <unknown> #13 0x5589a970bc0e <unknown> #14 0x5589a96ee610 <unknown> #15 0x5589a970cc23 <unknown> #16 0x5589a96e0545 <unknown> #17 0x5589a972d6a8 <unknown> #18 0x5589a972d836 <unknown> #19 0x5589a9748d13 <unknown> #20 0x14a280f1f609 start_thread
I watched the chrome driver through the vnc in the docker container and the page did successfully open so changedetect is talking to the driver. Even though i have changedetect set to wait 5 seconds before extracting the text, it seems to close the page almost instantly after it loads so maybe something is crashing.
Version
v0.44
To Reproduce
Steps to reproduce the behavior:
Create docker container with image "selenium/standalone-chrome:109.0" latest tag also has the same issue
Tell change detect to use that chrome driver
try to scrape a page
! ALWAYS INCLUDE AN EXAMPLE URL WHERE IT IS POSSIBLE TO RE-CREATE THE ISSUE - USE THE 'SHARE WATCH' FEATURE AND PASTE IN THE SHARE-LINK!
https://changedetection.io/share/kduj_tfkrv0a
Expected behavior
the page should be scraped and it shouldn't show the error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions