evandrocoan
commented
4 months ago I am running on Windows with 4175, and I do not see this behavior, although I do not see the plugin unloaded to be called:
import os
import sublime_plugin
def plugin_loaded():
with open(os.path.expanduser("~/out.txt"), "a") as f:
print(f"pid={os.getpid()}, plugin_loaded", file=f, flush=True)
def plugin_unloaded():
with open(os.path.expanduser("~/out.txt"), "a") as f:
print(f"pid={os.getpid()}, plugin_unloaded", file=f, flush=True)
class Event(sublime_plugin.EventListener):
def on_exit(self):
with open(os.path.expanduser("~/out.txt"), "a") as f:
print(f"pid={os.getpid()}, on_exit", file=f, flush=True)Output:
pid=13104, plugin_loaded
pid=13104, on_exit
pid=20936, plugin_loaded
pid=20936, on_exitAre you sure Sublime Text had exited after you closed it? Can you run ps aux | grep sublime after you exit it?
Can you try this version with flush=True?
giampaolo
FichteFoll
BenjaminSchaaf
Description of the bug
I'm using
on_exitevent to save session data on disk, but it turns outon_exitexecutes VERY late, like 3-5 secs after ST terminated. During this time I can start a new instance of ST. This is a problem because a typical use case ofon_exitis to flush session data to a file on ST termination (see https://github.com/sublimehq/sublime_text/issues/10), and read / reload that file on ST startup. In this caseon_exitsimply cannot be relied upon. Since it fires up so late, it can easily lead to data corruption, as the old ST process will overwrite session data of the new ST process. To me this looks like a potentially critical bug, which also happen to be quite hard to spot.In addition, it seems that
plugin_unloaded()is erroneously executed on ST startup.Steps to reproduce
1) put the following code in any ST plugin under
User/:2) open a shell and watch events as they occur with
tail -f ~/out.txtcommand 3) Stop ST 4) Start another instance of STExpected behavior
The order of events I would expect is:
...or:
Actual behavior
Instead I get:
This shows 2 problems:
on_exitis executed very late, AFTER I start a new ST instance and afterplugin_loaded.plugin_unloadedis erroneously executed on ST startupSublime Text build number
4175
Operating system & version
Linux Ubuntu 22.04
Possible solutions I see
plugin_unloaded()functions when ST terminates cleanly (e.g. viaalt+F4). This looks sub-optimal though, as we can't controlplugin_unloaded()execution order.on_quitevent that, differently fromon_exit, executes much sooner, when all plugins have been unloaded and all views and windows have been closed.