Step to reproduce the bug : Open mozilla Type the url Hit return Version 0.9.3 Buildid : 2001080110 As I mention in the bug description, the bug may be related to my strange proxy setting. I have 3 crash related to this bug, but Talkback can't pass througth my proxy. If there is a way to take talkback report and attach them directly to the bug, let me know. If not, I'll try to use that config file as describe in bug 19271. Regarding my proxy setting, I have one set for the http and one for the sock. What I am using is actualy a proxy that connect to another proxy. The other line of the manual proxy setting dialog are blank. I know I don't provide you a lot of information on that, but I am willing to do test. If somebody else could try to access the same url with the same build without a proxy (and with another) to make sure my proxy setting are invole in the bug, I would appreciate.
Reporter: The URL loads "fine" (it doesn't crash) but is a 404 page. If I recall corectly, when Moz crashes and Talkback pops up, it creates a talkback.ini file which contains the needed info. When Talkback pops up, just ignore it for a moment and search for that. If you find it, attach it. Better than nothing. :)
Sorry, I made a mistake typing the URL, it's a https, not a http.
Any https access on tzone.org seem to reproduce the bug. I also try https on another site (www.ebookers.fr) and it reproduce the bug. Regarding talkback, the talkback.ini contains the following : HistorySettings = 3, 10, 100 SeenIntro = 1 EmailEdit = "email@example.com" URLEdit = "https://www.ebborkers.com/..." LocalKey = 82A55A7A46 MainWindowTop = 23 MainWindowLeft = 22 MainWindowWidth = 803 MainWindowHeight = 571 ColumnWidths = 80, 90, 115, 150 RandomPool = 8A6A4D2CC89916D9292E1D3814BDEBE3C4B604A59B3CEB2BA80C1AE83C4BA2AE1BA12266D72E2576 2609E612D247DC9345FF2168E801B68CDEDC6D97140679C32356D1D6C32C2D434D22506817F58A75 BEAFE1E48E01521925E0D722AECE122DAA61AF83E2AF4A7097CD81C40BC0649FD91D6A5616EB06E7 156CB6CEA6BF7F94 I don't it's very usefull, but there is also file with the .pak extension, in the same number that the number of crash I had with mozilla. If I attach those file, can someone read them?
Grey and Guillaume, thanks for your help in testing Mozilla. The talkback data actually isn't useful until it has been sent into a server where I can extract a stack trace. Please go to your Mozilla install directory, look for a components/ directory. In there you should see a program called talkbacl.exe. Doubleclick on that application and it will launch the Talkback executable. If you already sent in the report and the send was successful you should see one (or more) talkback Incidents listed in the Talkback window. If you see that please comment the Incident ID to this bug. If you don't see that please try to reproduce the crash again and make sure to send in the data when the talkback wizard pops up. You can run talkback.exe again and it should have an Incident ID. Thanks.
Incident id that I think are related to this bug : TB34235012K https://www.ebookers.com/ TB34234473W https://www.tzone.org/ TB34229974E https://www.tzone.org/imp/ Also, the bug seem to happer on any https I try. Anybody has a list of https that I could try.
looks like PSM to me. Incident ID 34229974 Stack Signature nsHashtable::Exists 68fe52d9 Bug ID Trigger Time 2001-08-17 07:19:17 Email Address firstname.lastname@example.org User Comments Type this url in the location bar and hit return see bug 94523 Build ID 2001080112 Product ID MozillaTrunk Platform ID Win32 Trigger Reason Access violation Stack Trace nsHashtable::Exists [d:\builds\seamonkey\mozilla\xpcom\ds\nsHashtable.cpp, line 261] nsSSLIOLayerSetOptions [d:\builds\seamonkey\mozilla\security\manager\ssl\src\nsNSSIOLayer.cpp, line 1802] nsSSLIOLayerAddToSocket [d:\builds\seamonkey\mozilla\security\manager\ssl\src\nsNSSIOLayer.cpp, line 1881] nsSSLSocketProvider::AddToSocket [d:\builds\seamonkey\mozilla\security\manager\ssl\src\nsSSLSocketProvider.cpp, line 74] nsSocketTransport::doConnection [d:\builds\seamonkey\mozilla\netwerk\base\src\nsSocketTransport.cpp, line 737]
Assignee: asa → ssaux
Status: UNCONFIRMED → NEW
Component: Browser-General → Client Library
Ever confirmed: true
Product: Browser → PSM
QA Contact: doronr → ckritzer
Version: other → unspecified
reporter, can you try a more recent build? Using win32 Build ID 2001082803 and a proxy server I'm able to connect without a crash. Marking as worksforme. Reopen is necessary.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
Tested build 2001082803 Confirmed worksforme
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.