-
Notifications
You must be signed in to change notification settings - Fork 13
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
thread.fork errors #101
Comments
{ |
Maybe this will help: |
@wagne342 thanks -- I was able to fix the loading issue by statically linking the pthread library, so the object loads now, but it seems like it's not doing anything when I send messages in, so it will require some more attention. |
so the original issue is fixed, but on more testing there seems to be some funkiness in 64bit on Mac as well. On my system when sending a max message into thread fork the result is garbled when coming out of thread.join -- whereas it works fine in 32bit mode. on windows, in both bit modes, it loads now, but has no visible response when you send any input into thread.fork. |
also, sometimes it crashes in 64bit mode: Process: Max [749] Date/Time: 2018-01-25 22:13:45.916 +0100 Time Awake Since Boot: 64 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Signal: Segmentation fault: 11 VM Regions Near 0x1f73: Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread |
@ramagottfried
On Windows 64 thread.fork doesn't load properly. In the Max console we get:
error 126 loading external thread.fork
The text was updated successfully, but these errors were encountered: