-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Bug: AppExecutorUtil.getAppScheduledExecutorService().scheduleWithFixedDelay #149
Comments
This is expected. You have to manually free the resources between plug-in
reloads. I find it most convenient to use Disposables, for example see
“pluginDisposable” in the hello world example bundled with LivePlugin.
…On Wed, 19 Oct 2022 at 16:13, John ***@***.***> wrote:
The timer stays loaded in the context of the LivePlugin.
Even when you reload (or stop) the plugin, it will still continue in the
background.
If you start it several times you'll have mulitple of those timers running
on the old code.
—
Reply to this email directly, view it on GitHub
<#149>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAG5V7A6ZHRPMQGM7VOOYTWEAF2FANCNFSM6AAAAAARJHMCDY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks for the update, I tried and didn't work for me. Though I'm not a java developer ;) |
This is not specific to Java.
It might be useful to add to LivePlugin a wrapper API for |
Imho it doesn't fit to the idea of "unloading" a plugin that it keeps 'lost' background tasks in the IDE context. Your LivePlugin is the only thing I found that actually is well working, comes with samples and is not a total pain to implement. |
The timer stays loaded in the context of the LivePlugin.
Even when you reload (or stop) the plugin, it will still continue in the background.
If you start it several times you'll have mulitple of those timers running on the old code.
The text was updated successfully, but these errors were encountered: