-
One of my team members added this debugger to our Phoenix project recently (two days ago). But in these last two days my OOM deamon (Fedora Linux) is killing the phx server constantly even not using the debugging monitor (I don't use personally), after trying to allocate more than 10GB of memory (the usual is < 1GB) I did removed the dependencies locally to test and it solved for me, but other team devs are not having the same issues, so I don't want to remove from our project entirely. Great project and ideas, btw, I had something similar as a former Ruby on Rails dev, so I appreciate the efforts I can't provide more details on why it's using too much memory right now (rushing to deliver some new code and features), The question is: Is there an easy way to disable this debugger completely by using an env variable (or a config entry that reads a env variable)? Adding this to the README also will potentially help. Thanks a lot! I hope this project grows as well. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hey @rdlu - we'll add a config to disable LiveDebugger entirely. For now you can try setting |
Beta Was this translation helpful? Give feedback.
-
@rdlu since LiveDebugger 0.2.0 you can disable LiveDebugger using this config
|
Beta Was this translation helpful? Give feedback.
@rdlu since LiveDebugger 0.2.0 you can disable LiveDebugger using this config
config :live_debugger, :disabled?, true