Iceweasel randomly crashes in wheezy

eveningsky339 · 03-15-2011, 10:27 AM

I've upgraded from stable to testing. In stable, iceweasel performed flawlessly as I expected. Now it crashes at random times at an alarming rate. It does seem that I can recreate the crash to an extent on youtube, where crashes are the most prevalent.

I haven't located any bug reports regarding this issue with wheezy iceweasel.

andrewthomas · 03-15-2011, 10:33 AM

I am not seeing this, yet I am using the version from experimental.

eveningsky339 · 03-15-2011, 10:37 AM

Running from CLI leaves "segmentation fault" as the only clue after the crash.

TobiSGD · 03-15-2011, 10:39 AM

Run iceweasel from the command line and look for error-messages.

eveningsky339 · 03-16-2011, 03:10 PM

The only error I get in the terminal is

Quote:

segmentation fault

There doesn't appear to be a pre-existing bug report about this. (There is one regarding a seg fault when attempting to access a certain website, but my problem is more generalized)

I checked sid's packages to see if I could just grab a newer version, but it would appear sid and wheezy have the same iceweasel. Maybe I will grab the older one from squeeze.

k3lt01 · 03-16-2011, 03:29 PM

Why don't you report the bug and help Debian and Mozilla fix it?

eveningsky339 · 03-16-2011, 06:23 PM

Quote:

Originally Posted by k3lt01

Why don't you report the bug and help Debian and Mozilla fix it?

I plan on it, but I'm more interested in getting my iceweasel working again first.

jim_p · 03-17-2011, 02:12 AM

Delete your old profile, make a new one, test it and once done, configure it.
This is done by issuing a simple "iceweasel -profilemanager" at a terminal or at your DE's run dialog.

craigevil · 03-18-2011, 02:00 AM

No issues here with the newer Iceweasel 4rc.

$ apt-cache policy iceweasel
iceweasel:
Installed: 4.0~rc1-1
Candidate: 4.0~rc1-1
Version table:
*** 4.0~rc1-1 0
500 http://mozilla.debian.net/ experimental/iceweasel-4.0 i386 Packages
100 /var/lib/dpkg/status
3.5.17-1 0
500 http://mirrors.kernel.org/debian/ unstable/main i386 Packages

eveningsky339 · 03-18-2011, 06:51 AM

I installed Chromium the other day and lo and behold, it randomly crashes as well. Like iceweasel, the only clue the terminal gives me is

Code:

segmentation fault

It would appear the problem lies with another package that these web browsers have in common. I will be filing a bug report shortly, and perhaps limping back to squeeze for a while.

k3lt01 · 03-18-2011, 07:05 PM

What version of Chromium?

I use both (iceweasel 4 and Chromium 9) and have not had the difficulty you are describing.

eveningsky339 · 03-18-2011, 07:52 PM

Chromium 6.0.472.63~r59945-5
Iceweasel 3.5.17-1

k3lt01 · 03-18-2011, 08:09 PM

I realise your in Testing (Wheezy) but Squeeze has had a security update recently that may help to fix the issue.

craigevil · 03-19-2011, 01:06 AM

I installed Squeeze, upgraded to Wheezy then upgraded to sid, no issues with Iceweasel, Firefox, Chrome 10.0.648.82 beta, Opera 11.10.2048, midori 0.3.3-0.1,uzbl 0.0.0~git.20110314-1.

Try installing iceweasel-dbg - debugging symbols for iceweasel, then running Iceweasel from a terminal.

StriDer999999999 · 03-30-2011, 06:13 PM

Same random crashes, after an update lately, but I can't figure which package has done it. Crashes also with gmail, which is really annoying. Konqueror runs well, but gmail is in simple-html mode.
Running Wheezy, Iceweasel 3.5.17-1. System up-to-date.
running iceweasel with debugging symbols (iceweasel -g --sync) I get

Code:

Starting program: /usr/lib/iceweasel/firefox-bin --sync
[Thread debugging using libthread_db enabled]
[New Thread 0xb5affb70 (LWP 10045)]
[New Thread 0xb52f7b70 (LWP 10046)]
[New Thread 0xb47ffb70 (LWP 10047)]
[New Thread 0xb3dffb70 (LWP 10051)]
[New Thread 0xb32ffb70 (LWP 10052)]
[New Thread 0xb2afeb70 (LWP 10053)]
[Thread 0xb32ffb70 (LWP 10052) exited]
[Thread 0xb2afeb70 (LWP 10053) exited]
[New Thread 0xb22fdb70 (LWP 10054)]
[New Thread 0xb1afcb70 (LWP 10055)]
[Thread 0xb1afcb70 (LWP 10055) exited]
[Thread 0xb22fdb70 (LWP 10054) exited]
[New Thread 0xb1afcb70 (LWP 10057)]
[New Thread 0xb22fdb70 (LWP 10058)]
[New Thread 0xb32ffb70 (LWP 10059)]
[Thread 0xb22fdb70 (LWP 10058) exited]
[Thread 0xb32ffb70 (LWP 10059) exited]
[New Thread 0xb22fdb70 (LWP 10060)]
[New Thread 0xb32ffb70 (LWP 10061)]
[New Thread 0xb2afeb70 (LWP 10062)]
[New Thread 0xa9abbb70 (LWP 10063)]
[Thread 0xb22fdb70 (LWP 10060) exited]
[New Thread 0xb22fdb70 (LWP 10065)]
[New Thread 0xa90ffb70 (LWP 10066)]
[Thread 0xa90ffb70 (LWP 10066) exited]
[New Thread 0xa90ffb70 (LWP 10068)]
[Thread 0xb3dffb70 (LWP 10051) exited]
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 66481 error_code 1 request_code 139 minor_code 39)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0xb22fdb70 (LWP 10065) exited]
[Thread 0xa9abbb70 (LWP 10063) exited]
[Thread 0xb2afeb70 (LWP 10062) exited]
[Thread 0xb32ffb70 (LWP 10061) exited]
[Thread 0xb1afcb70 (LWP 10057) exited]
[Thread 0xb47ffb70 (LWP 10047) exited]
[Thread 0xb52f7b70 (LWP 10046) exited]
[Thread 0xb5affb70 (LWP 10045) exited]
[Thread 0xa90ffb70 (LWP 10068) exited]

Program exited with code 01.

Did anyone manage to fix it?