You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Things can go wrong and jobs can terminate abruptly. If the caller does not get a reference to the job back or does not invoke job.destroy() windows can remain open indefinitely. This results in memory leaks as the process continues to run.
Windows that remain open beyond a specified threshold should be automatically terminated. Subsequently, the owning job should also be freed up for garbage collection.
There should be a new event that clients can observe when this happens
The text was updated successfully, but these errors were encountered:
… more robust window destruction. Destroyed windows can remain in memory, so that needs to be inspected. Also allow clients to remove windows from the cache explicitly fraserxu#163
codecounselor
pushed a commit
to codecounselor/electron-pdf
that referenced
this issue
Feb 9, 2017
Things can go wrong and jobs can terminate abruptly. If the caller does not get a reference to the job back or does not invoke
job.destroy()
windows can remain open indefinitely. This results in memory leaks as the process continues to run.Windows that remain open beyond a specified threshold should be automatically terminated. Subsequently, the owning job should also be freed up for garbage collection.
There should be a new event that clients can observe when this happens
The text was updated successfully, but these errors were encountered: