Date: Sun, 24 Jul 2016 07:46:47 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 211233] www/firefox: frequent crashes Message-ID: <bug-211233-21738-2D1NSbxGOB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211233-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-211233-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211233 Martin Birgmeier <la5lbtyi@aon.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |New Resolution|Overcome By Events |--- --- Comment #9 from Martin Birgmeier <la5lbtyi@aon.at> --- Some more analysis... A new tab shows the top sites in a 5x3 preview grid. It seems that if for at least one site a preview is not available, a plugin-container process is be= ing spawned which then crashes. The plugin-container is started as follows: /usr/local/lib/firefox/plugin-container -greomni /usr/local/lib/firefox/omn= i.ja -appomni /usr/local/lib/firefox/browser/omni.ja -appdir /usr/local/lib/firefox/browser 3188 tab 3188 is the PID of the firefox main process. Whenever such a plugin-container is killed, the following lines are added to .xsession-errors: (process:12117): GLib-CRITICAL **: g_path_get_basename: assertion 'file_nam= e !=3D NULL' failed ###!!! [Parent][MessageChannel] Error: (msgtype=3D0x2C0076,name=3DPBrowser::Msg_Destroy) Channel error: cannot sen= d/recv So most likely the two processes - firefox and plugin-container - exchange = some information, with the plugin-container ultimately running out of memory and crashing. More info: plugin-container works fine for icedtea-web - I can start Java plugins without a problem. -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211233-21738-2D1NSbxGOB>