Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [Calibre Can't startup/ memory leak #1052

Closed
JeffersonBledsoe opened this issue Oct 30, 2023 · 2 comments
Closed

🐛 [Calibre Can't startup/ memory leak #1052

JeffersonBledsoe opened this issue Oct 30, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@JeffersonBledsoe
Copy link

Description

After upgrading from the previous latest to the latest version of Calibre, I can no longer start the app. Additionally, the error seems to cause a memory leak, leading to the restarting of my device.

Reproduction steps

1. Start up addon
2. Wait for initialising process to get part of the way through

Addon Logs

Obt-Message: Xinerama extension is not present on the server
time="2023-10-30T02:39:00.835591659Z" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
failed to start daemon: Devices cgroup isn't mounted
time="2023-10-30T02:39:10.942190935Z" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
failed to start daemon: Devices cgroup isn't mounted


### Architecture

armv7

### OS

HAos
@JeffersonBledsoe JeffersonBledsoe added the bug Something isn't working label Oct 30, 2023
alexbelgium added a commit that referenced this issue Nov 5, 2023
alexbelgium added a commit that referenced this issue Nov 5, 2023
@alexbelgium
Copy link
Owner

Should be good in latest version pushed I've tested on my system

@JeffersonBledsoe
Copy link
Author

Thanks for looking at this so quickly! I'm not getting the error noted in the issue anymore. I'll close this as completed for now and re-open if I see any more errors/ memory problems over time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants