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

Clipboard access/application focus crash. #2183

oceanhahn opened this issue Oct 17, 2019 · 2 comments

Clipboard access/application focus crash. #2183

oceanhahn opened this issue Oct 17, 2019 · 2 comments


Copy link

@oceanhahn oceanhahn commented Oct 17, 2019

ASEprite crashes when receiving focus after tabbing-away. I have not been able to isolate or deliberately reproduce this bug, but it has happened unpredictably on multiple occasions. Here is what I know:

  • There has been an active selection in the Workspace (possibly uncommitted paste data; not sure).
  • There has been data in the Clipboard (text, on at least one occasion).
  • ASEprite hung for a few seconds after gaining focus and before displaying an error, Cannot access to the clipboard. Maybe other application is using it. (clipboard_access_locked) It hung for a few seconds after "OK" was pressed, lighting that button but not closing the error pane, before crashing to Desktop.
  • Every time this has happened, it has been after ASE has been running for a rather long time without exit or restarting. Some kind of memory allocation problem, perhaps?

If there are more details I can provide, please let me know. I will submit a crash log by email in reference to this issue.

I hope that this helps! :D
..using ASEprite 1.2.15-x86 on Win10.

@dacap dacap added the bug label Oct 18, 2019
@dacap dacap added this to the v1.x-bugs milestone Oct 18, 2019
@dacap dacap self-assigned this Nov 20, 2019

This comment has been minimized.

Copy link

@dacap dacap commented Nov 26, 2019

Hi @oceanhahn, I saw that you reported this problem like using Aseprite 1.2.15-x86, and the crash is from an Aseprite 1.2.15-x64 in the email, so I guess this problem is related to a fix in this commit:



This comment has been minimized.

Copy link

@oceanhahn oceanhahn commented Nov 28, 2019

x64, sorry. I am 97% sure I am running x64.
I am not sure how I made that mistake; I suppose I will have to confirm my version next time I am at my desk. x_x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.