Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes with CLR20r3 problem event name #8334

Closed
cyberduck opened this issue Nov 17, 2014 · 10 comments
Closed

Crashes with CLR20r3 problem event name #8334

cyberduck opened this issue Nov 17, 2014 · 10 comments

Comments

@cyberduck
Copy link
Collaborator

70c68d7 created the issue

Hi Cyberduck Support:

I've installed the new version...it worked for a while and then it keeps on crashing again.
Please advise.

Thank you.

------------------------
Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	cyberduck.exe
  Problem Signature 02:	4.5.2.15058
  Problem Signature 03:	53fc8695
  Problem Signature 04:	Cyberduck
  Problem Signature 05:	4.5.2.15058
  Problem Signature 06:	53fc8695
  Problem Signature 07:	176b
  Problem Signature 08:	2de
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Previously reported in #8298.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Please check if there are any crash reports available and attach them.

@cyberduck
Copy link
Collaborator Author

70c68d7 commented

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	cyberduck.exe
  Problem Signature 02:	4.5.2.15058
  Problem Signature 03:	53fc8695
  Problem Signature 04:	Cyberduck
  Problem Signature 05:	4.5.2.15058
  Problem Signature 06:	53fc8695
  Problem Signature 07:	176b
  Problem Signature 08:	2de
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

That's what you've already posted. I mean, can you find any file in C:\Users\[username]\AppData\Roaming\Cyberduck\CrashReporter?

@cyberduck
Copy link
Collaborator Author

70c68d7 commented

Sorry. I did not find any crash report? and did not see C:\Users\[username]\AppData\Roaming\Cyberduck\CrashReporter? I saw C:\Users\[username]\Roaming\Intel\Wireless.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

That seems to be the wrong location. To easily find the Cyberduck AppData folder you can run the command %APPDATA%\cyberduck by pressing the Start button and the choose Run... After pressing OK an Explorer window should open showing the Cyberduck settings folder. From there you can navigate to the CrashReporter folder.

@cyberduck
Copy link
Collaborator Author

70c68d7 commented

Hi yla,

Thank you for providing the instruction in retrieving the crash report. Please see attachment for reference.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Thanks for providing the crash report. We are aware of this issue but it's pretty rare and we were unable yet to find the cause. Will need some more investigation.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Top-level Exception
Type:        System.Runtime.InteropServices.COMException
Message:     The current process has used all of its system allowance of handles for Window Manager objects. (Exception from HRESULT: 0x80070486)
Source:      Cyberduck
Stack Trace: at Ch.Cyberduck.Ui.Winforms.Taskdialog.VistaUnsafeNativeMethods.TaskDialogIndirect(TASKDIALOGCONFIG& pTaskConfig, Int32& pnButton, Int32& pnRadioButton, Boolean& pfVerificationFlagChecked)
   at Ch.Cyberduck.Ui.Winforms.Taskdialog.VistaTaskDialog.PrivateShow(IntPtr hwndOwner, Boolean& verificationFlagChecked, Int32& radioButtonResult)
   at Ch.Cyberduck.Ui.Winforms.Taskdialog.VistaTaskDialog.Show(IWin32Window owner, Boolean& verificationFlagChecked, Int32& radioButtonResult)
   at Ch.Cyberduck.Ui.Winforms.Taskdialog.TaskDialog.ShowTaskDialogBox(IWin32Window Owner, String Title, String MainInstruction, String Content, String ExpandedInfo, String Footer, String VerificationText, String RadioButtons, String CommandButtons, TaskDialogButtons Buttons, SysIcons MainIcon, SysIcons FooterIcon, Int32 DefaultIndex)
   at Ch.Cyberduck.Ui.Winforms.Taskdialog.TaskDialog.ShowTaskDialogBox(IWin32Window Owner, String Title, String MainInstruction, String Content, String ExpandedInfo, String Footer, String VerificationText, String RadioButtons, String CommandButtons, TaskDialogButtons Buttons, SysIcons MainIcon, SysIcons FooterIcon)
   at Ch.Cyberduck.Ui.Winforms.Taskdialog.TaskDialog.ShowCommandBox(IWin32Window Owner, String Title, String MainInstruction, String Content, String ExpandedInfo, String Footer, String VerificationText, String CommandButtons, Boolean ShowCancelButton, SysIcons MainIcon, SysIcons FooterIcon)
   at Ch.Cyberduck.Core.CrashReporter.Write(Exception e)
   at Ch.Cyberduck.Ui.Controller.MainController.ExceptionHandler(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(ApplicationContext context)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
   at Ch.Cyberduck.Ui.Controller.MainController.Run(ICollection commandLineArgs)
   at Ch.Cyberduck.Ui.Controller.MainController.Run()
   at Ch.Cyberduck.Ui.Controller.MainController.Main()

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #6550.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant