-
Notifications
You must be signed in to change notification settings - Fork 10
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
Crash on MacOS when calling Clipboard.generalClipboard.clearData twice #3648
Comments
Hi Can you please double-check the version of AIR that you're using there? you're mentioning "AirSDK 51.1.3.1; AirSDK 32.0" - but the call stack doesn't match up to 51.1.3.1 from what we can see. Not sure why there's mention of AIR 32? Plus we'd need to know if it's running as arm64 (on Apple-silicon Mac) or x86_64 - I suspect the latter, looking at the instruction addresses, but it would be good to confirm that. And this only happens when you're calling a NativeProcess? We couldn't see any relevant use of thanks |
Hi @ajwfrost I've tested with both AirSDK 32 and AirSDK 51, the same issue happened. The call stack above is what I got from AirSDK 32. This is the call stack from AirSDK 51:
Sometimes I got the call stack from the debug console. Sometimes I see a popup dialog that contains the call stack. Sometimes the application just crash and exit with nothing to see at all. I've tested on two machine:
I don't know whether the issue happened when I called a NativeProcess API or not. But it must be related to NativeProcess API. Because it happened at the end of uploading (after uploading complete). And if I replace Currently it's not possible to share the application that I'm working with, because it's running through a VPN and using password. But I'll try to create a simple application to see if the issue happens with another server with no VPN connection. Thank you! |
Presumably that call stack was from the 14.0 Sonoma on the VM. If you're able to reproduce it on the M1, it would be good, and please confirm the full version code for the runtime. Call stacks with ARM code are a bit easier to analyse (RISC) rather than x86_64 (variable-width instructions..) The above doesn't look any different from the AIR 32 one; your call stack from the other issue looked different in some aspects, but the final part of the call stack (where it comes out of JIT code and then ends up with a few functions before the thanks |
Hi @ajwfrost Video_250118213217_Slice_Slice.mp4My application crashed at this line: Clipboard.generalClipboard.setData(ClipboardFormats.TEXT_FORMAT, text); the value of It's strange that the issue only happended at the second time of uploading. The first time of uploading, the value of And since I can connect to the debugger, I didn't see the crash stack call anymore. |
This simple code will cause the app crash on MacOS: Clipboard.generalClipboard.clearData(ClipboardFormats.TEXT_FORMAT);
Clipboard.generalClipboard.setData(ClipboardFormats.TEXT_FORMAT, "foo/123");
Clipboard.generalClipboard.clearData(ClipboardFormats.TEXT_FORMAT);
Clipboard.generalClipboard.setData(ClipboardFormats.TEXT_FORMAT, "bar/456"); // CRASH I'm sorry. You're right. This issue is not related to NativeProcess. When I use another tool, the issue did not happen because there's an error after uploading then the code above did not run. |
Thanks @ylazy - so the clipboard was one of those few locations in the code where I think the call to create the mutable array in the first place is wrong i.e. despite being a function call on the FYI it's the thanks |
Yes my app does not crash anymore if I only call Thank you! |
Problem Description
Describe your problem in detail. Include the following information:
Steps to Reproduce
I'm using curl to upload some files to a server. I'm using
NativeProcess
to do the job.It's fine at the first time of uploading.
When I repeat that (the second time of uploading), my application exit (crash). Sometime it also happens at the first time of uploading.
This is the log:
If I manually run curl commands via Terminal or PowerShell multiple times, everything is ok.
What should I do now?
Thanks!
The text was updated successfully, but these errors were encountered: