Closed RoguedBear closed 2 years ago
update: when this happens, the bot doesn't post anything on discord. possible source of error could be these lines since: https://github.com/RoguedBear/codezinger-due-date-scraper/blob/7401be2e0db262c5137badf2e560efa05ae89d89/scrap_data.py#L173-L176
since they're not under try/except
relevant log files: red is the last log and since when the chromium high cpu usage is started green is when i manually restarted the container
processed running when cpu usage is high:
Last log message:
possible workarounds:
--disable-gpu
paramexact LOC where the freezing happens (confirmed via logs): https://github.com/RoguedBear/codezinger-due-date-scraper/blob/7401be2e0db262c5137badf2e560efa05ae89d89/scrap_data.py#L176
crond: USER root pid 9 cmd /entrypoint.sh
codezinger-due-date-scraper Copyright (C) 2022 RoguedBear, Ya-s-h
This program comes with ABSOLUTELY NO WARRANTY; see COPYING
This is free software, and you are welcome to redistribute it
under certain conditions; see COPYING
loaded short names
Starting browser...
browser started
crond: USER root pid 9 cmd /entrypoint.sh
codezinger-due-date-scraper Copyright (C) 2022 RoguedBear, Ya-s-h
This program comes with ABSOLUTELY NO WARRANTY; see COPYING
This is free software, and you are welcome to redistribute it
under certain conditions; see COPYING
loaded short names
Starting browser...
browser started
logging in.
Logged in. allegedly
sorting
loading more
Processing stuff
[<pyppeteer.element_handle.ElementHandle object at 0x7f1d26000640>, <pyppeteer.element_handle.ElementHandle object at 0x7f1d26001030>]
2
Scraped 2 questions(50%)
awaiting browser close
Browser closed
Processing new events...
Sent 0 new webhook messages
Finished, exiting...
update:
unable to reproduce the problem when running current version and previous version repeatedly, but --disable-gpu
does help in drastically reducing CPU usage.
graph:
running the program for 2 weeks, commit https://github.com/RoguedBear/codezinger-due-date-scraper/commit/a64681c2b01c03d78f1711d9987c3053e9fe66d3 does seem to have fixed the issue
orphan chromium processes still remain active and consume cpu as if the browser isn't closed.
workaround for now: