[Ubuntu Wiki] Update of "MozillaTeam/Bugs" by chrisccoulson

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=68&rev2=69

  If this works and the particular executable is from a software package in the Ubuntu archive, then we may consider adding an exception to the Apparmor profile. In this case, please report a bug using Apport. If the executable is from 3rd party software outside of the Ubuntu archive, then you will need to either keep the Apparmor profile disabled, or add an exception locally in /etc/apparmor.d/local/usr.bin.firefox.
  
  See [[https://help.ubuntu.com/community/AppArmor|AppArmor]]
+ 
+ == Check the Error Console ==
+ 
+ Some bugs may result in unhandled JS exceptions or other error messages being logged to the error console, and these may provide a strong clue as to the cause of a bug. To view these, open the error console from "Tools -> Web Developer -> Error Console", and select "Errors".
+ 
+ Note, you many need to enable the menuitem to access the error console. To do this, open "about:config", and set "devtools.errorconsole.enabled" to "true"
+ 
+ == For problems with memory usage ==
+ 
+ If you are reporting a bug about excessive memory usage, please copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport.
+ 
+ In the future, we hope to automate this step.
+ 
+ Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]]
+ 
  == Specific issues ==
  
  === XML errors and broken UI after upgrade ===