Bug#567415: iceweasel won't restart after it crashes

[Gary Dale]

Mike Hommey wrote:
> On Fri, Jan 29, 2010 at 12:27:26PM -0500, Gary Dale wrote:
>   
>> Mike Hommey wrote:
>>     
>>> On Fri, Jan 29, 2010 at 11:49:11AM -0500, Gary Dale wrote:
>>>       
>>>> Mike Hommey wrote:
>>>>         
>>>>> On Fri, Jan 29, 2010 at 09:50:13AM -0500, Gary Dale wrote:
>>>>>           
>>>>>> Mike Hommey wrote:
>>>>>>             
>>>>>>> On Thu, Jan 28, 2010 at 05:55:32PM -0500, Gary Dale wrote:
>>>>>>>               
>>>>>>>> Package: iceweasel
>>>>>>>> Version: 3.5.6-1
>>>>>>>> Severity: important
>>>>>>>>
>>>>>>>> After Iceweasel crashes it refuses to restart - even in safe-mode -
>>>>>>>> until I reboot the computer. Simply logging out and back in again
>>>>>>>> doesn't clear the problem.
>>>>>>>>                 
>>>>>>> Does it say something when it refuses to restart ?
>>>>>>>
>>>>>>> Isn't there a firefox-bin process still running ?
>>>>>>>
>>>>>>> Mike
>>>>>>>
>>>>>>>               
>>>>>> No. It just doesn't restart. There is no firefox-bin process
>>>>>> running. However syslog shows:
>>>>>>
>>>>>> 2010-01-29 09:49:16    transponder    kernel    [151666.119720]
>>>>>> firefox-bin[17244]: segfault at 0 ip (null) sp 00007fff546d4348
>>>>>> error 14 in xulrunner-stub[400000+15000]
>>>>>>             
>>>>> Is there a ~/.mozilla/firefox/*/lock file ? What happens if you remove
>>>>> it ?
>>>>>
>>>>> Mike
>>>>>
>>>>>           
>>>> Removing it doesn't help. That was the first thing I tried.
>>>>         
>>> Can you send the output for strace -f -o /some/file iceweasel ?
>>> (located, obviously, in /some/file, and, still obviously, when it fails,
>>> only)
>>>
>>> Cheers,
>>>
>>> Mike
>>>
>>>       
>> See attached:
>> 19206 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>> 19206 +++ killed by SIGSEGV +++
>>     
>
>
> Oh, segmentation fault.
> Can you follow the instructions in /usr/share/bug/iceweasel/presubj to
> get a backtrace ?
>
> Thanks
>
> Mike
>
>   
Interesting. It doesn't crash when I run it with the -g option. However, 
even after a normal shutdown from the -g mode, it still won't restart.