Closed
Bug 842956
Opened 11 years ago
Closed 11 years ago
Extension update process give me some errors
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: devunion, Unassigned)
Details
Attachments
(1 file)
8.02 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17 Steps to reproduce: I've created the extension with addon sdk and checked how it works when a user will update it. As I understand, update process should work like this: previous version of the extension is removed. We are receiving all unload events. New version of the extension is installed with all necessary events. In my case all is OK if I disable the extension. No any errors. Also all is OK when I enable the extension back. But it don't works when I updating it to the next version. Actual results: The extension don't works as expected. Expected results: Updating process should not throw any system errors. Take a look at the attached image to see the error.
Comment 1•11 years ago
|
||
Please attach a copy of your extension
(In reply to Dave Townsend (:Mossop) from comment #1) > Please attach a copy of your extension Unfortunately, customer not allowed me to provide XPI file...
Comment 3•11 years ago
|
||
(In reply to devunion from comment #2) > (In reply to Dave Townsend (:Mossop) from comment #1) > > Please attach a copy of your extension > > Unfortunately, customer not allowed me to provide XPI file... Source code then? Without something it's probably not going to be possible to diagnose this problem, chances are your extension is locking some files open and not releasing those locks when being asked to.
Can you provide a simplified testcase that can reproduce the problem?
Flags: needinfo?(devunion)
Please reopen if/when you can attach a testcase.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(devunion)
You need to log in
before you can comment on or make changes to this bug.
Description
•