Issue Reparenting NewtCanvasJFX

I've been able to use NewtCanvasJFX to successfully reparent a GLWindow to a JavaFX layout on Fedora, but the exact same code/configuration results in a crash on Win7 as soon as I attempt the "setNEWTChild" operation.

My Java build/runtime version is 1.8.0_181-b13, and I am using the "jogamp-next" deployment's "jogamp-all-platforms.7z" for the required libs/jars. [http://forums.jogamp.com/deployment/jogamp-next/archive/jogamp-all-platforms.7z]


Edit: Removed the super long JRE error log. It can be viewed in its entirety here: https://github.com/opcom/FX3D/blob/master/hs_err_pid5916.log


The "newt_head.dll" in question is bit-for-bit identical to the one found in the "jogamp-all-platforms.7z" archive, so it's not being copied from some other spurious location.

I have also completely disabled the Win7 UAC control, as recommended by various other sites as a possible workaround for the "Exception Access Violation", but have had no luck.

Any help would be greatly appreciated! Thanks!

I went ahead and uploaded the code to github in case anyone is interested: https://github.com/opcom/FX3D

If you import and build in Eclipse on Linux, it works perfectly.
If you import and build in Eclipse on Win7, it crashes. The produced error log is in the repo: https://github.com/opcom/FX3D/blob/master/hs_err_pid5916.log

Hopefully that sheds a bit more light on it.

Cheers.

Thank you for the windows testcase.
With your reproducer this can be fixed for the next jogamp release.

TODO list to make sure this issue is fixed for the next release:
1. open a bugreport to get a bug number
2. convert the testcase into a junit test with the bug number that can be automatically run that triggers the crash on the jogamp build and test infrastructure
3. the jogamp team can then look into it and fix it for the next jogamp jogl release

https://jogamp.org/wiki/index.php/Contributing_a_new_feature_or_fix

Bummer. I was hoping it was a misconfiguration or something on my end.

I originally intended to open a new bug for this but was unable to log into Bugzilla with my forum account, so I ended up posting here instead.
I'm more than happy to make the effort to ensure this can be used as a test case for future releases, so how should I go about creating a new bug report?
Anyone with access care to proxy for me? :)

Also, considering this might be low priority, and because I'm unaware of the current development timeline, is there nothing I  can do to try and fix this?
It seems like it could be way over my head, but I'm willing to take a crack at it.
Any pointers to relevant parts of the source or other debugging tips would be most welcome!

Thanks!

Send me an email and I'll create an account on bugzilla for you.