I have several times seen reports about FF crashing. It might have been
here or then on #openbsd (I am not sure where). I thought this is
something everybody knows. I made a misjudgement because I did not want
to send a bug-report for something I thought everybody knew already.
What I sent to the list today was not a bug report either, I was more
raising the concern that the maintainer might need more time to get it
stable even though the tree is in lock and no big changes should be allowed.
This problem might be related to drivers also. My laptop at home is
using i915, which has seen quite a bit of development during the latest
cycle. I am using amd64 snapshots. The pictures often get horizontal
stripes. HTML5 videos often crashes it completely, so also a bit more
intensive java scripts.
I can manage with Chromium, as it is not crashing. The problem is not
that big deal for me (although it is annoying). I am more concerned
about the reputation my favorite OS gets if FF gets released in this shape.
I am not a good C programmer (my code can be dangerous) and I am unable
of debugging C, but I am willing to do by instruction what anyone wants
me to do in order to help in this case.
On 07/22/13 07:41, Brian Callahan wrote:
On 7/22/2013 12:27 AM, Lars Engblom wrote:
Something seriously needs to be done to Firefox before 5.4 release. It
has been really buggy the latest months. It is almost completely
unusable. It dumps core daily for me. Pictures are often distorted.
Stellar bug report.
Like it is now, if anyone new to OpenBSD would try it, they would never
return as they would consider it as a way to buggy system (especially as
the ports do not even get upgrades for 6 months if you follow the
stable). I hope whoever works on Firefox will be allowed to do whatever
he/she needs to do in order to get a stable version.
Really? I use Firefox everyday on -current and don't run into problems.
I have been following snapshots the whole time and this problems in FF
has been since the spring.
And you waited until now to complain about it? Where's your email when
you first ran into problems? Here's MARC's list of all the emails
you've sent under this email address:
http://marc.info/?a=130034570400006&r=1&w=2
Where's the fucking bug report? What were you waiting for?
