-
Notifications
You must be signed in to change notification settings - Fork 33
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
Debug Assertion Failed in File "xtree" #30
Comments
(And once more: Sorry for the delay...) This is not good... it looks like a basic, conceptual error of how a map is used at a certain point in the native code. I have to admit that I usually don't compile the DLL in debug mode, but I should definitely do this to catch more possible bugs. I'll have to take a closer look at this, maybe together with the update to OpenCL 3.0. |
Here's a look at the log file created when you press retry on the dialog above.A fatal error has been detected by the Java Runtime Environment: Internal Error (os_windows_x86.cpp:144), pid=11064, tid=0x000000000000333c JRE version: Java(TM) SE Runtime Environment (8.0_251-b08) (build 1.8.0_251-b08) If you would like to submit a bug report, please visit: --------------- T H R E A D --------------- Current thread (0x000000000279e800): JavaThread "main" [_thread_in_native, id=13116, stack(0x00000000025d0000,0x00000000026d0000)] Stack: [0x00000000025d0000,0x00000000026d0000] Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) --------------- P R O C E S S --------------- Java Threads: ( => current thread ) Other Threads: VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None heap address: 0x00000006c1000000, size: 4080 MB, Compressed Oops mode: Zero based, Oop shift amount: 3 Heap: Card table byte_map: [0x0000000011c60000,0x0000000012460000] byte_map_base: 0x000000000e658000 Marking Bits: (ParMarkBitMap*) 0x000000006024af90 Polling page: 0x0000000000ca0000 CodeCache: size=245760Kb used=2919Kb max_used=2919Kb free=242841Kb Compilation events (10 events): GC Heap History (0 events): Deoptimization events (0 events): Classes redefined (0 events): Internal exceptions (2 events): Events (10 events): Dynamic libraries: VM Arguments: Environment Variables: --------------- S Y S T E M --------------- OS: Windows 10.0 , 64 bit Build 18362 (10.0.18362.959) CPU:total 16 (initial active 16) (16 cores per cpu, 1 threads per core) family 23 model 8 stepping 2, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, avx, avx2, aes, clmul, mmxext, 3dnowpref, lzcnt, sse4a, tsc, tscinvbit, tscinv, bmi1 Memory: 4k page, physical 16708320k(10444664k free), swap 23986964k(12373800k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (25.251-b08) for windows-amd64 JRE (1.8.0_251-b08), built on Mar 12 2020 06:31:49 by "" with MS VC++ 10.0 (VS2010) time: Mon Sep 07 08:48:27 2020 |
Here's my Java class that produced the error; the code has some fluff in it, sorry. |
Thanks again, I'll have to allocate some time to try this out. I think it is due to a wrong usage of iterators in https://github.com/gpu/JOCLCommon/blob/master/src/main/native/CLJNIUtils.cpp#L792 (and a first guess would be that the |
Hello Marco, I was wondering how you deduced this conclusion. Was it from past experience with the JOCL you created, the log file, or testing you have already done? I am just trying to follow your thought process to learn something possibly. I already created an executable file from launch4j to debug the dll with, but I have not found any culprit yet. I have been busy with schoolwork and my girl. I have not looked in CLJNIUtils.cpp yet, but its true the JNI naming conventions are giving me a headache. I guess you get used to it after a while -- like the Matrix. |
Until now, it was only a guess, but ... the search space should be small: I think this is the only place where I'm using a value-initialized iterator at all. There's not much necessity to use actual C++-features in JOCL. In the end, OpenCL is plainly C-based. But the callbacks that may be associated with a CL context have to be maintained somehow, The |
This error has occurred to me while running various JOCL samples and my own code. I've deleted the lines that did the assertion, but the error still persisted afterwards. I have also restarted my computer after deleting the lines, and the same error occurred after restart. After uninstalling Visual Studio 2019 and thus all of the include files of MSCV including xtree, running the program causes this error. I wonder if the problem is somehow related to Eclipse? It is important to note that the kernel seems to run okay; its just this annoying error message pops up whenever I run the host program.
The text was updated successfully, but these errors were encountered: