downthemall icon indicating copy to clipboard operation
downthemall copied to clipboard

Published 20 hours ago • verified publisher icon downthemall

Manager is empty and new downloads could not be started. Appears to be a problem with "db_1"

Open mfaizsyahmi opened this issue 2 years ago • 2 comments

Desktop (please complete the following information):

  • OS: Win7SP1
  • Browser and version: FF104
  • DownThemAll! version: latest

Describe the bug Manager is empty and new downloads could not be started. This started happening after I upgraded to FF104 and after I closed and re-launch FF. This only happens on my main FF profile.

To Reproduce Steps to reproduce the behavior:

  1. Close Firefox. Then relaunch Firefox.
  2. Open DTA Manager
  3. See error. Manager is empty when there should be previously paused/errored downloads. New downloads could not be started. previously paused/errored downloads

Expected behavior The DTA Manager loads as normal, and all previously paused/errored downloads would appear. New downloads can be initiated and queued and running as normal.

Screenshots What Manager looks like (should be filled with failed downloads from previous sessions): image

Find the devtool console error log below: image

Additional context This problem only appears to happen on my main profile. I have another profile for special uses with the same FF and DTA versions and DTA works as normal there. At the very least, I'd like a pointer about how to reset the extension on Firefox

mfaizsyahmi avatar Aug 28 '22 06:08 mfaizsyahmi

I removed and reinstalled the extension and it now works. Old download queues are forever lost now though. I'll restart firefox to see if problem recurs.

Okay, problem is solved!
Please disregard this thread. Sorry for any problems.

mfaizsyahmi avatar Aug 28 '22 06:08 mfaizsyahmi

This happens every time I restart Firefox now. Uninstalling and reinstalling would fix the issue but it's a chore, and I had to reconfigure everything.

mfaizsyahmi avatar Sep 01 '22 08:09 mfaizsyahmi

This seems rather curious honestly. Are you using that permanent private browsing mode by chance. I'll try to add some code to harden things up and make such failures more unlikely, however I cannot really reproduce this myself, so I can only really guess what's the underlying cause for this.

(Somehow the underlying db object is not initialized. Not entirely sure how this happens)

nmaier avatar Nov 30 '22 00:11 nmaier