1503883 - The Dev Tools Debugger tab is empty. It does not display anything after 63.0.1 update

Status: RESOLVED DUPLICATE of bug 1517531

(DevTools :: Debugger, defect)

Description

[jonathanfever]

Attachment: firefox-63.0.1--empty-debugger-tab-dev-tools.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

I updated Firefox from 63.0.0 to 63.0.1, via Firefox update notification. Restarted Firefox.


Actual results:

The Dev Tools "Debugger" tab is empty. It does not display anything in the Debugger tab after the 63.0.1 update on various websites.


Expected results:

I should see a working Dev Tools Debugger tab to debug JS code

Comment 1

[jonathanfever]

Just checked and downloaded from Mozilla ftp version 63.0.0 and Debugger tab in dev tools was also broken showing nothing. Then I downloaded from Mozilla FTP version 62.0.3 and Debugger tab in dev tools is visible and working like it should.

https://ftp.mozilla.org/pub/firefox/releases/62.0.3/win64/en-US/

Comment 2

[jonathanfever]

Tsted a new profile and teh debugger worked. So I was able to get the Debugger working after i went into my current profile files and deleted all extensions and previous extension files from before firefox was updated to new Quantum. Looks like Firefox did not delete old extension addon files and something was corrupt.

Comment 3

[Rares Doghi, Desktop QA]

I tried to reproduce this issue but without success also based on Comment 2 I will mark this issue as Resolved Works for Me, please re-open this issue if it will occur again.

Comment 4

[James B]

Just as a data point this is happening to me right now.  I will verify that a new profile fixes the issue, but I think it's worth trying to reproduce this and check for whatever stale / broken leftover files cause the misbehavior automatically during the upgrade process.  If it happens to me and the OP, it's probably going to happen to a lot more people.

Comment 5

[James B]

Please reopen.  I think I've got it figured out.  On the OP's suggestion, I dug around in my profile and found that if I delete `storage/permanent/indexeddb+++fx-devtools`, the bug stops happening.  This is happening on an isolated network that can't reach the internet, so I can't supply a copy of the broken files, but the structure is

/
  .metadata
  .metadata-v2
  idb/
    {some guid}.tmp
    {some gibberish}-cans.sqlite
    {same gibberish}-cans.files/
      49 (no extension)
      {some guid}.tmp


The `.metadata` files were last modified almost a year ago.  The `idb/` and `{blah}-cans.files/` directories are modified every time I run dev tools.  All other files haven't been touched since September.

Hopefully this helps at least give you an idea of how it might be breaking the state-loading process of the debugger tab.  Clearly there's a serious failure in error handling during debugger-tab initialization, and hopefully it won't be ignored.

Comment 6

[Rares Doghi, Desktop QA]

Given the fact that this issue occurs to more people and some extra information has been provided I think it's worth looking into this issue, I will reopen it based on Comments 4 and Comment 5.

Comment 7

[Jason Laster [:jlast]]

Thanks for the report. we recently started saving breakpoints to indexed db which should be faster and be able to store way more breakpoints. It looks like in your case the IDB database might be corrupted previously. Could you see if there are any exceptions in the browser console? https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Comment 8

[James B]

I do see errors in the browser console, but I'm not sure they are related to this issue.  There are a number of them that repeat but mostly along the lines of 

> IndexedDB UnknownErr: ActorsParent.cpp:605
> UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code.

and 

> Bootstrapped manifest not alllowed to use 'resource' directive

The IndexedDB errors appear to come from history-persistence.js:29:5 and Promise-backend.js:931:21, if that helps.  I think the history-persistence error might only happen when I open the (web) console tab of dev tools -- I was switching back and forth between that and the Debugger tab to see if it generated an error when the Debugger tries to open.  The one in Promise-backend.js seems to only happen when trying and failing to open the Debugger, but unfortunately that appears to be a generic promise rejection handler and doesn't shed much light on what's actually failing.  You're definitely on to something with your IndexedDB suspicions, though.

Comment 9

[joe]

I' am using 63.0.3 (64-Bit) on windows7 and have got the same problem. I renamed the `storage/permanent/indexeddb+++fx-devtools` but I still have the same problem. The debugger-tab remains empty. Any suggestions?

Comment 10

[James B]

Joe, have you tried launching the same install with a new profile?  (Use `firefox.exe --ProfileManager` to make a new one.)  If this fixes it, there's something about your profile keeping the debugger from running.  I actually made a backup copy of my profile and just started deleting stuff then restarting to see when it came back, which is how I narrowed it down to that specific storage folder mentioned upthread.  Of course, if using a new profile *doesn't* fix it, you must have a different issue.

Comment 11

[joe]

Thx James B. A complete new profile fixed my problem. But I'am losing all my preferences and open Tabs and the documentation of al the files stored in the Profiles-Folder is very poor.

Comment 12

[James B]

I'm afraid I can't help with what to delete, specifically, to salvage your old profile.  I just tried a shotgun approach -- delete some stuff, try it, if that didn't fix it, put it back and try something else.  If I had been less invested in that profile, I'd suggest just exporting your bookmarks and starting again.  (You can bookmark all open tabs at once by right clicking any tab, it's an option in the context menu...)

Comment 13

[Logan Smyth [:loganfsmyth]]

This is definitely something we'll need to investigate more. I'm closing this in favor of https://bugzilla.mozilla.org/show_bug.cgi?id=1517531 since we've had 2 separate issues filed about this.

Comment 14

[Tom Tung [:tt, :ttung]]

I'm Tom working on QuotaManager, IndexedDB storage stuff.

Hi James,

If you happen to keep the broken "storage/permanent/indexeddb+++fx-devtools/idb" directory, could you try to remove the xxx.tmp files there? I think that should fix the issue and such files shouldn't exist in IndexedDB directory. Note that please copy those files to somewhere else if you are afraid to lose the data from "indexeddb+++fx-devtools" (I think it's related to your dev-tools setting or something similar)

Hi Joe,

Could you also check if you also have such ".tmp" file in your idb directory? If so, could you check if deleting them works? Note that please copy those files to somewhere else if you are afraid to lose the data from "indexeddb+++fx-devtools" (I think it's related to your dev-tools setting or something similar)

Comment 15

[joe]

Hi Tom,
I still tried it and deleted the hole directory "storage/permanent/indexeddb+++fx-devtools". Without any success.

Comment 16

[James B]

Hi :tt, I did keep the broken directory. I copied it back as-is, checked that the debugger is still broken (yes), quit FF, then deleted the two .tmp files listed in the directory tree from comment #5. When I started FF, the debugger tab worked. So, I think that confirms your hunch, at least as far as my own symptoms are concerned.

Comment 17

[Tom Tung [:tt, :ttung]]

Thank both of you for providing more information

(In reply to joe from comment #15)

Hi Tom,
I still tried it and deleted the hole directory "storage/permanent/indexeddb+++fx-devtools". Without any success.

Joe, could you run the https://firefox-storage-test.glitch.me/ to see what the result is? It's a website basically tests the storage initialization. If unfortunately, your result is not really good, then there is a bug [1] for tracking this kind of issues. It would be also useful if you can find some specious message on the browser console or get the log from debug build.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1482662

(In reply to James B from comment #16)

Hi :tt, I did keep the broken directory. I copied it back as-is, checked that the debugger is still broken (yes), quit FF, then deleted the two .tmp files listed in the directory tree from comment #5. When I started FF, the debugger tab worked. So, I think that confirms your hunch, at least as far as my own symptoms are concerned.

That's good news that we find out the problematic files. However, I don't believe it's created by current IndexedDB, and I couldn't find the code for doing that, neither. I suspect they could be created by OS or anti-virus applications. I will keep tracing the code to check whether it could be done by Firefox (other components).

Comment 18

[Tom Tung [:tt, :ttung]]

ni Joe in the case that you miss the comment 17

Comment 19

[joe]

Hi Tom, I do not know that I can help you anymore. I fixed my problem with creating a complete new profile. Now it works fine. By that, I deleted my old profile completely.
Here the text I will get by running the glitch.me site with my new profile.

Overview:
Storage is working. This is your first visit or all storage was automatically cleared.
Specific Subsystem Statuses:

LocalStorage
Good: Totally Working. (fullyOperational)
QuotaManager
Good: Totally Working. (fullyOperational)
IndexedDB
Good: Totally Working. (fullyOperational)
Cache API
Good: Totally Working. (fullyOperational)

Debug Info:

{
"v": 1,
"curVersion": 64,
"prevVersion": 0,
"ls": {},
"qm": {
"lastWorkedIn": 64
},
"idb": {
"persistentCreatedIn": 64,
"persistentLastOpenedIn": 64,
"clearDetectedIn": 0
},
"cache": {
"firstCacheCreatedIn": 64,
"unpaddedOpaqueCreatedIn": 0,
"paddedOpaqueCreatedIn": 64
}
}

Comment 20

[Tom Tung [:tt, :ttung]]

(In reply to joe from comment #19)

I'm sorry about not helping to recover your profile. It's a new profile, so everything should work. :) If you happen to find similar problem and find out that might related to storage initialization by checking the website. Please feel free to ask at the meta-bug [1] or file a new bug there. Thanks!

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1482662