3D Adaptive encounters Internal Errors - closecrossovers too extreme - then throws unhandled exception

3D Adaptive encounters Internal Errors - closecrossovers too extreme - then throws unhandled exception

tlum08619
Participant Participant
413 Views
5 Replies
Message 1 of 6

3D Adaptive encounters Internal Errors - closecrossovers too extreme - then throws unhandled exception

tlum08619
Participant
Participant

3D Adaptive encounters Internal Errors - closecrossovers too extreme - then throws unhandled exception.

 

Feature flags: machine-space-geometry-simulator setup-sheet-viewer simulation-overtravel-reporting

Debug: Initialization elapsed time: 0 ms

Debug: Writing ironjob to C:\Users\TEDLUM~1\AppData\Local\Temp\Fusion360CAM\17644-1\operation17.ironjob

Debug: Writing jobfile to C:\Users\TEDLUM~1\AppData\Local\Temp\Fusion360CAM\17644-1\operation17.hsm-job

Debug: Using CAM kernel from: C:\Users\Ted Lum\AppData\Local\Autodesk\webdeploy\production\3167d85f5fd4280287d8295f20592fa13b977617\Applications\CAM360\camkernel.exe

Error: Internal error.

Error: Internal error.

Error: Internal error.

Error: Internal error - closecrossovers too extreme

Error: An unhandled exception occured 0xffffffff.

Error state stored at 'C:\Users\TEDLUM~1\AppData\Local\Temp\camkernel\camkernel-20648.dmp'.

Debug: Autodesk dcamcomponents 1.214.1 pm12847
Autodesk CAM Kernel 3.152.2 (0187c77b) x64 STABLE vs2022 0187c77bd98665c07439c1f3445f0bf71d233b90 2023/11/03 14:00
Internal error 'bwfibgood' failed at E:\Jenkins\CAMKernel\freesteel\freesteel/GenWeaveTempl.h:135 (#1).
Autodesk dcamcomponents 1.214.1 pm12847
Autodesk dcamcomponents Autodesk dcamcomponents 1.1214..2141. 1pm 12847pm
12847
Autodesk dcamcomponents 1.214.1 pm12847
Internal error 'bwfibgood' failed at E:\Jenkins\CAMKernel\freesteel\freesteel/GenWeaveTempl.h:135 (#3).
Error: class std::runtime_errorInternal error 'bwfibgood' failed at E:\Jenkins\CAMKernel\freesteel\freesteel/GenWeaveTempl.h:135 (#3).: 
Internal error (see statement in log).
Error: Error: concurrent job failed for worker class std::runtime_error: Error: class std::runtime_error: 1.Internal error (see statement in log).

Internal error (see statement in log).
Error: concurrent job failed for worker 0Error: concurrent job failed for worker .2
.
Internal error 'closecrossovers too extreme' for expression '0' failed at E:\Jenkins\CAMKernel\freesteel\freesteel\fsimplicitarea.cpp:1551 (#1).
Internal error (see statement in log)., -1
  File "lib\threading.py", line 973, in _bootstrap
  File "lib\threading.py", line 1016, in _bootstrap_inner
  File "lib\roughsteel\ZLevelsClass.py", line 1279, in run
  File "lib\roughsteel\ZLevelsClass.py", line 1302, in Lrun
  File "lib\roughsteel\ZLevelsClass.py", line 955, in FirstZDown
  File "lib\roughsteel\ZLevelsClass.py", line 549, in MakeZSliceInflex
  File "lib\roughsteel\ZLevelsClass.py", line 563, in MakeZSlice
  File "lib\roughsteel\ZLevelsClass.py", line 769, in MakeZSliceFromSurf
  File "lib\hsmkernel\hsmkernelPython.py", line 1995, in GenWeaveZProfile

Error: An unhandled exception occured 0xffffffff.

Debug: Total processing time: 718 ms

Debug: Total elapsed time: 1136 ms

Invalidated: Generation failed

close 

0 Likes
414 Views
5 Replies
Replies (5)
Message 2 of 6

tlum08619
Participant
Participant

This had been working in .v3 but started throwing the exception in .v4. I just managed to figure out how I broke it.

3DAdaptive.png

Change Top Height from Stock Top (works [.v3]) to Model Top (throws exception [.v4])

0 Likes
Message 3 of 6

popaa
Autodesk
Autodesk

Hi @tlum08619 ,

 

Thank you for providing an example. I created ticket CAM-49849 .

 

Regards,

Aurelia


Aurelia Popa Nielsen
SW Development Engineer
Message 4 of 6

tlum08619
Participant
Participant

Why do bug reports not belong in the support forum?

0 Likes
Message 5 of 6

seth.madore
Community Manager
Community Manager

Since it's a CAM issue, it will have better visibility in the CAM forum.

The Support forum is LONG overdue in its description getting updated. It's intended to be the bucket for installation, crashing, license, login etc etc


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 6 of 6

tlum08619
Participant
Participant

I think this is splitting hairs: "Unhandled Exception" is an explicit technical term, colloquially called "crashing", when a running process quits due to an unexpected and unhandled fatal error in a called function. The post literally has the "crash dump" file attached for the developers to explore in a debugger.  So, even your explanation is contradicting you... unless you're looking to differentiate "CAM Crashing" and "non-CAM Crashing".

0 Likes