Advertisement
Guest User

Mozilla Nightly/ Firefox crashing feedback

a guest
May 14th, 2019
131
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.74 KB | None | 0 0
  1. For MANY months now- probably at least the entirety of 2019 so far (four and a half months) my Nightly has been freezing after being open for a while. It produces the error window:
  2.  
  3.  
  4. "Warning: Unresponsive script
  5.  
  6. A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
  7.  
  8. Script: chrome://global/content/elements/browser-custom-element.js:448
  9.  
  10. [checkbox] Don't ask me again
  11.  
  12. [Continue] [Debug script] [Stop script]"
  13.  
  14.  
  15. The script it shows changes every time. The other screenshots I took of it say:
  16.  
  17. "Script: chrome://global/content/customElements.js:223"
  18.  
  19. Script: chrome://global/content/bindings/scrollbox.xml:291"
  20.  
  21.  
  22. On May 4 (10 days ago) Nightly actually FAILED TO LOAD ENTIRELY! It just produced a blank window saying:
  23.  
  24. "XML Parsing Error:
  25. Location: chrome://browser/content/browser.xul
  26. Line Number 31, Column 1:
  27.  
  28. %browserDTD;
  29. ^"
  30.  
  31. When this happened I just used Firefox for the next day until I assumed Nightly updated, at which point I installed that update manually, but the habitual freezing-after-staying-open-for-a-while still happened every time.
  32.  
  33. I assume the only reason this happens is because I disabled every button on the menu bar except "Help" via the use of the following script:
  34.  
  35. "#file-menu,#edit-menu,#view-menu,#history-menu,#bookmarksMenu,#tools-menu {
  36. display: none !important;
  37. }
  38.  
  39. #helpMenu"
  40.  
  41. To use the script I followed these instructions (I'm paraphrasing them):
  42. 1. Enter "about:support" (without quotes) in the URL bar
  43. 2. Ctrl + F "Open Folder" then click it
  44. 3. Create new folder called "chrome" (lowercase, no quotes)
  45.  
  46. And after that the guy gave me a file to put in there named "userChrome.css". But he only included a way to get rid of the "bookmarks" button from the menu bar (since that was my question, since it was freezing my browser for minutes every time I accidentally hovered over it.) So someone else taught me how to disable the other buttons if I wanted:
  47.  
  48. I'll just quote the second guy's instructions verbatim since I'm too lazy to paraphrase:
  49.  
  50. 1. f12
  51. 2. settings
  52. 3. tick last two boxes on the bottom right
  53. 4. dev tools/ ctrl-alt-shift-i
  54. 5. inspect/ styles
  55. 6. inspector/ click the arrow to select what you want to hide
  56. 7. style/ select userChrome.css
  57. 8. put that id there
  58. 9. click save changes
  59.  
  60. I was really not even sure how to find these instructions and all that, so I was just hoping it would just stop eventually. But it never did, for months. It was horrible. I was hoping by my bothering to submit everything I know that you guys could fix it.
  61.  
  62. Also, random other thing, like 2/3 years ago now Firefox used to have tab "favicons" when you opened an offline image in a tab (for example, "file:///C:/Users/user/Desktop/apple.png" in the URL bar). I really hated how these tab favicons behaved. There was no stansard for loading them at a 100% rate; instead it failed to load if an image was larger than like 1200x1200 pixels in res, but it would load sometimes if you didn't return to the tab for a while, then refreshed, as if to catch it off-guard when the browser didn't decide it won't try loading its tab favicon. It was truly horrible. But one day you guys just removed the feature altogether instead of fixing it to load tab favicons at a 100% rate. I complained about it so many times across the years... then I just eventually stopped... but I still mention it whenever I complain in this way anyway... I know I'm the only person in the world who could ever care about this in the history of time... I didn't even realize at first the proper terminology was "favicon"... but won't you at least add back the feature when it pretty much sucked, rather than just remove it for years and years only hurting me...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement