Upgraded to V 12, route calculation stops at 39% and crashes device

Made new profile where is nothing IQ related. Now those problematic courses will calculate fully, but only when using Garmin own maps, same crash happens at 39% with non garmin OSM maps. Looks like somekind memory handling issue with new firmware.

Good thing is that seems to be so that if I calculate route with this dummy profile and garmin maps, I van use this cached route with my real profile with all IQ fields.

As long as you stay strictly on course, yes.
Worse, if you deviate from the course and Edge recalculates the detour to the rest of the route (in the cache).

I can't quite agree with the CIQ problems - I use the maximum amount of CIQ (10) and I don't have any problems. If I am not mistaken, the memory for IQ is a dedicated Edge memory and is not used by the system for other purposes.

Even using only the garmine maps, you can see a break when recalculating 39%. There must be something to it that with certain user maps, Edge is unable to proceed with recalculation. Have you checked the log what are the errors?

This recalculation is no issue for my case, as I dont allow (never have allowed) recalculations to happen.

this is one of the errror logs:

[
{
"unit_id":"3318131232",
"product_name":"Edge 1030",
"software_part_number":"006-B2713-00",
"ms_since_epoch":1624082676000,
"system_version":"12.00",
"build_type":"PRODUCTION",
"backtrace":"NAV main - Error type ( 1 ) err( 6E5D800F )",
"error_cause":"RTL Trap",
"proprietary_info":{
"Commit ID":"6e1e774cfcf853d988042dd4031380aa2d37768c",
"Time":"2021-6-19 9:4:36",
"Project Specific":"2021-6-19 9:4:36",
"CDP_LOG":"3C91D,567229,560B09,3B2F49,31D489,3B2F49,1E74F5,200619,28A4F1,28A0B1,28A4F1,28A0B1,28A4F1,28A4F1,28A4F1,28A0B1,28A4F1,28A4F1,28A4F1,28A4F1,28A4F1,28A0B1,28A4F1,28A0B1,28A4F1,200619,1E74F5,3EDC1D,3EDC1D,32C159,5644E1,32C159,32C159,5644E1,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,219E05,28A0B1,219E05,219E05,32C159,2C008D,1E74F5,26C719,27E85D,29A641,3A548D,30826D,3A548D,38FD39,3EDC1D,2C008D,1E74F5,200605,1E74F5,2BFD79,1E74F5,3EDC1D,2C008D,1E74F5,3EDC1D,2C008D,3EDC1D,2ABF09,3EDC1D,32C159,219E05,32C159,",
"RTL Error Number":"6E5D800F",
"Error Message":"DFFF3F68,0025084F,002F1228,00001B2A,013F3AB4",
"Task Name":"NAV main",
"Saved SP":"DFFF1A18",
"Saved LR":"0011454D",
"Saved PC":"0042D09A",
"R[0]":"DFFF3F68",
"R[1]":"0025084F",
"R[2]":"002F1228",
"R[3]":"00001B2A",
"R[4]":"013F3AB4",
"R[5]":"00000000",
"R[6]":"00000000",
"R[7]":"00000000",
"R[8]":"00000000",
"R[9]":"00000000",
"R[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000000",
"R[14]":"00000000",
"R[15]":"00000000",
"cpsr":"00000000"
}

},
{
"unit_id":"3318131232",
"product_name":"Edge 1030",
"software_part_number":"006-B2713-00",
"ms_since_epoch":1624097353000,
"system_version":"12.00",
"build_type":"PRODUCTION",
"backtrace":"
Function Address: 0x0042D08A
Call Address at Function: 0x0042D09A

Function Address: 0x0049C710
Call Address at Function: 0x0049C72E

Function Address: 0x0042B29C
Call Address at Function: 0x0042B2EC

",
"error_cause":"RTL Trap",
"proprietary_info":{
"Commit ID":"6e1e774cfcf853d988042dd4031380aa2d37768c",
"Time":"2021-6-19 13:9:13",
"Project Specific":"2021-6-19 13:9:13",
"CDP_LOG":"EDC1D,32C159,32C159,5644E1,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,5644E1,32C159,219E05,32C159,5644E1,5644E1,5644E1,32C159,5644E1,32C159,5644E1,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,5644E1,32C159,5644E1,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,32C159,32C159,32C159,3EDC1D,32C159,32C159,5644E1,32C159,5644E1,32C159,5644E1,32C159,5644E1,32C159,219E05,55DCC5,33C91D,567229,5671BD,560B09,3B2F49,31D489,3B2F49,1E74F5,200619,1E74F5,2BFD79,55AC71,",
"RTL Error Number":"6E5D8017",
"Error Message":"01DFF6F0,0042B3A8,000000DA,0042B398",
"Task Name":"CDP io",
"Saved SP":"01DFF690",
"Saved LR":"0049C72F",
"Saved PC":"0042D09A",
"R[0]":"01DFF6F0",
"R[1]":"0042B3A8",
"R[2]":"000000DA",
"R[3]":"0042B398",
"R[4]":"00000000",
"R[5]":"00000000",
"R[6]":"00000000",
"R[7]":"00000000",
"R[8]":"00000000",
"R[9]":"00000000",
"R[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000000",
"R[14]":"00000000",
"R[15]":"00000000",
"cpsr":"00000000"
}

}
]

Send to Garmina, have them work on fixing the bug.

From the Edge beta file:

Form for Reporting Feedback

Please complete this form and attach it in an email to [email protected].

1. Title of Case (Subject Line): Best Condensed Explanation (Title) of Error, Feature or Question

2. Device and Version of Software: Include device name (Edge 1030) and version number (i.e. 11.24).

3. Computer/Phone: Type of computer you are using if it is a Garmin Connect or Garmin Express issue. Type of phone you are using including the phone OS version (i.e. iOS 11.1 or Android 8.0)

4. Category: Bug (Error), Improvement, or Inquiry (Question)

5. Description: Type the best description of what you’re reporting or requesting. Include as much information as possible about the issue.
a. What is the date of the crash?
b. What is the current behavior and what is the expected behavior?
c. Can you reproduce the behavior? If so, please list the steps.
d. Did your device freeze or shutdown? If so, are there any error reports you can provide?
e. Were you using any accessories? If so, which ones? If you were using a power meter, what type?
f. GPS on or off?
g. Wi-Fi on or off?
h. Were you running a course and/or a segment? If so, please attach your course, segments, and activity file.
i. Were you running a workout? If so, please attach your workout and activity file.
j. Were you recording an activity (i.e. was the timer running)? If so, please attach your activity file.
k. What page were you on when you encountered the issue?
l. Photos and videos of the screen showing the issue are always helpful!
m. The better the description the faster we will be able to track it down and fix it OR the faster we may be able to add it/change it.

6. Attach a file(s):
• If you get a photo of the issue, please attach to the e-mail. If you get a video of the issue, please provide a link.
• If you have issues with a course, segment, workout, or activity recording, please be sure to attach the activity file plus the course/segment/workout files as well. This will be in the Garmin/Activity, Garmin/Courses, Garmin/Segments, or Garmin/Workouts folder.
• If you have a shutdown on your device, we will want to have the error log associated with the shutdown. Error logs are stored on the Edge in a file called err_log.txt in the Garmin/Debugging folder.

Ok, I checked the recalculation with VeloMap. Polish routes, even very long ones - no problem. Your route on the Finland map, of course, only comes to 39%, whether it's downloaded via CIQ or Connect.
By the way, when downloading via CIQ, I got a message about the exceeded number of course points (over 200), although it does not matter, because loaded via Connect had no additional points (turns, etc.), and the recalculation did not exceed 39%.

Maybe some map routing bug that the current FW can't deal with?

I was experiencing this error as well, it was intermittent initially, but in the last couple of days grew so bad that I couldn't get any route to work.

Per recommendation of @hotdogsausageparty I deselected all options fro "avoidance" and disabled the "popularity routing." This did NOT resolve the issue. In frustration I changed the activity profile, and route calculation worked, and in a matter of seconds had calculated the route completely, as opposed to minutes as had been the previous case on v12.00 and all versions before. I deleted the profile which was giving the error, rebuilt it, and now the routing works and is still super fast on calculation, seconds not minutes.

I suspect that the issue for me, and for others, is some sort of corruption in the activity profile, because once the profile was changed the issue went away, and the rebuilt profile is behaving as expected. Bottomline: the firmware does NOT appear to the issue.

I have done full reset to my device (cleared everything) and that maybe solved the problems with this calculation error with Garmin own maps, but still if using 3rd party maps, I have device crash even with this latest beta 12.14 firmware. 

I wonder if there is some kind conflict between the popularity layer/routing & non Garmin maps.

I did spot something yesterday that I hadn't spotted before, there's a setting in routing to use popularity routing but there's also a setting in maps for sowing the popularity layer

@pertti_s and @hotdogsausageparty, I can't speak to the 3rd party maps, because I use the Garmin maps. But, I may give it a shot later today, to test the theory. I'll report the results then. Definitely, my issues (with the Garmin maps) have resolved by deleting what I suspect was a corrupt activity profile and rebuilding it.