[SERVER-51256] Improve truncated deep backtraces Created: 30/Sep/20  Updated: 21/Mar/23

Status: Backlog
Project: Core Server
Component/s: Diagnostics, Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Service Arch
Participants:

 Description   

HELP-18938 deals with an infinite recursion. It's hard to diagnose because we only log the boring repetitive top of the stack, not the exciting bottom where the trouble started.

Is it a mistake to truncate the backtrace in deep traces to the 100 top frames like this? I feel like we would be in a better position if we did something to show the bottom of the stack as well.

Maybe we can add auxilliary elements to the "bt" json document to help. Display the 100 bottom frames, which would show where the recursion started, and show how many frames there were in total.



 Comments   
Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ]

We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:24:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.