unkillable firefox

[Steve Kargl]

On Tue, Dec 20, 2016 at 05:28:09PM -0600, Eric Badger wrote:
> On 12/20/2016 15:29, Steve Kargl wrote:
> > Anyone know how to kill firefox?
> > 
> > 
> >   PID USERNAME   PRI NICE SIZE    RES STATE   C   TIME    WCPU COMMAND
> > 63902 kargl      40   0  3157M  2302M STOP    1  10:50   0.00% firefox{firefox}
> > 63902 kargl     -16   0  3157M  2302M STOP    2   5:46   0.00% firefox{Composit
> > 16874 kargl      40   0   740M   330M STOP    1   0:07   0.00% firefox{firefox}
> > 16874 kargl     -16   0   740M   330M STOP    1   0:00   0.00% firefox{Composit
> > 
> > It seems that firefox is wedged in the thread firefox{Compositor},
> > and slowly eating up memory.  This is on an amd64 system at
> > r310125 and latest firefox from ports.  procstat suggests that its
> > stuck in a vm sleep queue.
> > 
> > % procstat -k 63902
> >   PID    TID COMM       TDNAME       KSTACK                       
> > 63902 100504 firefox    -            mi_switch thread_suspend_switch
> >                                      thread_single exit1 sigexit postsig ast
> >                                      Xfast_syscall 
> > 63902 101494 firefox    Compositor   mi_switch sleepq_wait _sleep 
> >                                      vm_page_busy_sleep vm_page_sleep_if_busy
> >                                      vm_fault_hold vm_fault trap_pfault trap
> >                                      calltrap 
> > 
> 
> Do you have output of procstat -k for all threads? I'd guess one thread
> is busy dumping core.
> 

Those are the only threads.  'killall firefox' reaped all the
other threads.  I've tried attaching lldb and gdb712 to the
process, but neither made it to a prompt.

I would switch to www/chromium, but she appears to be broken, now.

-- 
Steve