[ros-bugs] [Bug 3676] New: Explorer crashes when choosing "Properties" from the Desktop context menu
ReactOS.Bugzilla at www.reactos.org
ReactOS.Bugzilla at www.reactos.org
Fri Aug 22 22:54:57 CEST 2008
http://www.reactos.org/bugzilla/show_bug.cgi?id=3676
Summary: Explorer crashes when choosing "Properties" from the
Desktop context menu
Product: ReactOS
Version: TRUNK
Platform: VMWare 5
OS/Version: ReactOS
Status: RESOLVED
Severity: normal
Priority: P3
Component: Shell
AssignedTo: janderwald at reactos.org
ReportedBy: mail at colinfinck.de
QAContact: ros-bugs at reactos.org
CC: reactos at byme.at
Colin Finck <mail at colinfinck.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
hpoussin <hpoussin at reactos.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |reactos at byme.at
j_anderw <janderwald at reactos.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Using r35508, Explorer crashes in shell32 when choosing "Properties" from the
Desktop context menu:
The instruction at "0x6a397474" referenced memory at "0x00000000". The memory
could not be "read"
raddr2line-ing this address outputs:
dll/win32/shell32/shv_def_cmenu.c:1411
(IDefaultContextMenu_fnInvokeCommand at 8)
Assigning this bug to janderwald as he implemented this code.
--- Comment #1 from Colin Finck <mail at colinfinck.de> 2008-08-21 22:45:25 CET ---
Bug is clearly reproducible and was confirmed by 3 people now
--- Comment #2 from hpoussin <hpoussin at reactos.org> 2008-08-21 23:05:38 CET ---
*** Bug 3673 has been marked as a duplicate of this bug. ***
--- Comment #3 from hefner <mail at mecklan.de> 2008-08-22 13:33:02 CET ---
Seems to be happens only on files with more than 1 dot in name
from a test with 35503:
(dll/ntdll/ldr/utils.c:2029) Failed to create or open dll section of
'C:\qemu-0.9.1-windows.zip' (Status c0000001)
(subsystems/win32/win32k/ntuser/timer.c:168) Unable to locate timer in message
queue for Window.
(ntoskrnl/mm/mm.c:222) Address: 850b7504
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 850b7504
Address: 6a37adab C:\ReactOS\system32\shell32.dll
CS:EIP 1b:6a37adab
DS 23 ES 23 FS 3b GS 0
EAX: 850b7504 EBX: 00000001 ECX: 00000001
EDX: ffffffff EBP: 008ad770 ESI: 761340f9 ESP: 008ad768
EDI: 008ad784 EFLAGS: 00000203
Frames:
6a360000+3b0cd C:\ReactOS\system32\shell32.dll
6a360000+37600 C:\ReactOS\system32\shell32.dll
6a360000+34562 C:\ReactOS\system32\shell32.dll
6a360000+35957 C:\ReactOS\system32\shell32.dll
77e30000+39114 C:\ReactOS\system32\user32.dll
77e30000+39462 C:\ReactOS\system32\user32.dll
77e30000+39a6a C:\ReactOS\system32\user32.dll
77e30000+250b2 C:\ReactOS\system32\user32.dll
77e30000+25491 C:\ReactOS\system32\user32.dll
76160000+233ab C:\ReactOS\system32\comctl32.dll
77e30000+39114 C:\ReactOS\system32\user32.dll
77e30000+39462 C:\ReactOS\system32\user32.dll
77e30000+39a6a C:\ReactOS\system32\user32.dll
76160000+20e8f C:\ReactOS\system32\comctl32.dll
76160000+23636 C:\ReactOS\system32\comctl32.dll
77e30000+39114 C:\ReactOS\system32\user32.dll
77e30000+39462 C:\ReactOS\system32\user32.dll
77e30000+39757 C:\ReactOS\system32\user32.dll
400000+3f5a6 C:\ReactOS\explorer.exe
400000+4beba C:\ReactOS\explorer.exe
400000+4c79a C:\ReactOS\explorer.exe
400000+65637 C:\ReactOS\explorer.exe
400000+6547d C:\ReactOS\explorer.exe
400000+6549a C:\ReactOS\explorer.exe
7c800000+21961 C:\ReactOS\system32\kernel32.dll
(subsystems/win32/csrss/api/wapi.c:115) CSR: received hard error c0000144
(subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at "0x6a37adab"
referenced memory at "0x850b7504". The memory could not be "read".
--- Comment #4 from Colin Finck <mail at colinfinck.de> 2008-08-22 14:27:58 CET ---
(In reply to comment #3)
> Seems to be happens only on files with more than 1 dot in name
> [...]
> (subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at "0x6a37adab"
> referenced memory at "0x850b7504". The memory could not be "read".
This looks like a totally different bug (different frame and memory addresses).
--- Comment #5 from j_anderw <janderwald at reactos.org> 2008-08-22 22:54:56 CET ---
* Fixed in rev 35540
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Ros-bugs
mailing list