Comment #83 on issue 13 by iambob: Closing last tab also closes window http://code.google.com/p/chromium/issues/detail?id=13
I will reiterate... my solution was a background solution only. If the last tab (application) is closed... rather than the application space (the extra chrome.exe) closing immediately... it could remain running for 5 seconds or so. If no action is taken before that time is up, all of the normal maintenance and background processes are run for closing... and the next time the application is run, it can do its normal start-up processing. If, however, before that 5 second interval is up, a new Chromium application (tab/browser) is opened, it can attach to that existing chrome.exe process and you would not have unnecessary startup and shutdown processing happening every time the last tab is "accidentally" closed. This would only work this way if the TAB's close button is clicked. If the close button of the whole window is clicked, it could either perform as it currently does (nuking everything immediately)... or, if it would be more in line with consistency to follow this same rule, it could do this as well. The only time it could become a problem is if someone were closing Chromium for a reason (memory leak?) and really wanted it completely flushed from memory. To do this, they would need to wait out the 5 seconds or so, unless closing the window itself terminated everything immediately. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
