canonical-partner-dev team mailing list archive

[daniel CURTIS <1656065@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  Hello.
  
- Today, after a couple of hours of using Firefox (mostly YouTube and
+ Yesterday, after a couple of hours of using Firefox (mostly YouTube and
  other websites), web browser unexpectedly had been closed. Next, a
  dialog box related to the Mozilla Crash Reporter appeared - which
  contained a message, that reporter is disabled (which I did earlier via
  'about:config' and *datareporting.healthreport.service.enabled* key set
  to _false_) and no crash report is available even via 'about:crashes'
- etc. By the way: today an update was available for flash-plugin [see:
- 1].
+ etc. By the way: yesterday an update for flash-plugin was also available
+ (see: 1).
  
  Anyway, 'LastCrash' file (which can be found in ~/.mozilla/firefox/Crash
  Reports/ directory) contains only: 1484142985. Just like all the others
  files in this directory. There are also two folders called: 'events' and
  'pending'. These directories are completely empty. However, system log
  files, such as '/var/log/kern.log' or '/var/log/syslog', contains an
- interesting entries:
+ interesting entries. An example:
  
  ---[ /var/log/kern.log:
  
  Jan 11 14:56:25 t4 kernel: [ 4161.540727] Chrome_ChildThr[2890]:
  segfault at 0 ip b76df673 sp b1efe9f0 error 6 in plugin-
  container[b76d8000+42000]
  
- There is also an AppArmor entry logged, but I don't know if it is
- related with plugin-container segfault. As we know, thanks to the
- plugin-container, plugins are separated from the browser process, making
- it more stable so now if a plugin crashes, Firefox should remains
- unharmed, right? It looks like, that this is a known problem [see: 2, 3,
- 4]. Anyway, here is some informations about versions:
+ There is also an AppArmor entry logged (concerning Firefox), but I don't
+ know if it is related with plugin-container segfault. As we know, thanks
+ to the plugin-container, plugins are separated from the browser process,
+ making it more stable, right? So now if a plugin crashes, Firefox should
+ remains unharmed. It looks like this is a known problem (see: 2, 3).
+ Anyway, here is some informations about versions:
  
  ● Firefox: 50.1.0
- ● Flash: 24.0.0.194ubuntu0.12.04.1 
+ ● Flash: 24.0.0.194ubuntu0.12.04.1
  ● Release: 12.04.5 LTS (via `lsb_release -a` command)
- ● Linux: 3.2.0-120-generic-pae (3.2.79) i686 
+ ● Linux: 3.2.0-120-generic-pae (3.2.79) i686
  
- Best regards. 
+ Best regards.
  _____________
- [1] https://lists.ubuntu.com/archives/precise-changes/2017-January/026047.html 
- [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199 
- [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199 
- [4] https://bugzilla.redhat.com/show_bug.cgi?id=1253086
+ [1] https://lists.ubuntu.com/archives/precise-changes/2017-January/026047.html
+ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199
+ [3] https://bugzilla.redhat.com/show_bug.cgi?id=1253086

-- 
You received this bug notification because you are a member of Canonical
Partner Developers, which is subscribed to adobe-flashplugin in Ubuntu.
https://bugs.launchpad.net/bugs/1656065

Title:
  plugin-container (Chrome_ChildThr): segfault at 0 ip b76df673 sp
  b1efe9f0 error 6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1656065/+subscriptions