Skip to content

Conversation

@bruvv
Copy link

@bruvv bruvv commented Jan 17, 2019

Please see a long list of memory leaks and raddar here:
Radarr/Radarr#1580

This debug is not needed in docker/radarr/mono in my opinion.

@sparklyballs whisper 👍

@LinuxServer-CI
Copy link
Contributor

Can an admin please whisper to jenkins to test this PR.

@bruvv
Copy link
Author

bruvv commented Jan 18, 2019

Currently testing the build test builds can be found here:
https://hub.docker.com/u/nivong

@sparklyballs
Copy link
Contributor

absolutely no way putting develop as the branch here, when we already have a develop branch..

@bruvv
Copy link
Author

bruvv commented Jan 19, 2019

I think you miss read this. This is just removing the debug

@sparklyballs
Copy link
Contributor

regardless, the thread you linked mentions nothing of removing --debug as a fix, it only says testing is required

that's fairly inconclusive at this stage.

@aptalca
Copy link
Member

aptalca commented Jan 19, 2019

We are in touch with sonarr/radarr devs and they let us know that there are fixes in the pipeline that will fix the memory leaks. Removing debug is not confirmed to fix any of the issues

@bruvv
Copy link
Author

bruvv commented Jan 20, 2019

@sparklyballs i got you. I found out that jackett is not running with debug. I have been running without debug and so far it seems a bit better. Also the new update fixes some stuff

anyway why is jackett not running with --debug? (not that I do not trust you but just trying to learn :) )
https://github.com/linuxserver/docker-jackett/blob/master/root/etc/services.d/jackett/run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants