What happens if I accidentally leave an app running and click “Install Now” in Software Updater?Update-manager does not show all updatesWhy Does Software Updater Say No updates Available, but apt-get upgrade Shows updates available?can't update from software updaterwhat type of update ubuntu 'software updater' do?I don't have firefox and I'm getting firefox updates?What is the software updater doing compared to e.g. “sudo apt-get update”?Why would System Notifications report updates available but each of sudo apt-get update, software updater and muon updater do not find updates?Prevent Restart after UpdatesSoftware Updater: how to avoid problematic updates and how to rollback a problematic update and avoid it in the future if it still gets throughUbuntu 16.04 Software Updater: you stopped checks for updates
Examples where existence is harder than evaluation
Linear Independence for Vectors of Cosine Values
Names of the Six Tastes
Expl3 and recent xparse on overleaf: No expl3 loader detected
When was it publicly revealed that a KH-11 spy satellite took pictures of the first Shuttle flight?
Is there a need for better software for writers?
How long can fsck take on a 30 TB volume?
Is there an idiom that means "revealing a secret unintentionally"?
Can I bring back Planetary Romance as a genre?
Do these creatures from the Tomb of Annihilation campaign speak Common?
What should I use to get rid of some kind of weed in my onions
Can radiation block all wireless communications?
How to explain intravenous drug abuse to a 6-year-old?
Why doesn't Dany protect her dragons better?
Did any early RISC OS precursor run on the BBC Micro?
Trying to understand a summation
Is there an application which does HTTP PUT?
How can one see if an address is multisig?
Are wands in any sort of book going to be too much like Harry Potter?
Is the tensor product (of vector spaces) commutative?
Was Mohammed the most popular first name for boys born in Berlin in 2018?
Using mean length and mean weight to calculate mean BMI?
Is this strange Morse signal type common?
Identity of a supposed anonymous referee revealed through "Description" of the report
What happens if I accidentally leave an app running and click “Install Now” in Software Updater?
Update-manager does not show all updatesWhy Does Software Updater Say No updates Available, but apt-get upgrade Shows updates available?can't update from software updaterwhat type of update ubuntu 'software updater' do?I don't have firefox and I'm getting firefox updates?What is the software updater doing compared to e.g. “sudo apt-get update”?Why would System Notifications report updates available but each of sudo apt-get update, software updater and muon updater do not find updates?Prevent Restart after UpdatesSoftware Updater: how to avoid problematic updates and how to rollback a problematic update and avoid it in the future if it still gets throughUbuntu 16.04 Software Updater: you stopped checks for updates
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
The Software Updater update-manager
pops up and shows security updates for Firefox, for example. Naturally, I will click on "Install Now" to continue.
However, what happens if I still have Firefox running when I do this? Will it still update Firefox? Will the update be skipped and just pop up next time, again? Will the update force Firefox to close and maybe crash? Will it only partially update the software and possibly break my Firefox installation?
apt software-installation updates firefox update-manager
add a comment |
The Software Updater update-manager
pops up and shows security updates for Firefox, for example. Naturally, I will click on "Install Now" to continue.
However, what happens if I still have Firefox running when I do this? Will it still update Firefox? Will the update be skipped and just pop up next time, again? Will the update force Firefox to close and maybe crash? Will it only partially update the software and possibly break my Firefox installation?
apt software-installation updates firefox update-manager
10
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
3
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
2
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago
add a comment |
The Software Updater update-manager
pops up and shows security updates for Firefox, for example. Naturally, I will click on "Install Now" to continue.
However, what happens if I still have Firefox running when I do this? Will it still update Firefox? Will the update be skipped and just pop up next time, again? Will the update force Firefox to close and maybe crash? Will it only partially update the software and possibly break my Firefox installation?
apt software-installation updates firefox update-manager
The Software Updater update-manager
pops up and shows security updates for Firefox, for example. Naturally, I will click on "Install Now" to continue.
However, what happens if I still have Firefox running when I do this? Will it still update Firefox? Will the update be skipped and just pop up next time, again? Will the update force Firefox to close and maybe crash? Will it only partially update the software and possibly break my Firefox installation?
apt software-installation updates firefox update-manager
apt software-installation updates firefox update-manager
edited May 4 at 19:41
Hashim
11918
11918
asked May 4 at 12:21
finefootfinefoot
2991215
2991215
10
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
3
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
2
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago
add a comment |
10
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
3
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
2
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago
10
10
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
3
3
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
2
2
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago
add a comment |
2 Answers
2
active
oldest
votes
You must be thinking of Windows. Unix did it right, and then later, Windows came along and developed wrong ways of doing things.
With Windows, replacing a file that is in use by a running process can badly affect that process. The process will reference locations within that file and get incorrect information from it, usually with catastrophic results. That's why a Windows update generally requires a reboot to ensure that all processes are using correct versions of libraries etc.
With Unix, once a file has been opened by a process, that same file will always be available to the process even if the original file is removed from the filesystem.
After an update, the filesystem will contain a different version of the file, and all process that start after the update will use that new file. But, unlike Windows, all old Unix processes will continue using the original files that they started with. Even though no longer accessible via the filesystem, those files will persist as long as any process is using them. Eventually, when no processes are using the files, the old version of the files will finally be deleted.
You may of course decide to restart Firefox (or other processes) if you want to get the benefits of the update right away. The choice is yours.
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
add a comment |
Typically, updating a program while it's already open is no problem – as the other answerers have explained, a running process can continue to run even if its executable is deleted.
However, due to Firefox's multi-process model, you may get a prompt to restart it after an update anyway. This is because Firefox spawns new processes to isolate different websites, so if it spawns a new process after you've updated it but before you restart Firefox, the new process will be a newer version of Firefox than the rest of the browser. This can cause various issues, so Firefox might prompt you to restart it before allowing you to continue.
Incidentally, Chrome avoids this by using a "zygote" process that sits around doing nothing; when the browser needs to spawn a new process, instead of asking the OS to execute the browser executable again (which would execute the possibly-updated binary) it asks the zygote process to duplicate itself, and one of the copies then becomes a normal renderer process.
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1140495%2fwhat-happens-if-i-accidentally-leave-an-app-running-and-click-install-now-in-s%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You must be thinking of Windows. Unix did it right, and then later, Windows came along and developed wrong ways of doing things.
With Windows, replacing a file that is in use by a running process can badly affect that process. The process will reference locations within that file and get incorrect information from it, usually with catastrophic results. That's why a Windows update generally requires a reboot to ensure that all processes are using correct versions of libraries etc.
With Unix, once a file has been opened by a process, that same file will always be available to the process even if the original file is removed from the filesystem.
After an update, the filesystem will contain a different version of the file, and all process that start after the update will use that new file. But, unlike Windows, all old Unix processes will continue using the original files that they started with. Even though no longer accessible via the filesystem, those files will persist as long as any process is using them. Eventually, when no processes are using the files, the old version of the files will finally be deleted.
You may of course decide to restart Firefox (or other processes) if you want to get the benefits of the update right away. The choice is yours.
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
add a comment |
You must be thinking of Windows. Unix did it right, and then later, Windows came along and developed wrong ways of doing things.
With Windows, replacing a file that is in use by a running process can badly affect that process. The process will reference locations within that file and get incorrect information from it, usually with catastrophic results. That's why a Windows update generally requires a reboot to ensure that all processes are using correct versions of libraries etc.
With Unix, once a file has been opened by a process, that same file will always be available to the process even if the original file is removed from the filesystem.
After an update, the filesystem will contain a different version of the file, and all process that start after the update will use that new file. But, unlike Windows, all old Unix processes will continue using the original files that they started with. Even though no longer accessible via the filesystem, those files will persist as long as any process is using them. Eventually, when no processes are using the files, the old version of the files will finally be deleted.
You may of course decide to restart Firefox (or other processes) if you want to get the benefits of the update right away. The choice is yours.
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
add a comment |
You must be thinking of Windows. Unix did it right, and then later, Windows came along and developed wrong ways of doing things.
With Windows, replacing a file that is in use by a running process can badly affect that process. The process will reference locations within that file and get incorrect information from it, usually with catastrophic results. That's why a Windows update generally requires a reboot to ensure that all processes are using correct versions of libraries etc.
With Unix, once a file has been opened by a process, that same file will always be available to the process even if the original file is removed from the filesystem.
After an update, the filesystem will contain a different version of the file, and all process that start after the update will use that new file. But, unlike Windows, all old Unix processes will continue using the original files that they started with. Even though no longer accessible via the filesystem, those files will persist as long as any process is using them. Eventually, when no processes are using the files, the old version of the files will finally be deleted.
You may of course decide to restart Firefox (or other processes) if you want to get the benefits of the update right away. The choice is yours.
You must be thinking of Windows. Unix did it right, and then later, Windows came along and developed wrong ways of doing things.
With Windows, replacing a file that is in use by a running process can badly affect that process. The process will reference locations within that file and get incorrect information from it, usually with catastrophic results. That's why a Windows update generally requires a reboot to ensure that all processes are using correct versions of libraries etc.
With Unix, once a file has been opened by a process, that same file will always be available to the process even if the original file is removed from the filesystem.
After an update, the filesystem will contain a different version of the file, and all process that start after the update will use that new file. But, unlike Windows, all old Unix processes will continue using the original files that they started with. Even though no longer accessible via the filesystem, those files will persist as long as any process is using them. Eventually, when no processes are using the files, the old version of the files will finally be deleted.
You may of course decide to restart Firefox (or other processes) if you want to get the benefits of the update right away. The choice is yours.
answered May 4 at 13:13
Ray ButterworthRay Butterworth
545211
545211
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
add a comment |
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
12 hours ago
add a comment |
Typically, updating a program while it's already open is no problem – as the other answerers have explained, a running process can continue to run even if its executable is deleted.
However, due to Firefox's multi-process model, you may get a prompt to restart it after an update anyway. This is because Firefox spawns new processes to isolate different websites, so if it spawns a new process after you've updated it but before you restart Firefox, the new process will be a newer version of Firefox than the rest of the browser. This can cause various issues, so Firefox might prompt you to restart it before allowing you to continue.
Incidentally, Chrome avoids this by using a "zygote" process that sits around doing nothing; when the browser needs to spawn a new process, instead of asking the OS to execute the browser executable again (which would execute the possibly-updated binary) it asks the zygote process to duplicate itself, and one of the copies then becomes a normal renderer process.
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
add a comment |
Typically, updating a program while it's already open is no problem – as the other answerers have explained, a running process can continue to run even if its executable is deleted.
However, due to Firefox's multi-process model, you may get a prompt to restart it after an update anyway. This is because Firefox spawns new processes to isolate different websites, so if it spawns a new process after you've updated it but before you restart Firefox, the new process will be a newer version of Firefox than the rest of the browser. This can cause various issues, so Firefox might prompt you to restart it before allowing you to continue.
Incidentally, Chrome avoids this by using a "zygote" process that sits around doing nothing; when the browser needs to spawn a new process, instead of asking the OS to execute the browser executable again (which would execute the possibly-updated binary) it asks the zygote process to duplicate itself, and one of the copies then becomes a normal renderer process.
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
add a comment |
Typically, updating a program while it's already open is no problem – as the other answerers have explained, a running process can continue to run even if its executable is deleted.
However, due to Firefox's multi-process model, you may get a prompt to restart it after an update anyway. This is because Firefox spawns new processes to isolate different websites, so if it spawns a new process after you've updated it but before you restart Firefox, the new process will be a newer version of Firefox than the rest of the browser. This can cause various issues, so Firefox might prompt you to restart it before allowing you to continue.
Incidentally, Chrome avoids this by using a "zygote" process that sits around doing nothing; when the browser needs to spawn a new process, instead of asking the OS to execute the browser executable again (which would execute the possibly-updated binary) it asks the zygote process to duplicate itself, and one of the copies then becomes a normal renderer process.
Typically, updating a program while it's already open is no problem – as the other answerers have explained, a running process can continue to run even if its executable is deleted.
However, due to Firefox's multi-process model, you may get a prompt to restart it after an update anyway. This is because Firefox spawns new processes to isolate different websites, so if it spawns a new process after you've updated it but before you restart Firefox, the new process will be a newer version of Firefox than the rest of the browser. This can cause various issues, so Firefox might prompt you to restart it before allowing you to continue.
Incidentally, Chrome avoids this by using a "zygote" process that sits around doing nothing; when the browser needs to spawn a new process, instead of asking the OS to execute the browser executable again (which would execute the possibly-updated binary) it asks the zygote process to duplicate itself, and one of the copies then becomes a normal renderer process.
answered May 4 at 13:50
JoshJosh
7741621
7741621
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
add a comment |
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
1
1
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
Also, with a complex application like Firefox, everything it could possibly need to deal with anything it encounters isn't loaded into memory when the program launches. So components that get loaded as needed may similarly create a mismatch of versions. I've often had Firefox hang when updating it while it was running.
– fixer1234
May 5 at 0:33
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
It's not just browsers with multi-process models, but any situation where libraries are used for IPC and the libraries can be loaded before and after the update - although browsers are probably the most well known example of this these days (COM interop on Windows being pretty prevalent means many more programs can implicitly do something like this though). I also can't imagine that Chrome completely avoids this problem with the zygote process - does it really load every single library that it might need at any point at startup?
– Voo
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Voo asks "does it really load every single library that it might need at any point at startup?". I don't know about this specific example, but in general it isn't necessary. All that is required is to ensure that each possible library is opened at startup, thereby guaranteeing that the correct data will be read should it ever be needed. Opening a file (or dozens of files) is a trivial expense compared with loading everything they contain.
– Ray Butterworth
yesterday
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Ray Fun fact: dlopen only takes a file name but not file descriptors so that might not be as simple as you thought it would be (you can play around with /proc but that's notoriously different along the *nixes). But the bigger issue is that that would eliminate most use cases where dynamic loading is used to begin with.
– Voo
21 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
@Voo, sorry, I mistakenly thought this comment was in the unix-oriented thread, not about Windows and dlls.
– Ray Butterworth
11 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1140495%2fwhat-happens-if-i-accidentally-leave-an-app-running-and-click-install-now-in-s%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
10
Nothing happens, Firefox is open in Ram. Sometimes it detects the update and tells you to restart the browser. But maybe someone with more insight and references can give a better answer.
– RoVo
May 4 at 12:25
3
I don't know specifically about Ubuntu, but on Arch (and I don't think it's all that different in this case), updating firefox under its feet while running seems to work, but then the first thing you do in firefox crashes the thing. I've always just attributed that to the complex nature of modern-day browsers, runtime-loading all kinds of stuff. But firefox is the only thing that happens with for me.
– tomsmeding
May 4 at 20:03
2
Firefox will stop the next time you open a tab, and tell you that it needs to restart. Other apps may do something different.
– Michael Hampton
2 days ago