Re: The Dilbert Problem...
On Wed, Mar 05, 2008 at 04:25:08PM +0100, ropers wrote: snip NB: As for the number of open tabs, Firefox 2.0.0.x is a real sieve when it comes to memory. It leaks and leaks and leaks... The upcoming Firefox 3 is reportedly going to be a major step forward, but I haven't tried it yet. The desktop machine I'm currently using runs Ubuntu, so this may or may not be directly comparable, but in my experience Firefox 2.0.0.x **can** still be used with 20 tabs spread over 6 windows -- IFF you throw truckloads of RAM at it (e.g. 1-2GB), and use a very comprehensive ABP filter list, and pkill firefox and restartrestore it at least once a day (Firefox 2 allegedly doesn't free memory when tabs are closed). wow. Firefox 2.0.0.12 running on OpenBSD 4.3beta from 29 Feb on a Powerbook G3 with a whopping 256meg of memory and a blinding fast 333mhz G3 happily opens 17 tabs (my default startup) and is quite usable. For the first 30 secs or so Firefox isn't usable. When done it's sucked 125meg and taken 3 mins of CPU. After about 30 of those cpu seconds you can easily swap from tab to tab. OpenBSD 4.2 with what ever Firefox shipped in ports (2.0.0.6 maybe) basically felt like it worked the same. Is the PPC that much more efficient? :-) cheers bruce
Re: The Dilbert Problem...
On 06/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Wed, Mar 05, 2008 at 04:25:08PM +0100, ropers wrote: snip NB: As for the number of open tabs, Firefox 2.0.0.x is a real sieve when it comes to memory. It leaks and leaks and leaks... The upcoming Firefox 3 is reportedly going to be a major step forward, but I haven't tried it yet. The desktop machine I'm currently using runs Ubuntu, so this may or may not be directly comparable, but in my experience Firefox 2.0.0.x **can** still be used with 20 tabs spread over 6 windows -- IFF you throw truckloads of RAM at it (e.g. 1-2GB), and use a very comprehensive ABP filter list, and pkill firefox and restartrestore it at least once a day (Firefox 2 allegedly doesn't free memory when tabs are closed). wow. Firefox 2.0.0.12 running on OpenBSD 4.3beta from 29 Feb on a Powerbook G3 with a whopping 256meg of memory and a blinding fast 333mhz G3 happily opens 17 tabs (my default startup) and is quite usable. For the first 30 secs or so Firefox isn't usable. When done it's sucked 125meg and taken 3 mins of CPU. After about 30 of those cpu seconds you can easily swap from tab to tab. OpenBSD 4.2 with what ever Firefox shipped in ports (2.0.0.6 maybe) basically felt like it worked the same. Is the PPC that much more efficient? :-) I haven't really done any rigorous testing, and I probably don't really need 1-2 GB for 20-30 tabs, but the above is what I currently use. ((I don't really care, because I plan on wiping this PC soon anyway, and I hope I'll be able to again use OpenBSD more.)) That said, my hunch is, PowerPC vs. x86 prolly hasn't much to do with it. IMHO (a) Ubuntu is MUCH less hardware-efficient than OpenBSD, and (b) I take it from your post that you're probably not using Flash -- I think heavy Flash in multiple tabs (even though eg. videos are not running concurrently) is probably the main culprit. In a nutshell: Flash. The FASTEST way to send **all** of your clock cycles to /dev/null.(TM) (Yeah. That's about it. That, and incompetently written s-sss-zzzloowww ECMAScript that uses polling and shit **cough** Digg **cough**.) To be honest, a further discussion of the performance issues seen with Ubuntu/Flash/bad JavaScript is off-topic for an OpenBSD mailing list. Feel free to email me off-list though. :) I might even get around to answering. ;-) Cheers, --ropers
Re: The Dilbert Problem...
On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: Hi, There's a strange incident that's repeatable on my system (4.2). Open up Firefox, make it load www.dilbert.com, then open another tab and visit any other website, then do the same for 2~3 more tabs. The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... Is it a Firefox problem or something to do with the system? Best, ~Mayuresh I have seen this on both Windows and OpenBSD. The later firefox releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems with having more tabs open. I used to have a lot of tabs but now I have restricted myself to 3-4 or firefox is not useable. BR Dunceor
Re: The Dilbert Problem...
On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: Hi, There's a strange incident that's repeatable on my system (4.2). Open up Firefox, make it load www.dilbert.com, then open another tab and visit any other website, then do the same for 2~3 more tabs. The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... Is it a Firefox problem or something to do with the system? Best, ~Mayuresh I have seen this on both Windows and OpenBSD. The later firefox releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems with having more tabs open. I used to have a lot of tabs but now I have restricted myself to 3-4 or firefox is not useable. I forgot to mention, my Firefox version is 2.0.0.6 Also I've only got a total of 3~4 tabs open while performing the Dilbert test. Taking your cue, I tried an experiment, I opened up 10 tabs, but without the Dilbert site and all of them opened up in parallel.
Re: The Dilbert Problem...
Mayuresh Kathe [EMAIL PROTECTED] writes: The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... another data point - here the dilbert site loads very slowly in a firefox with about 15 tabs open already (lots of graphics it seems) but other sites opened after it in separate tabs load normally. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: The Dilbert Problem...
On Wed, Mar 5, 2008 at 1:18 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: Hi, There's a strange incident that's repeatable on my system (4.2). Open up Firefox, make it load www.dilbert.com, then open another tab and visit any other website, then do the same for 2~3 more tabs. The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... Is it a Firefox problem or something to do with the system? Best, ~Mayuresh I have seen this on both Windows and OpenBSD. The later firefox releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems with having more tabs open. I used to have a lot of tabs but now I have restricted myself to 3-4 or firefox is not useable. I forgot to mention, my Firefox version is 2.0.0.6 Also I've only got a total of 3~4 tabs open while performing the Dilbert test. Taking your cue, I tried an experiment, I opened up 10 tabs, but without the Dilbert site and all of them opened up in parallel. Seems like an ipv6-dns-resolution problem to me. My 2c.
Re: The Dilbert Problem...
Op Wed, 05 Mar 2008 13:42:48 +0100 schreef Peter N. M. Hansteen [EMAIL PROTECTED]: Mayuresh Kathe [EMAIL PROTECTED] writes: The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... another data point - here the dilbert site loads very slowly in a firefox with about 15 tabs open already (lots of graphics it seems) but other sites opened after it in separate tabs load normally. The delay is most likely caused by the DNS requests for all the different advert sites. My guess is that Firefox handles the DNS requests in order, using the same execution context for all tabs, waiting for each one before proceeding to the next. Requesting an record that does not exist (or trying to connect to the first four bytes of an IPv6-address) might very well cause an additional slowdown. -- Boudewijn Dijkstra Indes - IDS B.V. +31 345 545 535
Re: The Dilbert Problem...
Mayuresh Kathe dixit (2008-03-05, 13:10:45): Hi, There's a strange incident that's repeatable on my system (4.2). Open up Firefox, make it load www.dilbert.com, then open another tab and visit any other website, then do the same for 2~3 more tabs. The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... Is it a Firefox problem or something to do with the system? What you describe migth be actually a DNS related problem. If dilbert.com doesn't resolve well using your current NS/resolver library combination, some applications might wait to receive an answer or a time out for the previous queried addresses before processing the next request(s). This behaviour can be avoided using a asynchronous resolver implementation - in this case the application wouldn't wait for a reply before performing the next queries. AFAIK the OpenBSD resolver library is not asynchronous, someone please correct me if I'm wrong here. However, if you can reproduce the behaviour using another browser, Opera comes to mind, then you can exclude Firefox from your list of suspects and the next step would be changing the NS you are using at this moment. -- Digitally yours, Florin Iamandi (Slippery) Reason is the first victim of emotion. -- Scytale, Dune Messiah [demime 1.01d removed an attachment of type application/pgp-signature]
Re: The Dilbert Problem...
On Wed, Mar 05, 2008 at 01:47:23PM +0100, Landry Breuil wrote: On Wed, Mar 5, 2008 at 1:18 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: Hi, There's a strange incident that's repeatable on my system (4.2). Open up Firefox, make it load www.dilbert.com, then open another tab and visit any other website, then do the same for 2~3 more tabs. The first (dilbert) tab takes a long time to load during which the other tabs too show nothing, they get stuck at Looking up... Is it a Firefox problem or something to do with the system? Best, ~Mayuresh I have seen this on both Windows and OpenBSD. The later firefox releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems with having more tabs open. I used to have a lot of tabs but now I have restricted myself to 3-4 or firefox is not useable. I forgot to mention, my Firefox version is 2.0.0.6 Also I've only got a total of 3~4 tabs open while performing the Dilbert test. Taking your cue, I tried an experiment, I opened up 10 tabs, but without the Dilbert site and all of them opened up in parallel. Seems like an ipv6-dns-resolution problem to me. My 2c. If that's the case, setting network.dns.disableIPv6 to true in about:config should do the trick. -Otto
Re: The Dilbert Problem...
On Wed, Mar 05, 2008 at 01:47:23PM +0100, Landry Breuil wrote: | On Wed, Mar 5, 2008 at 1:18 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: | | On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor | [EMAIL PROTECTED] wrote: | |On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe | [EMAIL PROTECTED] wrote: | Hi, | | There's a strange incident that's repeatable on my system (4.2). | | Open up Firefox, make it load www.dilbert.com, then open another tab | and visit any other website, then do the same for 2~3 more tabs. | | The first (dilbert) tab takes a long time to load during which the | other tabs too show nothing, they get stuck at Looking up... | | Is it a Firefox problem or something to do with the system? | | Best, | | ~Mayuresh | | | | I have seen this on both Windows and OpenBSD. The later firefox | releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems | with having more tabs open. | I used to have a lot of tabs but now I have restricted myself to 3-4 | or firefox is not useable. | | I forgot to mention, my Firefox version is 2.0.0.6 | Also I've only got a total of 3~4 tabs open while performing the Dilbert test. | Taking your cue, I tried an experiment, I opened up 10 tabs, but | without the Dilbert site and all of them opened up in parallel. | | Seems like an ipv6-dns-resolution problem to me. A bit of background here : Firefox can do lookups (for IPv6 addresses) by default for websites you visit. Some DNS servers don't like this sort of query and, in stead of saying hey, I dont understand what you want, they ignore you in the hope that you go away. Things time out on your end, your system will do a A lookup and from there you can continue browsing the website. In the case of the dilbert site, this doesn't seem to be the case. Apparantly, one of the NS'en is not responding to queries at all (nor ICMP Echo Requests - it's probably down or disconnected from the net temporarily). Your caching NS may be trying to contact this one nameserver. It'll wait for the timeout and then try one of the other NS'en. The problem is exacerbated by the fact that www.dilbert.com has a TTL of 300 seconds, so your caching NS doesn't keep this record in memory too long. The problem is that the resolver in OpenBSD isn't reentrant. If it's doing nameresolution, it'll not do another one in parallel. So while you wait for www.dilbert.com to get resolved (which takes long because of this timeout), you open a new tab, enter an address and your machine will have to resolve that too, which gets queued up (doesn't get handled in parallel), so the other tab also waits on www.dilbert.com to get resolved. You can test this hypothesis by going to a website by its IP address. Try visiting http://129.128.5.191/ (http://www.openbsd.org/) while you're waiting for www.dilbert.com to load. Visiting by IP should work (as it doesn't require a DNS lookup). Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Re: The Dilbert Problem...
On Wed, Mar 5, 2008 at 6:50 PM, Paul de Weerd [EMAIL PROTECTED] wrote: On Wed, Mar 05, 2008 at 01:47:23PM +0100, Landry Breuil wrote: | On Wed, Mar 5, 2008 at 1:18 PM, Mayuresh Kathe [EMAIL PROTECTED] wrote: | | On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor | [EMAIL PROTECTED] wrote: | |On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe | [EMAIL PROTECTED] wrote: | Hi, | | There's a strange incident that's repeatable on my system (4.2). | | Open up Firefox, make it load www.dilbert.com, then open another tab | and visit any other website, then do the same for 2~3 more tabs. | | The first (dilbert) tab takes a long time to load during which the | other tabs too show nothing, they get stuck at Looking up... | | Is it a Firefox problem or something to do with the system? | | Best, | | ~Mayuresh | | | | I have seen this on both Windows and OpenBSD. The later firefox | releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems | with having more tabs open. | I used to have a lot of tabs but now I have restricted myself to 3-4 | or firefox is not useable. | | I forgot to mention, my Firefox version is 2.0.0.6 | Also I've only got a total of 3~4 tabs open while performing the Dilbert test. | Taking your cue, I tried an experiment, I opened up 10 tabs, but | without the Dilbert site and all of them opened up in parallel. | | Seems like an ipv6-dns-resolution problem to me. A bit of background here : Firefox can do lookups (for IPv6 addresses) by default for websites you visit. Some DNS servers don't like this sort of query and, in stead of saying hey, I dont understand what you want, they ignore you in the hope that you go away. Things time out on your end, your system will do a A lookup and from there you can continue browsing the website. In the case of the dilbert site, this doesn't seem to be the case. Apparantly, one of the NS'en is not responding to queries at all (nor ICMP Echo Requests - it's probably down or disconnected from the net temporarily). Your caching NS may be trying to contact this one nameserver. It'll wait for the timeout and then try one of the other NS'en. The problem is exacerbated by the fact that www.dilbert.com has a TTL of 300 seconds, so your caching NS doesn't keep this record in memory too long. The problem is that the resolver in OpenBSD isn't reentrant. If it's doing nameresolution, it'll not do another one in parallel. So while you wait for www.dilbert.com to get resolved (which takes long because of this timeout), you open a new tab, enter an address and your machine will have to resolve that too, which gets queued up (doesn't get handled in parallel), so the other tab also waits on www.dilbert.com to get resolved. You can test this hypothesis by going to a website by its IP address. Try visiting http://129.128.5.191/ (http://www.openbsd.org/) while you're waiting for www.dilbert.com to load. Visiting by IP should work (as it doesn't require a DNS lookup). Paul, I tried your idea of starting up www.dilbert.com and then visiting http://129.128.5.191/ (the openbsd website). It worked as you'd predicted. So I guess its the problem with the OpenBSD resolver.
Re: The Dilbert Problem...
|On Wed, Mar 5, 2008 at 12:59 PM, Mayuresh Kathe wrote: | | Hi, | | There's a strange incident that's repeatable on my system (4.2). | | Open up Firefox, make it load www.dilbert.com, then open another tab | and visit any other website, then do the same for 2~3 more tabs. | | The first (dilbert) tab takes a long time to load during which the | other tabs too show nothing, they get stuck at Looking up... | | Is it a Firefox problem or something to do with the system? | On Wed, Mar 5, 2008 at 5:46 PM, Karl Sjodahl - dunceor wrote: | | I have seen this on both Windows and OpenBSD. The later firefox | releases (like from 2.0.0.3-2.0.0.5 something) I have seen problems | with having more tabs open. | I used to have a lot of tabs but now I have restricted myself to 3-4 | or firefox is not useable. | On Wed, Mar 5, 2008 at 1:18 PM, Mayuresh Kathe wrote: | | I forgot to mention, my Firefox version is 2.0.0.6 | Also I've only got a total of 3~4 tabs open while performing the Dilbert test. | Taking your cue, I tried an experiment, I opened up 10 tabs, but | without the Dilbert site and all of them opened up in parallel. On Wed, Mar 05, 2008 at 01:47:23PM +0100, Landry Breuil wrote: | | Seems like an ipv6-dns-resolution problem to me. On Wed, Mar 5, 2008 at 6:50 PM, Paul de Weerd [EMAIL PROTECTED] wrote: A bit of background here : Firefox can do lookups (for IPv6 addresses) by default for websites you visit. Some DNS servers don't like this sort of query and, in stead of saying hey, I dont understand what you want, they ignore you in the hope that you go away. Things time out on your end, your system will do a A lookup and from there you can continue browsing the website. In the case of the dilbert site, this doesn't seem to be the case. Apparantly, one of the NS'en is not responding to queries at all (nor ICMP Echo Requests - it's probably down or disconnected from the net temporarily). Your caching NS may be trying to contact this one nameserver. It'll wait for the timeout and then try one of the other NS'en. The problem is exacerbated by the fact that www.dilbert.com has a TTL of 300 seconds, so your caching NS doesn't keep this record in memory too long. The problem is that the resolver in OpenBSD isn't reentrant. If it's doing nameresolution, it'll not do another one in parallel. So while you wait for www.dilbert.com to get resolved (which takes long because of this timeout), you open a new tab, enter an address and your machine will have to resolve that too, which gets queued up (doesn't get handled in parallel), so the other tab also waits on www.dilbert.com to get resolved. You can test this hypothesis by going to a website by its IP address. Try visiting http://129.128.5.191/ (http://www.openbsd.org/) while you're waiting for www.dilbert.com to load. Visiting by IP should work (as it doesn't require a DNS lookup). On 05/03/2008, Mayuresh Kathe [EMAIL PROTECTED] wrote: Paul, I tried your idea of starting up www.dilbert.com and then visiting http://129.128.5.191/ (the openbsd website). It worked as you'd predicted. So I guess its the problem with the OpenBSD resolver. If you're not able to code a parallel/reentrant DNS resolver for OpenBSD (I'm not), then here's a possible partial workaround: The Dilbert site carries heavy advertising. You can use the Ad Block Plus Firefox Add-On to diable the ads. You may wonder how blocking Ablobe Flush ads helps with a DNS resolution problem. Well, the reason this works is that most ads these days are included from advertisement agencies **which use their own domains**. So blocking these domains not only saves you all that Flash garbage (which also incidentally eats up clock cycles like candy), it also saves you from having to look up the agencies' domain names in the first place. When I visit Dilbert with ABP enabled, the following filters are actively blocking flashvertisements: *.247realmedia.com/RealMedia/ads/* *.advertising.com/* *.adsonar.com/* So in case of dilbert.com, with an appropriate blocklist, 247realmedia.com, advertising.com and adsonar.com are never resolved = no attempted IPv6 lookup attempt for them = less slowdown. NB: As for the number of open tabs, Firefox 2.0.0.x is a real sieve when it comes to memory. It leaks and leaks and leaks... The upcoming Firefox 3 is reportedly going to be a major step forward, but I haven't tried it yet. The desktop machine I'm currently using runs Ubuntu, so this may or may not be directly comparable, but in my experience Firefox 2.0.0.x **can** still be used with 20 tabs spread over 6 windows -- IFF you throw truckloads of RAM at it (e.g. 1-2GB),
Re: The Dilbert Problem...
I've been noticing a similar problem with Firefox on OpenBSD... Try going to http://www.blahsfkfefe.non-existant/ and then trying a known site like http://www.google.ca/ .. It just locks up.. If this is an issue with OpenBSD's resolver, why don't the developers fix it? -Nix Fan.
Re: The Dilbert Problem...
On Wednesday 05 March 2008 12:51:09 Unix Fan wrote: I've been noticing a similar problem with Firefox on OpenBSD... Try going to http://www.blahsfkfefe.non-existant/ and then trying a known site like http://www.google.ca/ .. It just locks up.. If this is an issue with OpenBSD's resolver, why don't the developers fix it? Well, I certainly haven't seen this, using the examples you gave. I don't know what the problem is, but regardless of what it is (or is not), the developers have to hear of a problem before they can fix it... --STeve Andre'
Re: The Dilbert Problem...
On Wed, Mar 05, 2008 at 09:51:09AM -0800, Unix Fan wrote: | I've been noticing a similar problem with Firefox on OpenBSD... | | Try going to http://www.blahsfkfefe.non-existant/ and then trying a known site like http://www.google.ca/ .. It just locks up.. | | If this is an issue with OpenBSD's resolver, why don't the developers fix it? Lemme think : o It's not easy to solve properly o It's not that big a deal o It's something that takes time to do (right) o Noone cares enough to fix it / other priorities If this is a big deal to you, your patches will be welcomed on [EMAIL PROTECTED] I'd even be happy to test 'em for you ;) Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Re: The Dilbert Problem...
I've been noticing a similar problem with Firefox on OpenBSD... I've also experienced this problem, but was never able to reproduce it. It would happen maybe once every month or two during normal web browsing (which in my case means 5 or more tabs simultaneously open in Firefox).
Re: The Dilbert Problem...
On Wed, Mar 5, 2008 at 10:25 AM, ropers [EMAIL PROTECTED] wrote: NB: As for the number of open tabs, Firefox 2.0.0.x is a real sieve when it comes to memory. It leaks and leaks and leaks... The upcoming Firefox 3 is reportedly going to be a major step forward, but I haven't tried it yet. It seems to be better, at least on osx. I have a number of add-ons enabled, and after a while, things slow down - I keep 15-30 tabs open at any one time. Using the nightlies I don't have as much issues as the 2.x series, from a performance point of view. -- http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted. -- Gene Spafford learn french: http://www.youtube.com/watch?v=j1G-3laJJP0feature=related
Re: The Dilbert Problem...
* Unix Fan [EMAIL PROTECTED] [2008-03-05 09:51:09]: I've been noticing a similar problem with Firefox on OpenBSD... Try going to http://www.blahsfkfefe.non-existant/ and then trying a known site like http://www.google.ca/ .. It just locks up.. If this is an issue with OpenBSD's resolver, why don't the developers fix it? -Nix Fan. I can't duplicate your problem on amd64-beta and version 2.0.0.12. However, I have seen behavior similar to what you describe. I don't think it's an issue with the stub resolver, since I've not seen this with any other application that is or runs on OpenBSD. It is very likely this is a bug in the firefox/mozilla code which I have suspected before is DNS-related but could be so many other things as well. -- Travers Buda
Re: The Dilbert Problem...
On 05/03/2008, Matthew Szudzik [EMAIL PROTECTED] wrote: I've been noticing a similar problem with Firefox on OpenBSD... I've also experienced this problem, but was never able to reproduce it. It would happen maybe once every month or two during normal web browsing (which in my case means 5 or more tabs simultaneously open in Firefox). Could this be because of local caching and little new resolve attempts?
