For the record, Firefox 61 very much does continue to make use of /proc/NNNN/smaps (and /proc/NNNN/statm) when using the about:memory page.
I confirmed this by experimentally commenting out the AppArmor rules for those two /proc files (motivated by comment #3 above), and subsequently observed AppArmor denials. However, the about:memory page still displayed the memory summary, and no error message came up at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/911540 Title: about:memory displays a weird error due to lacking access to /proc/self/smaps Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Please note, this only affects users when the apparmor profile is enabled. "An error occurred when collecting a multi-reporter's results: [Exception... \"Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMemoryMultiReporter.collectReports]\" nsresult: \"0x80004005 (NS_ERROR_FAILURE)\" location: \"JS frame :: chrome://global/content/aboutMemory.js :: getReportersByProcess :: line 295\" data: no]" The error should go away on Ubuntu after bug 911494 is fixed. Bug 911494 is about apparmor blocking access to /proc/self/smaps. Upstream seems interested in refining this message. This bug is about refining the message rather than making it go away. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/911540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
