-
Notifications
You must be signed in to change notification settings - Fork 198
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
pthreads and workers support #56
Comments
Hi, Currently i'm doing some maintenance on the SDK, you can find the fork here: Most of the thread impl. is in these files: I'll try to look more into it later.. |
I would start to enable the trace statements, so have some sense about the execution flow.. |
Also i think the whole implementation should be reviewed according to AS3 API updates. |
it looks like that the issue is quite old: |
Hi Well, I'm a little frustrated.
So even if I compile the C_Run.as file to ABC and somehow compile it into my SWF - how can I see the traces? Flash Scout maybe? Sorry for the stupid questions, but my tech background is really miles away from Flash and Windows. |
Some help for debugging SWFs:
|
Some help for building CrossBridge SDK from source:
|
Thanks so much for the help! |
Hi, After decompiling two different versions of the test program I've found out that the following statement causes the issue:
public static function startAsync
If I comment this out I can run the embedded SWCs I'll release soon a new version of CrossBridge here with the fix: Anyway some feedback from the previous maintainers would be awesome, why this change has been applied since Flascc (CrossBridge) 1.0.0
Reviewing the changelist from 1.0.1 this one is a candidate:
|
Hi, I've uploaded a release with the fix for the issue: |
Hi all,
I have recently encountered several issues with pthreads and workers in crossbridge. It looks like the pthreads/workers support is not 100% stable and becomes a pitfall for any seriouse efforts to port complex C++ code. I am basically a C++ specialist, so although I have a basic understanding of how the threads were implmeented (both from looking at source and forums), it's really hard for me to debug these issues in the crossbridge code.
I'm using Windows 8 64bit, Crossbridge 1.0.1, Flex 4.12.1, Flash debug player standalone 13.
In sample 09, pthread_swc2.swf - pthread_join causes deadlock, when running the main() on the UI wroker with startAsync() - you can try the original sample code.
In sample 09, after changing pthread_swc.as by Console.as (basically just running the main() in background worker) the main() works fine, however trying to call spawnThread() from UI events sometimes causes deadlock in pthread_join
And after I've removed the pthread_join(), it sometimes deadlocked in printf().
I will really appritiate any suggestions and will be glad to assist, as right now this is the major pitfall of our porting efforts.
Thanks!
The text was updated successfully, but these errors were encountered: