Extension crashes after the computer was asleep for more than about 50 minutes
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
People
(Reporter: giregk, Unassigned, Mentored)
Details
Attachments
(1 file)
|
32.30 KB,
image/png
|
Details |
reproduced.png
Steps to reproduce:
- I open the popup of our UpSignOn extension
- I let my computer in sleep mode for more than 50 minutes
- When I open my computer again and click on the extension popup again, it shows nothing because it crashes
Actual results:
The extension crashes. The reason is that Firefox tries to call a function that no longer exists in the code. It's as if Firefox has loaded an older version of the extension from some cache.
The extension works again when I restart Firefox, but it's not a long term fix.
The bug is definitely fixed I manually go to the addons page and manually "search for updates". So I guess the automatic update lacks a clearing of some cache that is used after computer wake up.
Expected results:
It should never crash and I should not have to do this manual "search for updates" after each automatic update.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Application Update' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•3 years ago
|
||
I'm not sure if we have a way of knowing for sure - but it almost sounds like the extension did not have an update available when you updated Firefox, but then did later.
Do you have any idea of how long it was between Firefox applying the update, and you restarting for it?
Which version of Firefox are you running? If on Nightly, I'm wondering if the Nightly you updated to removed the function in question. We don't do any version bumps for most Nightly updates, so I'm less surprised if this situation is happening there.
I'm running Firefox 99.0 (64 bits), not the Nightly.
I don't have any idea of the time between Firefox auto-updating my addons and me needing to restart it or if it could be linked to an update to Firefox itself. To be honest, I don't use Firefox that much myself. One of my customers reported this issue with my addon. I was able to reproduce the issue and the fix consistently with several people though.
|
|
||
Comment 4•3 years ago
|
||
I tried a few things to reproduce this, including:
- starting from an older Firefox version + latest UpSignOn
- starting from an older Firefox version + older UpSignOn
- starting from the current Firefox version + latest UpSignOn
- starting from the current Firefox version + older UpSignOn
...but was unable to :(.
I'd love to know exactly what Firefox and UpSignOn version you've started with to reproduce, as well as how to open the pop-up you mentioned.
The extension "popup" is the small view that appears when you click on the extension's icon.
Sorry, I'm not going to be very helpful about exactly which version of Firefox and which version of the extension started the bug. That bug was reported to me with various versions of the extension (until I decided to take a look at it) by several persons who run Firefox on their personal computer (probably up to date version) and by several persons who run the ESR version of Firefox (pros).
I don't know how you tested, but remember that if you manually click on "search for updates" in the addons page, you won't be able to reproduce the bug.
I managed to reproduce this issue on Firefox 106.0b9 on Windows 10 using the STR from the reporter. This error appeared in the Extension pop-up after interrupting Sleep Mode(I left it in Sleep Mode for about an hour). Will do further testing to see if it's reproducible on other platforms/versions of Fx.
Setting as NEW so that the developers can have a look at it.
|
||
Updated•3 years ago
|
I could also reproduce the crash on Ubuntu 22 but not on macOS 12. I tested 107.0a1 Nightly and the extension crashes there as well.
Hello,
Is this bug expected to be fixed any time soon ?
This problem is critical to me because I loose a lot of customers for this reason.
I finally understood what happened with that "bug". It was actually a mistake in our code, not with Firefox. We wrongly thought that since it was working in Chrome, it wasn't a problem with us... Apologies
Description
•