As a Roblox developer, it is currently too hard to determine what engine system lead to a crash, making crash investigation and improvement very difficult without a live, consistent repro of the crash.
Understandably, Roblox cannot give us full crash logs. Full crash logs can include private information, and they generally only make sense when source code and debugging symbol access is available — something only Roblox has.
Automated analysis to identify a broad-category system could help developers know how they might be triggering a crash. Examples: Rendering, Physics, Out of Memory, GUI, etc.
This avoids sending any private information and does not require the developers to have source code or debugging symbol access but still gives them a target area to investigate.
I imagine this looks like — to us as developers — a breakdown in the Crashes graph indicating which engine system caused the crash.
If Roblox is able to address this issue, it would improve my development experience because it would make it significantly easier to identify and fix hard-to-reproduce crashes.
This feature request covers engine-level system tagging, which is not user-customizable and gives insight into engine functioning. Here is a related feature request for custom developer crash tags: Crash Reports: Tag Crashes with Developer Tags