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

Jump to bottom

Run out of window handles #6550

Closed
cyberduck opened this issue Feb 20, 2012 · 17 comments
Closed

Run out of window handles #6550

cyberduck opened this issue Feb 20, 2012 · 17 comments
Assignees
@ylangisc
Labels
bug core high priority worksforme
Milestone
5.0

Comments

@cyberduck
Copy link
Collaborator

adee164 created the issue

When I attempt to upload or download a file, Cyberduck crashes. I have attached two crash reports for this problem.

Thank you for your help.

Attachments
@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Does this always happen or just after some time using Cyberduck?

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

In ed31575.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Additional fixes in 229bdbd, 0ad3afe, 5a52dd0, 5355011.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Refactor form create/dispose in f84c240.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8407 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#7733 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Caused by: cli.System.ComponentModel.Win32Exception: Error creating window handle.
2014-12-09 13:24:47,656 [background-3] ERROR AsyncController - Unhandled exception during invoke
cli.System.ComponentModel.Win32Exception: Error creating window handle.
	at cli.System.Windows.Forms.Control.MarshaledInvoke(Unknown Source)
	at cli.System.Windows.Forms.Control.Invoke(Unknown Source)
	at cli.Ch.Cyberduck.Ui.Controller.AsyncController.invoke(Unknown Source)
	at IKVM.Internal.ExceptionHelper.toString(Unknown Source)
	at java.lang.Throwable.toString(map.xml:1315)
	at java.lang.Object.toString(map.xml)
	at java.lang.StringHelper.valueOf(StringHelper.java:2390)
	at java.io.PrintWriter.println(PrintWriter.java:754)
	at java.lang.ThrowableHelper$WrappedPrintWriter.println(ThrowableHelper.java:343)
	at java.lang.ThrowableHelper.printStackTrace(ThrowableHelper.java:231)
	at java.lang.ThrowableHelper.printStackTrace(ThrowableHelper.java:300)
	at java.lang.Throwable.printStackTrace(map.xml:1188)
	at org.apache.log4j.DefaultThrowableRenderer.render(DefaultThrowableRenderer.java:60)
	at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:87)
	at org.apache.log4j.spi.LoggingEvent.getThrowableStrRep(LoggingEvent.java:413)
	at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:313)
	at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:277)
	at org.apache.log4j.WriterAppender.append(WriterAppender.java:163)
	at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:252)
	at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64)
	at org.apache.log4j.Category.callAppenders(Category.java:206)
	at org.apache.log4j.Category.forcedLog(Category.java:392)
	at org.apache.log4j.Category.error(Category.java:324)
	at cli.Ch.Cyberduck.Ui.Controller.AsyncController.invoke(Unknown Source)
	at cli.Ch.Cyberduck.Ui.Controller.WindowController.invoke(Unknown Source)
	at cli.Ch.Cyberduck.Ui.Controller.MainController.<ApplicationDidFinishLaunching>b__e(Unknown Source)
	at cli.Ch.Cyberduck.Ui.Controller.AsyncDelegateBackgroundAction.cleanup(Unknown Source)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable$1.run(AbstractController.java:206)
	at cli.Ch.Cyberduck.Ui.Controller.BaseController.invoke(Unknown Source)
	at ch.cyberduck.ui.AbstractController.invoke(AbstractController.java:64)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:202)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:58)
	at java.lang.Thread.run(Thread.java:937)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8334 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

1e47fb0 commented

Hi Ticket 8407 that has been marked as duplicate and added to this. Has a fix actually been found as I am no clearer to what the issue is or how to fix it.

Thanks

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:13 nick-necgroup]:

Hi Ticket 8407 that has been marked as duplicate and added to this. Has a fix actually been found as I am no clearer to what the issue is or how to fix it.

Thanks

No, we have no resolution yet for this.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8744 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8747 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8972 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#9008 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Try to remove all items from the transfer window. If you cannot open the Transfers window, remove the directory Transfers in the application support directory and restart Cyberduck.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#9084 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10996 closed as duplicate.

@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.
Assignees

@ylangisc ylangisc

Labels
bug core high priority worksforme
Projects
None yet
Milestone
5.0
Development

No branches or pull requests
2 participants
@ylangisc @cyberduck