Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Main application (v2.0.27.0) crashes on startup (during splash screen) if launched when 2 cameras (Canon 70D) are already connected by USB.
Workaround is to connect seconds camera after application starts. Both cameras work fine after that.
Have not tested with other cameras or with more then 2 cameras.
Note: that when a 70D is connected a photo of the camera is NOT displayed in the bottom left, as with other cameras such as 600D. Not sure if this could somehow be related to this crash or not.
OS: Windows 7 64-bit
Crash details:
"digiCamControl is not responding"
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: CameraControl.exe
Application Version: 2.0.27.0
Application Timestamp: 572dcb2c
Hang Signature: e5ed
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: e5eddac24f21a408bd937ee89faed25c
Additional Hang Signature 2: d184
Additional Hang Signature 3: d18429911c39093fb8fd3682299d6911
Additional Hang Signature 4: e5ed
Additional Hang Signature 5: e5eddac24f21a408bd937ee89faed25c
Additional Hang Signature 6: d184
Additional Hang Signature 7: d18429911c39093fb8fd3682299d6911
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
app.log details:
2016-05-16 04:28:48,654 [1]DEBUG DCC [(null)] - --------------------------------===========================Application starting===========================--------------------------------
2016-05-16 04:28:48,669 [1]DEBUG DCC [(null)] - Application version : 2.0.27.0
2016-05-16 04:28:48,670 [1]DEBUG DCC [(null)] - Init : Analytics
2016-05-16 04:28:48,682 [1]DEBUG DCC [(null)] - Init : DeviceManager
2016-05-16 04:28:48,683 [1]DEBUG DCC [(null)] - Init : ExternalDeviceManager
2016-05-16 04:28:48,685 [1]DEBUG DCC [(null)] - Init : Trigger
2016-05-16 04:28:48,686 [1]DEBUG DCC [(null)] - Init : QueueManager
2016-05-16 04:28:48,690 [1]DEBUG DCC [(null)] - Init : ScriptManager
2016-05-16 04:28:48,693 [1]DEBUG DCC [(null)] - Init : PluginManager
2016-05-16 04:28:48,695 [1]DEBUG DCC [(null)] - Init : _pipeServer
2016-05-16 04:28:49,023 [1]DEBUG DCC [(null)] - Logo file not foundC:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\logo.png
2016-05-16 04:28:49,024 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\CameraControl.Plugins.dll
2016-05-16 04:28:49,912 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\Plugin.DeviceControlBox\Plugin.DeviceControlBox.dll
2016-05-16 04:28:56,232 [1]DEBUG DCC [(null)] - New canon camera found !
2016-05-16 04:28:56,235 [1]DEBUG DCC [(null)] - Pas 1
2016-05-16 04:28:56,235 [1]DEBUG DCC [(null)] - Pas 2
2016-05-16 04:28:56,771 [1]ERROR DCC [(null)] - Canon error
Canon.Eos.Framework.EosPropertyException: Properties Unavailable.
Failed to get property integer data: propertyId 1042
at Canon.Eos.Framework.Helper.Util.Assert(UInt32 result, String message, UInt32 propertyId, Object propertyValue) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\Helper\Util.cs:line 40
at Canon.Eos.Framework.EosObject.<>c__DisplayClassb.<GetPropertyIntegerData>b__a() in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosObject.cs:line 179
at Canon.Eos.Framework.EosObject.ExecuteGetter[TResult](Func`1 function) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosObject.cs:line 127
at Canon.Eos.Framework.EosCamera.ExecuteGetter[TResult](Func`1 function) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosCamera.cs:line 308
2016-05-16 04:28:56,775 [1]DEBUG DCC [(null)] - Pas 3
2016-05-16 04:28:56,776 [1]DEBUG DCC [(null)] - Pas 4
2016-05-16 04:28:56,776 [1]DEBUG DCC [(null)] - Pas 5
2016-05-16 04:28:56,777 [1]DEBUG DCC [(null)] - ===========Camera is connected==============
2016-05-16 04:28:56,777 [1]DEBUG DCC [(null)] - Driver :CanonSDKBase
2016-05-16 04:28:56,778 [1]DEBUG DCC [(null)] - Name :Canon EOS 70D
2016-05-16 04:28:56,778 [1]DEBUG DCC [(null)] - Manufacturer :Canon Inc.
2016-05-16 04:28:56,780 [1]DEBUG DCC [(null)] - DeviceManager_CameraSelected 1
2016-05-16 04:28:56,780 [1]DEBUG DCC [(null)] - DeviceManager_CameraSelected 2
2016-05-16 04:28:56,787 [1]DEBUG DCC [(null)] - New canon camera found done!
2016-05-16 04:28:56,788 [1]DEBUG DCC [(null)] - New canon camera found !
2016-05-16 04:28:56,788 [1]DEBUG DCC [(null)] - Pas 1
2016-05-16 04:28:56,789 [1]DEBUG DCC [(null)] - Pas 2
2016-05-16 04:28:56,975 [14]DEBUG DCC [(null)] - cameraDevice_CameraInitDone 1
Workaround is to connect seconds camera after application starts. Both cameras work fine after that.
Have not tested with other cameras or with more then 2 cameras.
Note: that when a 70D is connected a photo of the camera is NOT displayed in the bottom left, as with other cameras such as 600D. Not sure if this could somehow be related to this crash or not.
OS: Windows 7 64-bit
Crash details:
"digiCamControl is not responding"
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: CameraControl.exe
Application Version: 2.0.27.0
Application Timestamp: 572dcb2c
Hang Signature: e5ed
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Hang Signature 1: e5eddac24f21a408bd937ee89faed25c
Additional Hang Signature 2: d184
Additional Hang Signature 3: d18429911c39093fb8fd3682299d6911
Additional Hang Signature 4: e5ed
Additional Hang Signature 5: e5eddac24f21a408bd937ee89faed25c
Additional Hang Signature 6: d184
Additional Hang Signature 7: d18429911c39093fb8fd3682299d6911
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
app.log details:
2016-05-16 04:28:48,654 [1]DEBUG DCC [(null)] - --------------------------------===========================Application starting===========================--------------------------------
2016-05-16 04:28:48,669 [1]DEBUG DCC [(null)] - Application version : 2.0.27.0
2016-05-16 04:28:48,670 [1]DEBUG DCC [(null)] - Init : Analytics
2016-05-16 04:28:48,682 [1]DEBUG DCC [(null)] - Init : DeviceManager
2016-05-16 04:28:48,683 [1]DEBUG DCC [(null)] - Init : ExternalDeviceManager
2016-05-16 04:28:48,685 [1]DEBUG DCC [(null)] - Init : Trigger
2016-05-16 04:28:48,686 [1]DEBUG DCC [(null)] - Init : QueueManager
2016-05-16 04:28:48,690 [1]DEBUG DCC [(null)] - Init : ScriptManager
2016-05-16 04:28:48,693 [1]DEBUG DCC [(null)] - Init : PluginManager
2016-05-16 04:28:48,695 [1]DEBUG DCC [(null)] - Init : _pipeServer
2016-05-16 04:28:49,023 [1]DEBUG DCC [(null)] - Logo file not foundC:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\logo.png
2016-05-16 04:28:49,024 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\CameraControl.Plugins.dll
2016-05-16 04:28:49,912 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\Plugin.DeviceControlBox\Plugin.DeviceControlBox.dll
2016-05-16 04:28:56,232 [1]DEBUG DCC [(null)] - New canon camera found !
2016-05-16 04:28:56,235 [1]DEBUG DCC [(null)] - Pas 1
2016-05-16 04:28:56,235 [1]DEBUG DCC [(null)] - Pas 2
2016-05-16 04:28:56,771 [1]ERROR DCC [(null)] - Canon error
Canon.Eos.Framework.EosPropertyException: Properties Unavailable.
Failed to get property integer data: propertyId 1042
at Canon.Eos.Framework.Helper.Util.Assert(UInt32 result, String message, UInt32 propertyId, Object propertyValue) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\Helper\Util.cs:line 40
at Canon.Eos.Framework.EosObject.<>c__DisplayClassb.<GetPropertyIntegerData>b__a() in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosObject.cs:line 179
at Canon.Eos.Framework.EosObject.ExecuteGetter[TResult](Func`1 function) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosObject.cs:line 127
at Canon.Eos.Framework.EosCamera.ExecuteGetter[TResult](Func`1 function) in d:\devel\vs2010\CameraControl\Canon.Eos.Framework\EosCamera.cs:line 308
2016-05-16 04:28:56,775 [1]DEBUG DCC [(null)] - Pas 3
2016-05-16 04:28:56,776 [1]DEBUG DCC [(null)] - Pas 4
2016-05-16 04:28:56,776 [1]DEBUG DCC [(null)] - Pas 5
2016-05-16 04:28:56,777 [1]DEBUG DCC [(null)] - ===========Camera is connected==============
2016-05-16 04:28:56,777 [1]DEBUG DCC [(null)] - Driver :CanonSDKBase
2016-05-16 04:28:56,778 [1]DEBUG DCC [(null)] - Name :Canon EOS 70D
2016-05-16 04:28:56,778 [1]DEBUG DCC [(null)] - Manufacturer :Canon Inc.
2016-05-16 04:28:56,780 [1]DEBUG DCC [(null)] - DeviceManager_CameraSelected 1
2016-05-16 04:28:56,780 [1]DEBUG DCC [(null)] - DeviceManager_CameraSelected 2
2016-05-16 04:28:56,787 [1]DEBUG DCC [(null)] - New canon camera found done!
2016-05-16 04:28:56,788 [1]DEBUG DCC [(null)] - New canon camera found !
2016-05-16 04:28:56,788 [1]DEBUG DCC [(null)] - Pas 1
2016-05-16 04:28:56,789 [1]DEBUG DCC [(null)] - Pas 2
2016-05-16 04:28:56,975 [14]DEBUG DCC [(null)] - cameraDevice_CameraInitDone 1
Last edited by Serge on Sun May 15, 2016 10:01 pm, edited 2 times in total.
-
- Posts: 684
- Joined: Sat Oct 03, 2015 7:57 pm
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Please send your log file Menu=>Help=>Send log file
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Log details added to post, full Log also sent.
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Was this ever resolved I need the same assistance
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Still an issue in 2.0.72
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
I'm getting the same error in 2.0.72 unfortunately. Connecting the second camera after launch seems to work, but then it crashes after a few minutes of capturing on both cameras.
Event viewer error is:
I've sent the logs in.
Event viewer error is:
Code: Select all
Faulting application name: CameraControl.exe, version: 2.0.72.0, time stamp: 0x58cd35f0
Faulting module name: PresentationFramework.ni.dll, version: 4.7.2053.0, time stamp: 0x58fa72d3
Exception code: 0xc00000fd
Fault offset: 0x003588ab
Faulting process id: 0x16e8
Faulting application start time: 0x01d2ee63bb480788
Faulting application path: C:\Program Files (x86)\digiCamControl\CameraControl.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\1d3239102d5b94204fc5f9cb4289f4a6\PresentationFramework.ni.dll
Report Id: 88fdfd22-5a57-11e7-8798-b8ca3a8b86b5
-
- Posts: 684
- Joined: Sat Oct 03, 2015 7:57 pm
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
For Canon cameras if you experience program hang on startup, start the application without connected cameras, go to File->Settings->Advanced and uncheck the Load Canon transfer mode
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
I tried that but it didn't seem to make much of a difference. I donated a couple of years back though and got the branding info, and what does work is to disable the startup screen.
Love your work!
Love your work!
-
- Posts: 684
- Joined: Sat Oct 03, 2015 7:57 pm
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
For a updated branding please contact me at admin@digicamcontrol.com