Open Bug 976265 Opened 11 years ago Updated 3 years ago

Looking for CurWorkD causes main thread I/O.

Categories

(Core :: XPCOM, defect)

defect

Tracking

()

People

(Reporter: Yoric, Unassigned)

Details

(Keywords: main-thread-io)

While looking at bug 859912, I found out that a call to nsDirectoryService::Get with "CurWorkD" indirectly calls fstat64, which does main thread I/O. Looking at the stack, I'm not sure that there is much we can do about it. * thread #1: tid = 0x2003, 0x00007fff8dac955c libsystem_kernel.dylib`fstat$INODE64, stop reason = breakpoint 1.1 frame #0: 0x00007fff8dac955c libsystem_kernel.dylib`fstat$INODE64 frame #1: 0x00007fff8b1050ff libsystem_c.dylib`__getcwd + 108 frame #2: 0x00007fff8b105347 libsystem_c.dylib`__private_getcwd + 209 frame #3: 0x0000000100056d2b XUL`nsDirectoryService::GetFile(char const*, bool*, nsIFile**) [inlined] nsGetterAddRefs<nsIFile>::operator nsIFile**(aSmartPtr=0x0000000000000000, aSystemSystemDirectory=0) + 29 at SpecialSystemDirectory.cpp:492 frame #4: 0x0000000100056d0e XUL`nsDirectoryService::GetFile(, _retval=0x00007fff5fbfca38) + 718 at nsDirectoryService.cpp:553 frame #5: 0x0000000100056338 XUL`FindProviderFile() + 280 at nsDirectoryService.cpp:355 frame #6: 0x00000001000561a7 XUL`nsDirectoryService::Get(this=0x0000000107226440, prop=0x0000000107e54430, uuid=0x0000000107e54450, result=0x00007fff5fbfcbd0) + 311 at nsDirectoryService.cpp:399
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.