Closed Bug 216540 Opened 22 years ago Closed 21 years ago

Mozilla unnecessarily opens index.dat from IE

Categories

(Core Graveyard :: File Handling, defect)

Product:
Core Graveyard
Component:
File Handling
Platform:
x86
Windows 95
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: aceman, Assigned: law)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98) Build Identifier: Mozilla 1.3.1 When using Mozilla and watching it with a process monitoring program (i used TaskInfo 2002) I noticed it has open some files which belong to IE (4). They were index.dat, located in the Cache, Cookie and History directories as set in IE. They were open and seeked to offset 0. This probably causes no serious problems. Maybe just takes up memory, file handles and time. I haven't tried what happens, when IE is run at this time. Maybe it would be allowed to read and write these files. But what if it tried to remove them? You know, when Mozilla has about 90 files open when just reading mail, any file handles that can be saved and files not opened are a win. Reproducible: Always Steps to Reproduce: 1.Run Mozilla 2.Use a process monitoring program to watch files Mozilla has opened Actual Results: The files index.dat in various IE directories are opened at offset 0. Expected Results: No such files should be open. Mozilla must not touch IE if it is properly installed and no migration or import is requested.
worksforme Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030802 Mozilla Firebird/0.6.1 and 20030817. I used www.sysinternals.com File Monitor and filtered "index". 1.3.1 is pretty old. Could you try a more recent version?
wfm with a current trunk and win2k (used taskinfo2002 )
Comment #1: Maybe you should look for "INDEX". I just tested it with Mozilla 1.4, IE 5.5, Win 98, sysinternals.com process explorer. The files are still there. Interestingly, the first time I tried it, I started Moz with the monitor running. The index.dat files were opened at quite an early stage. But then, with the splash screen still shown, Moz hanged. I had to kill it. Then I started it without the monitor and all went ok. I started the monitor when Moz was fully ready. The index files were there. I am waiting for 1.5b... Do both of you have IE properly installed and configured, can you use it on the web normally?
OS: Windows 98 → Windows 95
Now I noticed both of you have Win NT 5.x. There may be some difference against Win 9x...
aceman, file monitor appears to be case-insensitive. Launching IE shows pages of hits to index.dat files, but when IE isn't running, I see none.
It is still there in Firebird 0.6.1 (=1.5a). Chris, could you try it without filtering? Show all files and search it manually.
OS: Windows 95 → NetBSD
Ok, here it comes. I still found it in the absolutely latest Firebird nightly (=Moz 1.5b). See the attachment for the handle list. BTW: this one feels much faster than the stable 0.6.1 :)
Adding an attachment causes a server error... I'll paste it here: Process: MOZILLAFIREBIRD.EXE Pid: FFFCEF2B Handle Type Access Name 0x70 Device 0x00000000 WSOCK2 0x10C File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\CLASSIC.JAR 0x110 File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\EN-US.JAR 0x114 File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\EN-WIN.JAR 0x11C File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\US.JAR 0x120 File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\BROWSER.JAR 0x124 File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\TOOLKIT.JAR 0x128 File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXX.SLT\CACHE\_CACHE~1 0x12C File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXX.SLT\CACHE\_CACHE~2 0x130 File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXX.SLT\CACHE\_CACHE~3 0x134 File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXX.SLT\CACHE\_CACHE~4 0x154 File 0x00000023 C:\PROGRA~1\MOZILL~1\CHROME\COMM.JAR 0x98 File 0x00000133 C:\WINDOWS\TEMPOR~1\CONTENT.IE5\INDEX.DAT 0xA4 File 0x00000133 C:\WINDOWS\COOKIES\INDEX.DAT 0xB0 File 0x00000133 C:\WINDOWS\HISTORY\HISTORY.IE5\INDEX.DAT 0xD4 File 0x00000130 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXXX.SLT\PARENT~1.LOC 0xF4 File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXXX.SLT\HISTORY.DAT 0xF8 File 0x00000133 C:\WINDOWS\APPLIC~1\PHOENIX\PROFILES\DEFAULT\XXXXXXXX.SLT\FORMHI~1.DAT 0x44 MappedFile 0x00000000 fileAllocatorMutex 0x6C MappedFile 0x00000000 spiral_persistent_counter_shared_memoryNetscapeMozillaFirebirdWin322003082518 0x9C MappedFile 0x00000000 C:_WINDOWS_Temporary Internet Files_Content.IE5_index.dat_507904 0xA8 MappedFile 0x00000000 C:_WINDOWS_Cookies_index.dat_49152 0xB4 MappedFile 0x00000000 C:_WINDOWS_History_History.IE5_index.dat_311296 0xC MappedFile 0x00000000 rpcrt4sharedmem 0xDC MappedFile 0x00000000 DCOMSharedGlobals12321 0xE4 MappedFile 0x00000000 fileAllocatorMutex 0x10 Mutex 0x001F0001 OLESCMLOCKMUTEX 0x1C Mutex 0x001F0001 Winsock2ProtocolCatalogMutex 0x20 Mutex 0x001F0001 Winsock2ProtocolCatalogMutex 0x28 Mutex 0x001F0001 OleCoSharedStateMtx 0x2C Mutex 0x001F0001 OLESCMSRVREGLISTMUTEX 0x30 Mutex 0x001F0001 OLESCMGETHANDLEMUTEX 0x34 Mutex 0x001F0001 OLESCMROTMUTEX 0x38 Mutex 0x001F0001 OleDfSharedMemoryMutex 0x3C Mutex 0x001F0001 ScmWIPMutex 0x64 Mutex 0x001F0001 spiral_persistent_counter_mutexNetscapeMozillaFirebirdWin322003082518 0x7C Mutex 0x00100000 WininetConnectionMutex 0x84 Mutex 0x00100000 WininetProxyRegistryMutex 0x88 Mutex 0x00100000 WininetStartupMutex 0x90 Mutex 0x00100000 _!MSFTHISTORY!_ 0x94 Mutex 0x00100000 c:!windows!temporary internet files!content.ie5! 0xA0 Mutex 0x00100000 c:!windows!cookies! 0xAC Mutex 0x00100000 c:!windows!history!history.ie5! 0xD8 Mutex 0x001F0001 ObjectResolverGlobalMutex 0xF0 Mutex 0x001F0001 Microsoft RPC UUID Mutex 0x4 Process 0x001F0FFF MOZILLAFIREBIRD.EXE(FFFCEF2B) 0x40 Semaphore 0x001F0003 DocfileAllocatorMutex 0xE0 Semaphore 0x001F0003 DocfileAllocatorMutex 0x100 Thread 0x00000000 MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF88A2F 0x104 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF88A2F 0x118 Thread 0x00000000 MOZILLAFIREBIRD.EXE(FFFCEF2B): FFC70073 0x13C Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFFB0273 0x14 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8629F 0x140 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFFB0273 0x144 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF90FCF 0x148 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFC70073 0x24 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8629F 0x48 Thread 0x00000000 MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF93C7B 0x54 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8629F 0x74 Thread 0x00000000 MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8293F 0xBC Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8293F 0xC4 Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF8293F 0xC8 Thread 0x00000000 MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF90FCF 0xCC Thread 0x001F03FF MOZILLAFIREBIRD.EXE(FFFCEF2B): FFF90FCF
OS: NetBSD → Windows 95
Further research has shown interesting facts. It looks like ANY program using Winsock(2) have these files opened. Even those which have nothing to do with the web, just need a network connection. Is this some M$ 'feature'? Can somebody confirm this, so I can mark this bug as Invalid?
I have just tested this. Those files are not open on win2000, even though they exist in the IE cache dir.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.