will try
Will try to do so.
- yereverluvinunclebert
Post a reply
Topic review
- martin
Re: should each tab run in a separate process?
Sorry, it is unlikely this ever gets implemented.
Anyway, I would like to fix the bug you are facing. Are you able to reproduce it easily?
Anyway, I would like to fix the bug you are facing. Are you able to reproduce it easily?
- yereverluvinunclebert
should each tab run in a separate process?
I have regularly found that I have to kill winscp when it gets its "knickers in a twist" when one tab cannot connect for some reason causing the whole app. to freeze.
For example, I may have connected to a site using cpanel and then I may suspend that account from WHM meaning that site is no longer available. When I return to the current WinSCP session then it freezes and I see the spinning hourglass over the app. I cannot close the offending session nor can I close the app. This is a real pain if I have multiple tabs open and I always have multiple tabs open.
I currently have to kill the WinSCP app from task manager. If each connection had its own process then the application and the other tabs would not be affected and I could kill the offending tab manually. Being able to identify the process in task manager would also help me kill an individual process from there.
For example, I may have connected to a site using cpanel and then I may suspend that account from WHM meaning that site is no longer available. When I return to the current WinSCP session then it freezes and I see the spinning hourglass over the app. I cannot close the offending session nor can I close the app. This is a real pain if I have multiple tabs open and I always have multiple tabs open.
I currently have to kill the WinSCP app from task manager. If each connection had its own process then the application and the other tabs would not be affected and I could kill the offending tab manually. Being able to identify the process in task manager would also help me kill an individual process from there.