Re: Firefox and the ports tree LOCKED
On Mon, Jul 22, 2013 at 07:56:31AM +0300, Lars Engblom wrote: > 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. You just need to use common sense. - try with a fresh empty profile - try to reset your regular profile (see about:support) - collect backtraces of crashes, open bugs upstream & cc me - gfx issues with pictures are known and have been discussed here, try the various workarounds devised in the archives. (about:config gfx.xrender.enabled, layers.acceleration.enabled, MOZ_DISABLE_IMAGE_OPTIMIZE=1 in the env... see http://marc.info/?l=openbsd-ports&m=136560946723949&w=2) Of course, i'm using firefox all the time on all my computers, and i dont see such OMGSOUNSTABLE behaviour. It crashes with OOM sometimes with heavy javascript, gobbles all cpu when viewing huge images, but besides that it's totally usable. > >>I have been following snapshots the whole time and this problems in FF > >>has been since the spring. Yeah, great timing to come whining... nothing will happen for 5.4. Landry
Re: Firefox and the ports tree LOCKED
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=13003457046&r=1&w=2 Where's the fucking bug report? What were you waiting for?
Re: Firefox and the ports tree LOCKED
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=13003457046&r=1&w=2 Where's the fucking bug report? What were you waiting for?
php-tidy vs tidyReleaseDate
the tidy php extension tries to call tidyReleaseDate to get some
silly version string, but the library symbol doesnt exist for it
to resolve. this points it at tidyVersion instead.
you can reproduce the problem this solves by enabling the tidy
extension and running "php-5.3 -i" or by writing a script that calls
phpinfo(). they should segfault after complaining about a missing
symbol.
the only caveat to this is the meaning of tidyReleaseDate doesnt
map well to what tidyVersion returns now (which is a version number),
but i dont care.
im happy for someone else to commit this at the most appropriate
time.
Index: 5.3/patches/patch-ext_tidy_tidy_c
===
RCS file: /cvs/ports/lang/php/5.3/patches/patch-ext_tidy_tidy_c,v
retrieving revision 1.2
diff -u -p -r1.2 patch-ext_tidy_tidy_c
--- 5.3/patches/patch-ext_tidy_tidy_c 18 Jun 2011 19:49:50 - 1.2
+++ 5.3/patches/patch-ext_tidy_tidy_c 22 Jul 2013 04:32:48 -
@@ -10,3 +10,21 @@ $OpenBSD: patch-ext_tidy_tidy_c,v 1.2 20
#include "buffio.h"
/* compatibility with older versions of libtidy */
+@@ -1095,7 +1095,7 @@
+ {
+ php_info_print_table_start();
+ php_info_print_table_header(2, "Tidy support", "enabled");
+- php_info_print_table_row(2, "libTidy Release", (char
*)tidyReleaseDate());
++ php_info_print_table_row(2, "libTidy Release", (char *)tidyVersion());
+ php_info_print_table_row(2, "Extension Version",
PHP_TIDY_MODULE_VERSION " ($Id$)");
+ php_info_print_table_end();
+
+@@ -1309,7 +1309,7 @@
+ return;
+ }
+
+- RETURN_STRING((char *)tidyReleaseDate(), 1);
++ RETURN_STRING((char *)tidyVersion(), 1);
+ }
+ /* }}} */
+
Firefox and the ports tree LOCKED
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. 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. I have been following snapshots the whole time and this problems in FF has been since the spring. On 07/21/13 23:34, Christian Weisgerber wrote: The ports tree is now LOCKED for the 5.4 release.
Ports tree LOCKED
The ports tree is now LOCKED for the 5.4 release. -- Christian "naddy" Weisgerber na...@mips.inka.de
