Closed Bug 10526 Opened 26 years ago Closed 26 years ago

crash saving wallet information

Categories

(Core :: Networking, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED DUPLICATE of bug 10456

People

(Reporter: chofmann, Assigned: morse)

Details

after filling in wallet information from the samples page, clicking on the save button at the bottom of th page opens a small dialog box with messed up text in it, and then clicking ok causes crash. Steps: 1. Edit | Wallet | Samples 2. Click "HERE" to goto the wallet form page. 3. Fill in some information (first and last name) and click "SAVE" 4. Look at the dialog window that pops up (text is all messed up) 5. Click "OK" and watch apprunner crash. Expected: After clicking OK, a new dialog should ask for your password. Machine and Build: Win95, 166MHz, 64 MB RAM with NECKO build 1999072311
paulmac or chofmann, please confirm that this does not happen on M9 trunk builds. Necko only?
Target Milestone: M9
here is the stack... Incident ID 11625112 wallet_FetchFromNetCenter [d:\builds\seamonkey\mozilla\extensions\wallet\src\wallet.cpp, line 1361] wallet_FetchFieldSchemaFromNetCenter [d:\builds\seamonkey\mozilla\extensions\wallet\src\wallet.cpp, line 1391] wallet_Initialize [d:\builds\seamonkey\mozilla\extensions\wallet\src\wallet.cpp, line 1624] wallet_Capture [d:\builds\seamonkey\mozilla\extensions\wallet\src\wallet.cpp, line 1990] WLLT_OnSubmit [d:\builds\seamonkey\mozilla\extensions\wallet\src\wallet.cpp, line 2740] nsWalletlibService::Notify [d:\builds\seamonkey\mozilla\extensions\wallet\src\nsWalletService.cpp, line 211] nsFormFrame::OnSubmit [d:\builds\seamonkey\mozilla\layout\html\forms\src\nsFormFrame.cpp, line 475] nsButtonControlFrame::MouseClicked [d:\builds\seamonkey\mozilla\layout\html\forms\src\nsButtonControlFrame.cpp, line 357] nsFormControlFrame::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\forms\src\nsFormControlFrame.cpp, line 586] nsButtonControlFrame::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\forms\src\nsButtonControlFrame.cpp, line 583] nsEventStateManager::CheckForAndDispatchClick [d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line 676] nsEventStateManager::PostHandleEvent [d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line 195] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2251] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 834] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 819] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 819] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 819] nsViewManager::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1736] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 67] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 493] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 514] nsWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3258] ChildWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3409] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2514] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 579] KERNEL32.DLL + 0x3663 (0xbff73663) KERNEL32.DLL + 0x22894 (0xbff92894) 0x00638c18
Assignee: gagan → morse
Steve is probably a better owner looking at the stack trace.
Status: NEW → ASSIGNED
Looks like it might be related to 10456. I say that because the crash is occuring in the FetchFromNetcenter routine in both cases. But 10456 has the stacktrace going deeper (into OpenInputStream) which this bug does not, so they are probably not duplicates. I'll investigate.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
That's strange -- I just tested this and it works for me. I have a tree that was pulled at 11AM on Friday the 23rd and build with NECKO=1. Closing this out as WORKS-FOR-ME. Please let me know if you are still getting the failure. BTW, I've already filed a bug report on item #4 (text all messed up). It's 10423.
I get no response to clicking on the "save" button(step 3) with the 990726 necko builds
Status: RESOLVED → REOPENED
That's good news -- at least you are no longer getting a crash. But you should get the message asking if you want to save the values on the form. That's the bad news. I'll pull a fresh tree right now and try this out again. Reopening the report for the time being, until I get the new results.
Status: REOPENED → RESOLVED
Closed: 26 years ago26 years ago
Chris, I don't know why you are getting the behavior you describe. Using a fresh tree that I just pulled and built with NECKO=1 last night (7-26) at around midnight, I am not seeing any problems. I go to samples page that you refer to, fill in some information, and then press save. I get a dialog asking if I want to save the data. I reply yes and then I get a second dialog asking for a database password. I provide one and the data gets saved. Closing this out once again as works-for-me.
Status: RESOLVED → REOPENED
Status: REOPENED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: WORKSFORME → DUPLICATE
Status: RESOLVED → VERIFIED
Well this crashes for me on an 11am Friday pull but it is probably a dup of 10456. At least the behavior is similar. Will re-open and mark as suck for bug tracking.
*** This bug has been marked as a duplicate of 10456 ***
No sync in HTTP as yet.
I like that I wrote 'suck' instead of 'such' in my comments of 7/30. Must have been a freudian slip :-)
Bulk move of all Necko (to be deleted component) bugs to new Networking component.
You need to log in before you can comment on or make changes to this bug.