[8.0ß23 x64] Image OLE tooltip crash

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
umbra
Power Member
Power Member
Posts: 871
Joined: 2012-01-14, 20:41 UTC

Post by *umbra »

2ghisler(Author)
It should redirect you to a specific picture called "My will is the source of my power". Also when you open its site, don't download the big thumbnail but click on the "Download Image" button.

To check if you have the right file, check its Properties->Details->GPS whether it contains a nonsense or some valid data (or nothing) - just see my previous posts.
Windows 7 Pro x64, Windows 10 Pro x64
Top
User avatar
HolgerK
Power Member
Power Member
Posts: 5406
Joined: 2006-01-26, 22:15 UTC
Location: Europe, Aachen

Post by *HolgerK »

umbra wrote:"My will is the source of my power".
http://fc09.deviantart.net/fs71/f/2012/083/b/2/my_will_is_the_source_of_my_power_by_titschipoo-d4tqyjb.jpg

Okay confirmed (had to disable the MediaInfo Tooltip-Handler).
TC 8.0b23 x86 Okay
TC 8.0b23 x64 "stopped responding"
MS Problem report:

Code: Select all

<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
	<OSVersionInformation>
		<WindowsNTVersion>6.1</WindowsNTVersion>
		<Build>7601 Service Pack 1</Build>
		<Product>(0x1): Windows 7 Ultimate</Product>
		<Edition>Ultimate</Edition>
		<BuildString>7601.17727.amd64fre.win7sp1_gdr.111118-2330</BuildString>
		<Revision>1130</Revision>
		<Flavor>Multiprocessor Free</Flavor>
		<Architecture>X64</Architecture>
		<LCID>1033</LCID>
	</OSVersionInformation>
	<ParentProcessInformation>
		<ParentProcessId>2884</ParentProcessId>
		<ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
		<ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
	</ParentProcessInformation>
	<ProblemSignatures>
		<EventType>APPCRASH</EventType>
		<Parameter0>TOTALCMD64.EXE</Parameter0>
		<Parameter1>8.0.0.1</Parameter1>
		<Parameter2>00000000</Parameter2>
		<Parameter3>PhotoMetadataHandler.dll</Parameter3>
		<Parameter4>6.1.7600.16385</Parameter4>
		<Parameter5>4a5be037</Parameter5>
		<Parameter6>c0000090</Parameter6>
		<Parameter7>000000000001bfaf</Parameter7>
	</ProblemSignatures>
	<DynamicSignatures>
		<Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
		<Parameter2>1031</Parameter2>
		<Parameter22>c719</Parameter22>
		<Parameter23>c719fb1b445e58a2e114b3bae027d08d</Parameter23>
		<Parameter24>dbbd</Parameter24>
		<Parameter25>dbbd00130113d2e8add43eb919c65f45</Parameter25>
	</DynamicSignatures>
	<SystemInformation>
		...
	</SystemInformation>
</WERReportMetadata>
Callstack:

Code: Select all

>	PhotoMetadataHandler.dll!000007fef69cbfaf() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for PhotoMetadataHandler.dll]	
 	PhotoMetadataHandler.dll!000007fef69ba919() 	
 	PhotoMetadataHandler.dll!000007fef69b50c9() 	
 	PhotoMetadataHandler.dll!000007fef69b5276() 	
 	PhotoMetadataHandler.dll!000007fef69b48bf() 	
 	PhotoMetadataHandler.dll!000007fef69b4bf7() 	
 	PhotoMetadataHandler.dll!000007fef69b44f8() 	
 	WindowsCodecs.dll!000007fefbeb537c() 	
 	PhotoMetadataHandler.dll!000007fef69b42b2() 	
 	PhotoMetadataHandler.dll!000007fef69b2de5() 	
 	PhotoMetadataHandler.dll!000007fef69b346a() 	
 	PhotoMetadataHandler.dll!000007fef69b3feb() 	
 	propsys.dll!000007fefc474cc9() 	
 	shell32.dll!000007fefe5a5ae2() 	
 	propsys.dll!000007fefc474cc9() 	
 	propsys.dll!000007fefc475c1e() 	
 	propsys.dll!000007fefc475b32() 	
 	propsys.dll!000007fefc474cc9() 	
 	propsys.dll!000007fefc475c1e() 	
 	propsys.dll!000007fefc475b32() 	
 	propsys.dll!000007fefc474cc9() 	
 	propsys.dll!000007fefc474bb9() 	
 	propsys.dll!000007fefc474af1() 	
 	propsys.dll!000007fefc474a5e() 	
 	shell32.dll!000007fefe77a569() 	
 	TOTALCMD64.EXE!000000000055e62b()
Regards
Holger
Top
User avatar
sztihamer
Member
Member
Posts: 117
Joined: 2012-01-31, 17:46 UTC

Post by *sztihamer »

I can also reproduce the problem, same thing as the previous ones. There is definitely something wrong here. This doesn't supposed to happen I guess.
Screenshot: http://i.imgur.com/1xHdN.png

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	TOTALCMD64.EXE
  Application Version:	8.0.0.1
  Application Timestamp:	00000000
  Fault Module Name:	PhotoMetadataHandler.dll
  Fault Module Version:	6.1.7600.16385
  Fault Module Timestamp:	4a5be037
  Exception Code:	c0000090
  Exception Offset:	000000000001bfaf
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	c719
  Additional Information 2:	c719fb1b445e58a2e114b3bae027d08d
  Additional Information 3:	dbbd
  Additional Information 4:	dbbd00130113d2e8add43eb919c65f45
Top
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48093
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:
Contact ghisler(Author)

Post by *ghisler(Author) »

Thanks, I had indeed the wrong picture! It's causing an SSE exception, although I'm disabling them at program start! Please try with beta 24 - I'm now disabling SSE exceptions before each call to the load tip function.

The SSE exception seems to occur because the GPS coordinates contain 0.0/0.0 as the last number pair (as can be seen with Irfanview), which is a division by zero.
Author of Total Commander
https://www.ghisler.com
Top
User avatar
sztihamer
Member
Member
Posts: 117
Joined: 2012-01-31, 17:46 UTC

Post by *sztihamer »

I can confirm that it's fixed in Total Commander 8.0ß24 x64. No more crashes if OLE2 comments are enabled. It just works as it supposed to.
Top
umbra
Power Member
Power Member
Posts: 871
Joined: 2012-01-14, 20:41 UTC

Post by *umbra »

Only partially fixed. Now TCx64 crashes the same way as TCx32. However the crash report now shows different values. Original post: http://ghisler.ch/board/viewtopic.php?p=245200#245200

First, it will show a message box with text "Exception EInvalidOp in module TOTALCMD.EXE at 6C698673. Invalid floating point operation." When you close it, another message box will appear with text "Control deleted from background thread!". This message cannot be closed - it will keep reopening until you kill TC's process. And sometimes, but not always, you can see a crash dialog:

Code: Select all

---------------------------
Total Commander 8.0ß24
---------------------------
Access violation at address 0044823A. Read of address 000000E4.
Access violation at address 0044823A. Read of address 000000E4
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0044823A
4244D8  424C84  4270DD  >423E00  423E00  42602A
44471D  423E00  445EE0  44621B  448238  44471D
44666E  423E00  445C2F  423E00  42941E  429564
6D95C1  
Raw:
448238  424467  4244D8  424957  424C84  4270DD
44471D  44693D  425ADC  44667A  423E00  4469E7
42666D  446FC5  44471D  44693D  425ADC  44667A
423E00  42602A  426F42  44471D  44693D  425ADC
44667A  423E00  445EE0  5F004A  402235  4033BC
4021B4  4023DB  4026A4  4036AD  445A96  6D6285
41D98C  446066  44621B  5F004A  445B9D  421193
424804  4263D4  4463C2  448226  448238  64A818
445B9D  423E00  4469E7  402E36  44471D  44693D
425ADC  445CF1  44666E  423E00  445C2F  423E00

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes   No   
---------------------------
For some reason, TCx64 crashes without showing any error.
Windows 7 Pro x64, Windows 10 Pro x64
Top
User avatar
sztihamer
Member
Member
Posts: 117
Joined: 2012-01-31, 17:46 UTC

Post by *sztihamer »

Didn't payed enough attention about the part where you have to press delete. You are right umbra. I get the same error messages and crashes. It seems to be partially fixed, but at least we have the tooltips for now.

Code: Select all

---------------------------
Total Commander 8.0ß24
---------------------------
Access violation at address 0044823A. Read of address 000000E4.
Access violation at address 0044823A. Read of address 000000E4
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0044823A
4244D8  424C84  4270DD  >423E00  423E00  42602A
44471D  423E00  445EE0  44621B  448238  44471D
44666E  423E00  445C2F  423E00  42941E  429564
6D95C1  
Raw:
448238  424467  4244D8  424957  424C84  4270DD
44471D  44693D  425ADC  44667A  423E00  4469E7
42666D  446FC5  44471D  44693D  425ADC  44667A
423E00  42602A  426F42  44471D  44693D  425ADC
44667A  423E00  445EE0  5F004A  402235  4033BC
4021B4  4023DB  4026A4  4036AD  445A96  6D6285
41D98C  446066  44621B  5F004A  421193  421193
424804  4263D4  4463C2  448226  448238  64A818
445B9D  423E00  4469E7  402E36  44471D  44693D
425ADC  445CF1  44666E  423E00  445C2F  423E00

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes   No   
---------------------------

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	TOTALCMD64.EXE
  Application Version:	8.0.0.1
  Application Timestamp:	00000000
  Fault Module Name:	PhotoMetadataHandler.dll
  Fault Module Version:	6.1.7600.16385
  Fault Module Timestamp:	4a5be037
  Exception Code:	c0000090
  Exception Offset:	000000000001bfaf
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	41b6
  Additional Information 2:	41b66de3883f1aade1942da5d1ab4c5c
  Additional Information 3:	548b
  Additional Information 4:	548b68219fd8b776cc2139b72aa42e53
Here's a video demonstration of the bug: http://screenr.com/XlS8
Top
User avatar
HolgerK
Power Member
Power Member
Posts: 5406
Joined: 2006-01-26, 22:15 UTC
Location: Europe, Aachen

Post by *HolgerK »

29.03.12 Fixed: Some jpg files could cause an SSE floating point exception in Microsoft's PhotoMetadataHandler -> turn off SSE exceptions before each call to GetInfoTip (32/64)
Fix confirmed with TC8.0b24 x64

Regards
Holger
Top
User avatar
HolgerK
Power Member
Power Member
Posts: 5406
Joined: 2006-01-26, 22:15 UTC
Location: Europe, Aachen

Post by *HolgerK »

umbra wrote:Only partially fixed.
2umbra

This seems to be a complete different bug!

I can confirm that TC8.0B23/24 x64 stops working if I press <Del> to delete the mentioned jpg (even without moving the mouse over the file, so the tooltip would never appear).

Callstack(TC8.0b23 x64):

Code: Select all

>	PhotoMetadataHandler.dll!000007fef790bfaf() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for PhotoMetadataHandler.dll]	
 	PhotoMetadataHandler.dll!000007fef78fa919() 	
 	PhotoMetadataHandler.dll!000007fef78f50c9() 	
 	PhotoMetadataHandler.dll!000007fef78f5276() 	
 	PhotoMetadataHandler.dll!000007fef78f48bf() 	
 	PhotoMetadataHandler.dll!000007fef78f4bf7() 	
 	PhotoMetadataHandler.dll!000007fef78f44f8() 	
 	WindowsCodecs.dll!000007fefbe3537c() 	
 	PhotoMetadataHandler.dll!000007fef78f42b2() 	
 	PhotoMetadataHandler.dll!000007fef78f2de5() 	
 	PhotoMetadataHandler.dll!000007fef78f346a() 	
 	PhotoMetadataHandler.dll!000007fef78f3feb() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	shell32.dll!000007fefe535ae2() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d5c1e() 	
 	propsys.dll!000007fefc4d5b32() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d5c1e() 	
 	propsys.dll!000007fefc4d5b32() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d4bb9() 	
 	propsys.dll!000007fefc4d4af1() 	
 	propsys.dll!000007fefc4d4a5e() 	
 	shell32.dll!000007fefe70a569() 	
 	shell32.dll!000007fefe796a7d() 	
 	shell32.dll!000007fefe83bcde() 	
 	shell32.dll!000007fefe83e262() 	
 	shell32.dll!000007fefe83c845() 	
 	shell32.dll!000007fefe83ca40() 	
 	shell32.dll!000007fefe79644f() 	
 	shell32.dll!000007fefe72d440() 	
 	shell32.dll!000007fefe679eca() 	
 	shell32.dll!000007fefe4ca9d8() 	
 	shell32.dll!000007fefe4ca8fe() 	
 	shell32.dll!000007fefe72e558() 	
 	shell32.dll!000007fefe67bee6() 	
 	shell32.dll!000007fefe5193da() 	
 	shell32.dll!000007fefe51ea91() 	
 	shell32.dll!000007fefe733640() 	
 	TOTALCMD64.EXE!00000000005696d3()
TOTALCMD64.EXE!00000000005696d3()
is different to the tooltip bug address:
TOTALCMD64.EXE!000000000055e62b()

Callstack(TC8.0b24 x64):

Code: Select all

>	PhotoMetadataHandler.dll!000007fef78ebfaf() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for PhotoMetadataHandler.dll]	
 	PhotoMetadataHandler.dll!000007fef78da919() 	
 	PhotoMetadataHandler.dll!000007fef78d50c9() 	
 	PhotoMetadataHandler.dll!000007fef78d5276() 	
 	PhotoMetadataHandler.dll!000007fef78d48bf() 	
 	PhotoMetadataHandler.dll!000007fef78d4bf7() 	
 	PhotoMetadataHandler.dll!000007fef78d44f8() 	
 	WindowsCodecs.dll!000007fefbe3537c() 	
 	PhotoMetadataHandler.dll!000007fef78d42b2() 	
 	PhotoMetadataHandler.dll!000007fef78d2de5() 	
 	PhotoMetadataHandler.dll!000007fef78d346a() 	
 	PhotoMetadataHandler.dll!000007fef78d3feb() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	shell32.dll!000007fefe535ae2() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d5c1e() 	
 	propsys.dll!000007fefc4d5b32() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d5c1e() 	
 	propsys.dll!000007fefc4d5b32() 	
 	propsys.dll!000007fefc4d4cc9() 	
 	propsys.dll!000007fefc4d4bb9() 	
 	propsys.dll!000007fefc4d4af1() 	
 	propsys.dll!000007fefc4d4a5e() 	
 	shell32.dll!000007fefe70a569() 	
 	shell32.dll!000007fefe796a7d() 	
 	shell32.dll!000007fefe83bcde() 	
 	shell32.dll!000007fefe83e262() 	
 	shell32.dll!000007fefe83c845() 	
 	shell32.dll!000007fefe83ca40() 	
 	shell32.dll!000007fefe79644f() 	
 	shell32.dll!000007fefe72d440() 	
 	shell32.dll!000007fefe679eca() 	
 	shell32.dll!000007fefe4ca9d8() 	
 	shell32.dll!000007fefe4ca8fe() 	
 	shell32.dll!000007fefe72e558() 	
 	shell32.dll!000007fefe67bee6() 	
 	shell32.dll!000007fefe5193da() 	
 	shell32.dll!000007fefe51ea91() 	
 	shell32.dll!000007fefe733640() 	
 	TOTALCMD64.EXE!0000000000569163()
The bug does not happen if you you use <Shift+Del> to permanently remove the file.

Regards
Holger

Edit:
This seems to be caused by the VistaDelete=1 confirmation dialog which normally shows some metadata from the file.
Last edited by HolgerK on 2012-03-30, 19:49 UTC, edited 1 time in total.
Top
umbra
Power Member
Power Member
Posts: 871
Joined: 2012-01-14, 20:41 UTC

Post by *umbra »

HolgerK wrote:This seems to be a complete different bug!
I wouldn't say it's a completely different bug, since it crashes on the same images, in the same .dll with the same error code, but let's say you are right. However I never noticed that it has nothing to do with a tooltip, because I usually delete files with mouse (means I have to point to that file).
Windows 7 Pro x64, Windows 10 Pro x64
Top
User avatar
HolgerK
Power Member
Power Member
Posts: 5406
Joined: 2006-01-26, 22:15 UTC
Location: Europe, Aachen

Post by *HolgerK »

2umbra
See my edit:

This seems to be caused by the VistaDelete=1 confirmation dialog which normally shows some metadata from the file.

Regards
Holger
Top
umbra
Power Member
Power Member
Posts: 871
Joined: 2012-01-14, 20:41 UTC

Post by *umbra »

2HolgerK
Yes, it makes sense.
Windows 7 Pro x64, Windows 10 Pro x64
Top
User avatar
karlchen
Power Member
Power Member
Posts: 4603
Joined: 2003-02-06, 22:23 UTC
Location: Germany

