BeBits - Firefox Bleeding Edge - Talkback

BeBits

Firefox Bleeding Edge

Talkback

Go back to the Firefox Bleeding Edge page

Post a new Talkback comment!

By s_d - Posted on April 12, 2004 - 13:36:36 (#11948)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Scrolling with on-top windows and too fast blink are laready fixed in Mozilla/Bone build, so will be fixed in netserver version too, when and if normal process of cvs-patching starts again.

Shorcuts is more complicated problem, not technically, but due ideological reasons independent of us.

Wow

By misza - Posted on April 12, 2004 - 13:14:57 (#11947)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I'm certainly very impressed by this build of firefox. It feels a heck of alot faster than the linux version. Well done everyone on the dev team.

I have some suggestions/observations:

The cursor blinks really fast :P

Middle mouse button and drag up/down like in net+ leaves artefacts of the up/down arrow circle thingy.

Scrolling with the wheel and a window on top of firefox (like workspaces or ktv) will leave a bit just scrolled from non-invalidated()/doesn't redraw.

Any change to over-ride the ctrl-tab switcher in BeOS to the one in firefox that switches tabs (ctrl-shift-tab - back a tab, ctrl-tab - forward a tab).

Thanks again for the great work. I'm glad bookmarks work now too :)

By tb100 - Posted on April 12, 2004 - 12:49:57 (#11942)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Jess; if the build still suffers the add-on problem, you can fix it simply by rearranging some of the files in the distribution dirctory.

BGA added a comment below explaining what needs moving.

By tqh - Posted on April 12, 2004 - 08:26:15 (#11934)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

We think we have it figured out. But I never seen the problem myself, so we have some problem verifying if it's gone when we release something.

Netserver builds should probably work under BONE / Zeta, but with suboptimal networking code.

Net_server builds on BONE

By Jess - Posted on April 12, 2004 - 06:09:14 (#11927)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Hey,
I was wondering if you had a Bleeding Edge Bone build for Firefox comming soon. A while ago I saw a new firefox build for net_server so I figured what the hell, let's try it. So I fired it up & hey it worked on BONE. Works pretty good. So I see a new one up today & got it. This net_server build doesn't play so nice on BONE so I had to go back to the last build.

So is the "Bleeding Edge" version safe now or does it still kill the add-on memory subsystem?

Select blocks

By ataoist1@yahoo.com - Posted on April 11, 2004 - 15:57:54 (#11909)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I'm using

Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.7a) Gecko/20040218 Firefox/0.8.0+

This is fast fairly stable but I've seen the same text caret problem as well a few dialog boxes come up were I couldn't check a block.

Keep up the great work. BeOS RULES!

thanks,

ataoist1

More recent build

By tb100 - Posted on April 9, 2004 - 19:02:11 (#11888)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Ah, cursor is the pointer to the mouse. You mean text caret - seems dano/zeta users have some problems with this.

You can get a build of firefox/netserver (although it should also run under BONE, just not as well as native BONE builds) that supposedly doesn't have this problem, and also has fixed transparency (less freeze-prone) here:
http://bezilla.xentronix.com/Static-Firefox.zip

I haven't posted it to this page as it doesn't contain the latest nsImage fixes (so theage will crash, Zenja :)), and it doesn't contain debug symbols so stack crawls will be useless. Works quite nicely for me though.

Cursor flakiness

By tqh - Posted on April 9, 2004 - 13:59:37 (#11884)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

The current Firefox for BONE has none of the recent cursor fixes. So it will be much nicer in next release. Transparency will work much nicer (noticable in the fading in of downloads in Download Manager).

It may take a while though as recent CVS-builds been a bit flaky.

downloads freezing

By tqh - Posted on April 9, 2004 - 13:55:48 (#11883)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Btw it has been reported to me that BONE has some issues at high speed downloads. So most will be fixed with the patch but not everything.

By tb100 - Posted on April 9, 2004 - 13:49:48 (#11882)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

We have a patch under review to prevent the freezing in the download manager; I've been using it here with no freezes for a couple of weeks.

Cursor flakiness seems to partly be due to BeOS - I've seen the same thing happen in BeIDE, BeHappy, GoBe Productive, etc.

Firefox freezing

By Hugh - Posted on April 8, 2004 - 22:17:49 (#11870)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I'm also regularly experiencing this freezing on Zeta RC2 here, and also the download-window has a deadlock-tendency, but I am really impressed by Firefox's speed and the continuing improvement of the BeOS-port! I'm using it as a standard-browser on any OS I get my hands on now..:)

Thanks for the hard work, and looking forward to the patch!

PS: The cursor is still a bit flaky (not always updating)

drag and drop support

By Drake - Posted on March 31, 2004 - 14:33:33 (#11757)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Rearranging the toolbar requires drag and drop support which does not work yet in mozilla/firefox.

navigation toolbar items

By Grijns - Posted on March 31, 2004 - 14:25:20 (#11756)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

ffox works geat and browsing is super. The navigation items work good aswell but i can't seem to add or remove them by dragging items..

Is this me doing something wrong or is this a work in progress part? Anyhow, keep up the good work!

By ljr - Posted on March 27, 2004 - 16:45:53 (#11699)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

it seems...
I'm waiting next release as i dont want to switch back to mozilla! ffox is so lovely ;-)

By tb100 - Posted on March 26, 2004 - 11:45:26 (#11683)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I don't think FireFox has been updated recently.

I think the problem you describe is due to the app-server hitting it's limit for offscreen windows when doing blending (FF's snazzy new download window uses this a lot). We have a fix in progress for this.

By s_d - Posted on March 26, 2004 - 11:26:32 (#11681)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Same style here. It is very rare case when i have less than 20 tabs open.
And yeah, thois is reason why i also think that Opera is the best (though. it was problem somewhere between Opera 4-6 when Ctrl+Shif+Clock worked awfuly).

better but...

By ljr - Posted on March 26, 2004 - 11:03:45 (#11680)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Fifefox seems to break something after some minutes (~20). Maybe it's the addon limit ?
I move the libs and stub in right place but i still got these crashes. I need almost of the time to restart the deskbar.

The problem is FFox windows are freezed, deskbar is unusable (no menu access). I must kill FFox and deskbar to restart surfing..... :-(

my config : Zeta rc2.
This problem does not appear on Bemax with or w/o SMP

any idea ?

Re: wow, much more stable

By zenja - Posted on March 26, 2004 - 01:08:06 (#11676)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

My browsing habit is very stressful for the application in question - I usually open up several tabs, keep jumping between them, keep highlighting and deselecting text, use the mouse wheel heavily, have 4 downloads happening in the background, and usually give the browser hell. For users like myself, thats why we love Opera, because it handless heavy use the best. For browsing single sites one at a time, I'm sure you wont find anything wrong with Mozilla either. But under heavy load, it used to crumple, so I guess the developers are used to treating the browser gently, fine strokes instead of slaps, like walking on broken glass, and not rumpage in like an elephant like the way I browse.

Having said that, the other night Mozilla was finally able to keep up with me without crashing during a 3-4 hour session of heavy use. I think I downloaded quite a bit that night ...

Re: Wow, much more stable

By Kokito - Posted on March 25, 2004 - 17:53:31 (#11669)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

> This is realy realy realy weird that it didn't work for
> you before more than 15 minutes without crash.
>
> Or was it Zeta-only behaviour?

Been using Mozilla in Zeta for months now (RC1 & now RC2), and I haven't seen it crash in a looonng time. I doubt that it is a Zeta specific problem.

JustBe: the place to offer your help is at http://www.livejournal.com/community/bezilla/. Check it out!

Koki

where is the new build?

By justBe - Posted on March 25, 2004 - 14:39:20 (#11666)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

ive checked the comments, it says new build but the links always point to and older build....

where we can get the newer ones?

also i want to help building firefox, i have a good box and time..

you can contact me :)

Re: Wow, much more stable

By s_d - Posted on March 25, 2004 - 12:24:43 (#11663)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

This is realy realy realy weird that it didn't work for you before more than 15 minutes without crash.

Or was it Zeta-only behaviour?

Wow, much more stable

By zenja - Posted on March 25, 2004 - 04:57:41 (#11654)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

For the first time (like, ever), I was able to use Mozilla without crashing for a full session. Until now, it was always flaky, temperamental, and I hardly ever could **use** it for more than 15 minutes without it crashing. Last night, I was surfing and downloading for 3 hours without a hickup. That has got to be some sort of milestone . . .

version 20040218-BONE-BLEEDING_EDGE

By Grijns - Posted on March 24, 2004 - 23:52:55 (#11651)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Thanks for updating this build. it's a great peice of browsing software and am glad it's usable in beos !

There are plenty of better alternatives

By Prognathous - Posted on March 24, 2004 - 13:48:41 (#11630)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Some good suggestions here: http://www.livejournal.com/community/bezilla/23252.html

Prog.

Re: build date info

By s_d - Posted on March 24, 2004 - 13:15:25 (#11628)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Yeah, unfortunately BeBits lacks info about variation update date. And even if you click on "history" - it produces misterious output, with occasionaly choosen versions.

So, maybe it is good idea to post build date manually in variation description.

re: Yup it's the download manager.

By tqh - Posted on March 24, 2004 - 13:07:50 (#11625)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

We think we have found at least one problem with the downloadmanager.

Hopefully Simon and fyysik will get this fixed quite soon.

new releases and build dates

By lichtgestalt - Posted on March 24, 2004 - 09:50:35 (#11621)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I check the BeBits updates daily and am always excited when I see my favorite browser as a new entry in the list. Unfortunately, when opening the download page I don't know what flavour has been updated; Firefox or Mozilla, BONE or net_server. The versions/build dates are all old...
Am I missing something?

Yup it's the download manager.

By Karina - Posted on March 24, 2004 - 09:30:51 (#11620)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Seems to just lock up and freeze up a few apps with it, whilst doing multiple downloads via the download manager.
Just installed Dano on one partition and am using Firefox there at the moment, seems a lot more responsive and so far has been better behaved, I'll let you know if I continue to have these issues here but strangely it seems infinently better.
The other bug that I'm sure you're probably already aware of, is the dialogues for saving passwords and accepting certificates needing to be acknowledged twice. ie. I'm at bebits and enter my login details... it asks if I want to save the login/pass (I say yes and it asks me the same again...) It does the same with certificates. Otherwise great work as always, it's really appreciated, even if we get a few bugs here and there.

Better stability :-)

By zenja - Posted on March 24, 2004 - 09:29:16 (#11619)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Simon, just letting you know that www.theage.com.au no longer crashes Mozilla under Zeta. This is probably the most solid release yet...

Great work everybody

Good work! Very good work!

By Das Jott - Posted on March 23, 2004 - 23:48:32 (#11615)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I feel like someone has to say that actually.
I'm using Mozilla for Bone on Zeta RC2 and I must say I'm really satisfied! The progress you made for the last versions is amazing.
I'm using Mozilla for my whole Email-traffic and sometimes I play around with that funny composer. Because of Mozilla I could entirely get away from Win concernig Internet things :)

Keep up the good work!

Greetings from Germany!!

By tqh - Posted on March 22, 2004 - 13:01:57 (#11578)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

This may very well be the case. It crashes faster the more downloads you got going, which makes it either a synchronization prob or it runs out of threads faster. If I remember correctly it locks the whole system if you don't kill it fast enough, so appserver is probably involved.

By tb100 - Posted on March 22, 2004 - 11:51:25 (#11575)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Do you actually get a crash dialog or does it just freeze?

If it is just a freeze, it may be caused by the app server running out of threads. This seems to happen when doing offscreen blending (FF's dl manager looks fancy enough to use something like that). Take a look with progress controller just before it crashes to see if there's lots of "o::" threads in the app server.

More on the blog.

Re: Crash Happy

By tqh - Posted on March 22, 2004 - 11:43:11 (#11574)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

I assume you are using Firefox and it's the download manager that crashes. It's in a horrible state right now under BeOS (dunno about other platforms, but there are plenty of bugs on it). I havn't had time to look into that since, the cvs has been pretty broken.

Note, I think I'm alone fixing Firefox specific things, so don't expect any miracles.

Crash happy.

By Karina - Posted on March 22, 2004 - 11:32:10 (#11573)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Works well but crashes fairly frequently... ussually when the saving file/s dialogue comes up, when that happens it ussually takes 2 or 3 other applications down with it. Vision seems to be one app that always crashes at the same time. I'm using the BONE build and I have moved the .so files to /lib and the so.stub files to /components.

By tb100 - Posted on March 9, 2004 - 17:56:50 (#11391)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

That is a bit weird. I don't think it's anything firefox specific, maybe just that-build-specific (although I think I d/led the same one to test with and replacing the lib solved it for me).

Hopefully the next firefox release somebody makes will fix the problem for you.

By zenja - Posted on March 9, 2004 - 09:04:55 (#11386)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Simon, it still crashes. What I've tried doing now is downloading a version of Mozilla from the Bezilla blog (not Firefox), build 0205-build7, and the website in question works without any issues. So its definately something specific to Firefox which isn't in the main Mozilla build. Hope that helps.

OK, will try tonight

By zenja - Posted on March 8, 2004 - 22:54:27 (#11378)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Hmm, now that you mention it, I do remember having to move .so files from the /components directory to the /lib directory to get things running, so I placed your .so file in the /lib directory. Will try tonight with replacing it in the /component directory. Other than that website (and the blinking gifs), I cannot find another site which crashes Firefox.

I'll get back to you in 12 hours. Over.

By tb100 - Posted on March 8, 2004 - 09:24:54 (#11369)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

That issue is fixed by the lib I sent you, at least on my machine. Are you sure you replaced the lib correctly? The other option is that you have another copy of the broken libgfx_beos.so somewhere in your search path. Try a search for it, and delete any occurences not in a subdir of the firefox directory - people who copy the libs to home/config/libs/ might be missing out on all the great improvements going on!

If that still doesn't help, then I'm out of ideas. Maybe there's an interdependancy that will be fixed when the next full build with the fixes is released? Seems unlikely, as just replacing that lib on the firefox release here fixes the crash for me.

By zenja - Posted on March 7, 2004 - 23:11:49 (#11365)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Simon, tried the blinking gif link you suppliled, and sure enough, Firefox crashed.

loading symbols
Memory has been clobbered beyond end of allocation (block start 0x813c5378 size 24960)
Alloc call chain (thid 504): 0xec063ad0 0xec04e60b 0xec054bdd 0xeaefe849 0xeaf03912 0xee0155d1 0xee015276 0xed374fa8 0xed375079 0xed3714ef 0xed371407 0xed3729eb 0xee09d5bb 0xee061f9c 0x8000ef72 0x8000f624 0x8000b68e 0x8000b495

_debugger:
_debugger:
+0007 ec0508f3: * c3 retn
firefox:

If it helps, I'm running Zeta RC1-SP2, 512Mb RAM on an XP2400+. I've been viewing theage.com.au from Mozilla/Firefox for over a year, the problem started maybe 6 weeks ago (vague recollection)

By tb100 - Posted on March 7, 2004 - 20:17:41 (#11364)
Current version when comment was posted: 20040218-BONE-BLEEDING_EDGE

Cheers for the tip Bruno,

A change in the startup script that stopped moz starting at all (due to path issues) made me poke around the code a bit - in the part that loads the BeOS .so.stub files, there is a fallback case where it tries to directly load the .so file. I think there should be a stub for every so file, so really we should exit to the debugger with a helpful message if the .stub file can't be found, as it is indicative of a path-related problem.

Simon



	Comment Pages: << prev \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| 7 \| 8 \| 9 \| 10 \| 11 \| 12 \| 13 \| 14 \| 15 \| 16 \| 17 \| 18 \| 19 \| 20 \| 21 \| 22 \| 23 \| 24 \| next >>













			Recent Downloads - # 321 Total Downloads - # 23 Total Views - # 13 User Ratings - # 57




			Web Browsers




			1. BePodder - 9.80 2. QEMU - 9.68 3. ScummVM - 9.57 4. cpu_fix - 9.42 5. Jukebox - 9.40 6. libdl.so - 9.40 7. Haiku AGP busm... - 9.35 8. vim6 - 9.31 9. Beezer - 9.26 10. HandBrake - 9.25




			1. BeOS 5 Perso... - 13,599 2. Realtek RTL8... - 13,114 3. Ati Radeon G... - 12,582 4. Ensoniq Audio... - 7,565 5. ATI Rage 128... - 7,442 6. USB Joystick... - 5,663 7. Broadcom 440x... - 5,411 8. S3 Trio 64 v2... - 4,726 9. USB Serial dr... - 4,707 10. Intel Extreme... - 4,468




			You are not logged in. Login


	Unless otherwise noted, everything is copyright © 1999-2009 Haikuware. All Rights Reserved. For more legal trivia, take a gander at our Legal Stuff page and our Privacy Statement.