Reproduction Steps
This was probably a fluke and will not reproduce easily.
I was running simple command bar code trying to remember some syntax and behavior and encountered a hard crash a second after running the last command.
Judging by the log an autosave happened at the same time I was running the command. Autosave needs to be more aware of when the user is doing something before it tries to save. Autosave is disruptive, and this alone would prevent it from screwing up most of the time in weird edge cases like this. Right now, more often than not it feels like autosave specifically kicks in the moment I start doing something instead.
The last segment of my log is the following:
2022-07-10T18:53:18.503Z,6439.503906,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::open - start
2022-07-10T18:53:18.545Z,6439.545898,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:53:53.853Z,6474.853027,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:54:48.935Z,6529.935059,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:56:03.113Z,6604.113281,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::open - start
2022-07-10T18:56:03.155Z,6604.155273,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:56:33.815Z,6634.815430,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:56:43.181Z,6644.181152,2ebc,6 [FLog::Output] RobloxMainWindow::requestDocClose doc.docType=2
2022-07-10T18:56:43.181Z,6644.181152,2ebc,6 [FLog::Output] RobloxMainWindow::forceDocClose doc.docType()=2
2022-07-10T18:56:43.181Z,6644.181152,2ebc,6 [FLog::Output] RobloxDocManager::removeDoc type 2
2022-07-10T18:56:43.199Z,6644.199707,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:56:43.217Z,6644.217773,2ebc,6 [FLog::Output] RobloxBasicDoc::closeDocument 0000027A214DC530
2022-07-10T18:56:51.330Z,6652.330566,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:57:01.738Z,6662.738770,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::open - start
2022-07-10T18:57:01.782Z,6662.782715,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:57:03.597Z,6664.597656,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:57:08.126Z,6669.126465,2170,12 [DFLog::HttpTraceError] HttpResponse(#3428 0000027B11C80E70) time:489.6ms (net:489.6ms callback:0.0ms timeInRetryQueue:0.0ms)status:403 Forbidden bodySize:158 url:"https://thumbnails.roblox.com/v1/games/icons?universeIds=402451863,1657224176,3720314446,177749064,3515778187,756649728,41286846,41286923,1413699782,599235448,1294279534,1294281994,273904,2373492520,465276754,1501658302,41286665,2370740230,357082927,2541089106,1493667986,2273314113,1291147857,2165888062&size=150x150&format=png&returnPolicy=AutoGenerated" ip:128.116.117.3 external:0 numberOfTimesRetried:0
2022-07-10T18:58:53.666Z,6774.666016,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T18:59:12.642Z,6793.642090,2ebc,6 [FLog::Output] Info: RobloxScriptDoc::activate - start
2022-07-10T19:01:31.721Z,6932.721680,2ebc,6 [FLog::Output] > local a = {1,2,3} for i = #a-1,1 do print(a[i]) end
2022-07-10T19:01:53.016Z,6954.016602,2ebc,6 [FLog::Output] > local a = {1,2,3} for i=#a-1,1 do print(a[i]) end
2022-07-10T19:01:57.667Z,6958.667480,2ebc,6 [FLog::Output] > local a = {1,2,3,4,5,6} for i=#a-1,1 do print(a[i]) end
2022-07-10T19:02:01.284Z,6962.284180,2ebc,6 [FLog::Output] > local a = {1,2,3,4,5,6} for i=#a-1,1 do print(i, a[i]) end
2022-07-10T19:02:02.711Z,6963.711426,2ebc,6 [FLog::UpdateUIManager] Start waiting for long process(00000279C64E2AB0): Auto-Saving
2022-07-10T19:02:03.030Z,6964.030762,2ebc,6 [FLog::UpdateUIManager] Pausing status bar update (00000279C64E2AB0)
Expected Behavior
Studio should not crash.
Actual Behavior
Crashed directly to desktop, no dialog was shown. No crash dump was generated.
Issue Area: Studio
Issue Type: Crashing
Impact: Low
Frequency: Very Rarely
Date First Experienced: 2022-07-10 14:07:00 (-05:00)
A private message is associated with this bug report