At this point in time I'm fairly sure it's a bug in a proprietary java messaging library I'm using and for which I don't have source. I turn on a certain feature, client persistence (which writes messages to disk before they are sent), and the problem occurs. When I wrote earlier I hadn't yet tracked it down to specifically client persistence.
It really doesn't make much sense; the behavior when the problem manifests seems very much like a deadly embrace. I can't think of any resource that both a browser and a messaging library might have in common (other then acquiring specific ports). Nonetheless, the problem does not appear using either FF or IE. On Mon, Jul 20, 2009 at 5:56 PM, Eric Roman<[email protected]> wrote: >> Is there a list of ports that Chromium uses? > > Chromium should not be listening on any ports. > > That sounds strange. > > I suggest filing a bug with more details at: > http://crbug.com > > Specifically stuff to describe: > - what are the repro steps (are you navigating to google.com, or > typing search queries in omnibox etc..) > - what does the bottom left "load state" read while it is hung > waiting (resolving host, waiting for server, etc...) > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
