306496 - Crash ( pure virtual function ) with quicklaunch (turbo) during WinXP shutdown after Mozilla & desktop are gone

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Doug MacDonald]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728

I'm filing a separate bug because this one is different from the ones I found
when I searched the Bugzilla database.  I did find several "crash with pure
virtual function call" bug reports, most of them marked DUP.  Most or all of
them occurred while Mozilla was up and running.  Mine didn't.  It occurred 
  -  after I exited from Mozilla, leaving QuickLaunch active in the SysTray (see
step 12 under "Steps to Reproduce")
  -  after I had started Windows shutdown (see step 13 under "Steps to Reproduce")
  -  after the desktop wallpaper had disappeared

An alert suddenly appeared against one of the 3 blue shutdown screens (logging
off, saving your preferences, or windows is shutting down - I don't remember
which).  I was lucky to have been looking at the screen!  It appeared too
briefly for me to note which shutdown screen and too briefly for me to read all
of it.  

However, I did see the phrases "Visual C++" and "pure virtual function" in it. 
It was similar if not identical to the alert depicted in the attachment to bug
291250 entitled "Error that is produced within this bug".


Reproducible: Couldn't Reproduce

Steps to Reproduce:
I tried various actions, starting and restarting the system and Mozilla, without
being able to repeat the crash.  Sorry, I don't have time now to repeat the
whole migration scenario - maybe someday.  

However, I do think this case merits your attention because it appears to be
limited to QuickLaunch code paths, which could narrow your search considerably.  

I'm including a very detailed description in the hope that if someone repeats
the whole thing - including migration of an existing profile and not editing
prefs.js or prefs.bak before launching Mozilla the first time -  they might be
able to reproduce it. 

I was using Mozilla 1.7.20041.21708 until late June (2005), when my notebook
died.  I was able to rescue the hard drive contents, including my large Mozilla
profile with many email folders and a large bookmarks file.  I had earlier
migrated this profile to Mozilla from Netscape 7.x by editing the old profile
name into the new Mozilla/registry.dat file and editing pathnames in prefs.js
and prefs.bak.

I migrated to my new notebook by backing up the old notebook's HD to CDs, then
restoring to my "C:\Documents and Settings\" subfolder in the new notebook.  I
did this because drag & drop appeared not to copy all hidden and system files,
including my profile.

On the new notebook, which didn't have an old Netscape or Mozilla internet
client in it, I figured I needed to install a fresh Mozilla, then hack
Mozilla/registry.dat to make it play with the migrated files.  Last night I did
the following:
   1.  downloaded and installed the latest Mozilla installer,
mozilla-win32-1.7.11-installer.exe
   2.  moved the migrated profile folder into the new Application
Data\Mozilla\Profiles\default\ folder
   3.  edited Application Data\Mozilla\registry.dat to show the new profile
folder's mangled name
   4.  FORGOT to edit the account settings in prefs.js & prefs.bak to point to
my new Documents and Settings subfolder name, which unfortunately was different.
 This is the GOOF I mentioned above.
   5.  ran Mozilla, which ran fine on the browser side, and also mostly on the
mailer, except that the email accounts had no messages
   6.  tried to download mail to two email accounts, one POP3 and the other a
webmail/POP3 interface to mail.yahoo.com, but still no messages
   7.  realized my error, exited Mozilla, exited QuickLaunch, and edited
prefs.js and prefs.bak to use my new user folder name
   8.  checked my folder hierarchy and noted that Mozilla had added a subtree
named after my old user folder name, but it contained only 4 browser cache fies
and no email/news state
   9.  restarted the system
  10.  ran Mozilla, this time seeing all my migrated folders
  11.  downloaded the email into the two accounts mentioned above
  12.  exited Mozilla, leaving QuickLaunch active
  13.  shut down Windows by clicking "Start -> Turn Off Computer -> Turn Off"

Steps 12 and 13 were the actions mentioned at the beginning of the "Details"
section above.

Actual Results:  
n/a - see explanation above

Expected Results:  
It should exited quietly, without raising the alert.  I cannot point to any
persistent negative effects, such as a truncated bookmarks file.   

No module info - haven't instrumented a debugger at this time.  If I do, and the
problem recurs, I'll report it.

Comment 1

[Wayne Mery (:wsmwk)]

if you attempt to reproduce please use SM 1.1 or trunk

two items
1. without being able to repeat, how do you conclude this is quick launch?
2. would be great if STR are simplified

possibility related: 14807, bug 212316, Bug 144559.

Comment 2

[Doug MacDonald]

My reason for thinking it was Quick Launch is that that was probably the only part of Mozilla still running, because I had exited Mozilla and performed the Start --> Turn Off Computer action, and because (I have usually observed that) the shutdown processing displays the Deaktop until all application processes have exited.  In the case described, Mozilla was no longer displayed on the Taskbar (except for Quick Launch in the System Tray), and the Desktop and wallpaper _had_ gone away.

Of course, it could have been coincidence and may have nothing to do with Mozilla at all.  But my system is pretty stable and I don't recall any other instance of getting a crash message like this one, on the light blue login / shutdown screen.   The slightly broken account migration / installation sequence described above was the only recent thing I could think of that might have confused C++ runtime code - which I assume we're talking about because of the "pure virtual function" language in the error message.