Crash on Delete Reproduced with T.C. 7.57a

Post by *karlchen »

---------------------------
Total Commander 7.57a
---------------------------
Access violation at address 00447AA2. Read of address 000000E4.
Access violation at address 00447AA2. Read of address 000000E4
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
00447AA2
423F50 4246FC 426B55 >423878 423878 425AA2
443F85 423878 445748 445A83 447AA0 443F85
445ED6 423878 445497 423878 428E96 428FDC
6CBD48
Raw:
423EDF 423F50 4243CF 4246FC 426B55 443F85
4461A5 425554 445EE2 423878 44624F 4260E5
44682D 443F85 4461A5 425554 445EE2 423878
425AA2 4269BA 443F85 4461A5 4260E5 425554
445EE2 423878 445748 4F0052 402235 4033BC
4021B4 4023DB 4026A4 4036AD 4452FE 6C8A1D
41D7B0 4458CE 445A83 44624F 443F85 4461A5
445559 4357D2 4F0052 420F8B 5C6135 420F8B
5C6135 42427C 425E4C 445C2A 447A8E 447AA0
64093C 445405 423878 44624F 402E36 443F85

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------
Reproduced the crash when trying to delete to the recycle bin using Total Commander 7.57.a.
So the crash on delete problem is not specific to T.C. 8.0ß24.

Also reproduced the crash by trying to delete to the recycle bin using Total Commander 8.0ß24 32-bit.
---------------------------
Total Commander 8.0ß24
---------------------------
Access violation at address 0044823A. Read of address 000000E4.
Access violation at address 0044823A. Read of address 000000E4
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0044823A
4244D8 424C84 4270DD >423E00 423E00 42602A
44471D 423E00 445EE0 44621B 448238 44471D
44666E 423E00 445C2F 423E00 42941E 429564
6D95C1
Raw:
424467 4244D8 424957 424C84 4270DD 44471D
44693D 425ADC 44667A 423E00 4469E7 42666D
446FC5 44471D 44693D 425ADC 44667A 423E00
42602A 426F42 44471D 44693D 42666D 425ADC
44667A 423E00 445EE0 5F004A 402235 4033BC
4021B4 4023DB 4026A4 4036AD 445A96 6D6285
41D98C 446066 44621B 4469E7 44471D 44693D
445CF1 435D5A 5F004A 421193 421193 424804
4263D4 4463C2 448226 448238 64A818 445B9D
423E00 4469E7 402E36 44471D 44693D 425ADC

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------
Do not get a crash when deleting the same image file to recycle bin inside Windows Explorer.

By the way, Free Commander 2009.2.0.417 simply freezes when trying to delete the same image file to the recycle bin. The "one ring to rule them all" (former Windows hour glass) is still spinning ... Yet, none of its thread shows any signs of activity, so it is just waiting for something to happen which never happens. (Just to show that T.C. is not alone.)

Karl
--
Windows 7 Enterprise SP1, 32-bit
Total Commander 7.57a
Total Commander 8.0ß24 32-bit
MX Linux 21.3 64-bit xfce, Total Commander 10.52 64-bit
The people of Alderaan keep on bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine.
The Prophet's Song
Top
User avatar
karlchen
Power Member
Power Member
Posts: 4603
Joined: 2003-02-06, 22:23 UTC
Location: Germany

Post by *karlchen »

HolgerK wrote:
29.03.12 Fixed: Some jpg files could cause an SSE floating point exception in Microsoft's PhotoMetadataHandler -> turn off SSE exceptions before each call to GetInfoTip (32/64)
Fix confirmed with TC8.0b24 x64
Confirmed by me, too. The original error, reported in this thread, has been fixed.

Total Commander 8.0ß24 64-bit
Windows 7 Home Premium SP1, 64-bit

Karl
MX Linux 21.3 64-bit xfce, Total Commander 10.52 64-bit
The people of Alderaan keep on bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine.
The Prophet's Song
Top
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48093
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:
Contact ghisler(Author)

Post by *ghisler(Author) »

Thanks for confirming the original bugfix! Indeed the delete error has nothing to do with it, it occurs also when going with the cursor keys to the file and pressing Delete. It seems to be caused by the Windows delete confirmation dialog, which tries to display the image (apparently with the same problematic dll)...
Author of Total Commander
https://www.ghisler.com
Top
Post Reply

Return to “TC Fixed bugs”