Open
Bug 1842613
Opened 1 year ago
Updated 1 year ago
Multiple `Error: Error(s) encountered during statement execution: database disk image is malformed` errors when opening the migration window for the first time, or after a Firefox restart
Categories
(Firefox :: Migration, defect, P3)
Tracking
()
NEW
People
(Reporter: atrif, Unassigned)
References
Details
Attachments
(2 files)
Filled on request 1840792#c12
Found in
- 117.0a1 (2023-07-10)
Affected versions
- 117.0a1 (2023-07-10)
Tested platforms
- Affected platforms: Windows 10x64 (only on one station)
- Unaffected platforms: Windows 11x64,Ubuntu 22.04, macOS 12
Steps to reproduce
- Open the migration window and observe the browser console.
Expected result
- No errors are displayed and the migration window is opened almost instantly.
Actual result
- Multiple
Error: Error(s) encountered during statement execution: database disk image is malformed
errors and migration window takes some time to open.
Regression range
- Not a regression.
Additional notes
- Attached a screen recording.
- The errors are displayed only for the first time after the migration window is opened. Opening the migration window again in the same session will no longer display the errors. However, restarting Firefox will display the errors again but only for the first time.
- Note this happens on only one Windows 10 machine.
Comment 1•1 year ago
|
||
:atrif, if you think that's a regression, could you try to find a regression range using for example mozregression?
Reporter | ||
Comment 2•1 year ago
|
||
I don't know, if this relates to this issue but if extensions (browser.migrate.chrome.extensions.enabled:true) are enabled I am seeing these errors as well (see attachment).
Reporter | ||
Comment 3•1 year ago
|
||
Setting 116 as affected because bug 1840792 was uplifted.
status-firefox116:
--- → affected
Reporter | ||
Comment 4•1 year ago
|
||
Hmm... Unfortunately, it seems that the errors can reaper in the same session if the Preferences page is closed and reopened and the Migration window is opened again. The steps are:
- Open the migration window and close it.
- Click the Preferences page and open the browser console.3
- Open the migration window again and observe the browser console.
You need to log in
before you can comment on or make changes to this bug.
Description
•