User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en; rv:220.127.116.11pre) Gecko/2009020700 Camino/2.0b2pre (like Firefox/3.0.7pre) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en; rv:18.104.22.168pre) Gecko/2009020700 Camino/2.0b2pre (like Firefox/3.0.7pre) there is at least a two minute hangup waiting for this to load: tag.contextweb.com, refreshing the page does not help. Nightly builds do not solve problem as it is reoccurring. Reproducible: Always Steps to Reproduce: 1. Load any site that uses tags from contextweb.com 2. 3.
Does the same thing happen in any other browser? Does it happen with a fresh profile using Troubleshoot Camino? http://pimpmycamino.com/parts/troubleshoot-camino
It happens in Camino and Firefox but NOT with Safari or IE. It does NOT happen with "troubleshoot Camino"
If you quit Camino, move the prefs.js and user.js files out of ~/Library/Application Support/Camino/ and then re-launch Camino, does the problem persist?
Problem still exists after deleting pref.js file. There was no user.js file.
Try the same thing again, but with the permissions.sqlite file this time instead. If that *still* doesn't change anything, and you have some time to troubleshoot this further, try removing each file or folder from your profile one at a time and testing in turn. When you find the file that caused the problem, let us know what it was (and save it). Make sure Camino is not running whenever you change anything in the profile folder.
Deleted every file, problem still exists.
Try clearing your cache. I have no idea *why* that would cause this, but that (or some haxie or input manager that you might be running) are about the only other things I can think of.
Clearing the cache does not help. Might have something to do with the website itself I suppose. Down right irritating. Thanks for trying....
Troubleshoot Camino merely automates the process of * using a fresh profile * using a fresh cache * disabling any haxies/inputmanagers that respect our "no hacks" environment variable. The fact that TC worked and doing these things manually hasn't suggests to me that you might have missed a step somewhere ;)
email@example.com, are you still seeing this problem?
Whiteboard: [CLOSEME - 4/5]
Yes, the problem still exists.
OK, let's try this again. Quit Camino. Move aside your ~/Library/Application Support/Camino/ folder. Put it on the Desktop or something. Do the same thing with both ~/Library/InputManagers/ and /Library/InputManagers/ (the former is in your user folder's Library folder; the latter is in the Library folder at the root level of your hard drive). Re-launch Camino and see if the problem exists. If the problem still exists, let us know. If the problem does NOT still exist -- and I bet it won't -- quit Camino again. Now, put back the contents of the Camino profile folder one item at a time. Relaunch Camino and test for this bug after putting each item back. Make sure you quit Camino before putting each subsequent item back in the profile. When the bug reappears, let us know what file you most recently put back in the profile.
The Camino and the users inputmanagers folders are not the problem. I cannot find the other inputmanagers folder in the root library folder.
Try Troubleshoot Camino again. Also, if you could get a sample of the hang, that might be helpful. cl
How do I "get a sample of the hang" and get it to you?
http://caminobrowser.org/documentation/bugzilla/#hang explains it. You can attach the sample here using the "Add an attachment" link above. cl
Is that an example of a site where you're experiencing the hang? If so, I can't get that site to hang Camino 1.6 with a fresh profile *or* Camino trunk with my normal profile. Did a fresh profile (via Troubleshoot Camino) work for you a second time?
It still hangs after second try.
Can you please attach a sample of the hang as requested in comment 16?
Whiteboard: [CLOSEME - 4/5] → [CLOSEME - 4/19]
Can you explain to me in some detail how to do that? I don't have a clue. Sorry.
The link in comment 16 explains it very clearly. Is there a specific part of the process there you don't understand? cl
I still can't reproduce this, but if you try to load that site with NOTHING else loaded (i.e., in the only open tab/window), do you still get the hang? If so, take another sample and compare it to the one you posted in comment 23 -- are they similar? I'm curious to know if the sample itself is reproducible.
(In reply to comment #23) > Requested Sample This was taken while Camino was hung (showing the spinning rainbow cursor and not responding to clicks)? It doesn't look consistent with a hang. I'm a little confused by your initial statement that "refreshing the page does not help". How are you refreshing the page if the browser is hung?
Can you please respond to comment 24/25?
Whiteboard: [CLOSEME - 4/19] → [CLOSEME - 5/31]
Ok, last time.... I load this page via browser. It loads till I get the message in the bottom left hand side of the screen that reads: Waiting for tag.contexweb.com. The screen is blank with the exception of the black arrow and the black and white spinning ball. At this time I started to load the page at 8:31pm, it is now 8:38pm and the page is still trying to load. Page finally finished loading at 8:39pm. I refresh the browser using the "refresh" button at the top of the screen. The page reloads once again until it gets to the contexweb item and starts the cycle all over again. The browser is NOT locked up. It is still functional at any time till it loads contextweb.
Okay, so this is not actually a hang, it's just a slow response. Retitling to clarify. The samples don't actually tell us what's going on since it's not a hang. Since this happens in Firefox as well I suspect that the best approach here is to file a new bug--since this one has a lot of noise to due the misunderstanding of what the actual symptoms were--against Firefox, since that way it can be more easily routed to the correct people who can help debug this (the Camino developers don't have anything to do with low-level networking code). When you file the new bug, be sure to include a specific URL that people can use to try to reproduce this (like your comment 17); I had originally tried to reproduce this by going to tags.contextweb.com, and only just now noticed that that's not how to reproduce this, since there was no URL given in the initial report. Also, you'll want to avoid the term "hang" to prevent confusion. (And for the record, now that I know how to reproduce this I tried with the URL in comment 17 and it worked for me)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
Summary: When visiting sites the use the following: tag.contextweb.com, browser hangs up. → Very long delay loading tag.contextweb.com
You need to log in before you can comment on or make changes to this bug.