workbench.glass.main.js · part 887

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js, part 887. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

[MemoryMonitor] Failed to trigger emergency profile:

[MemoryMonitor] No upload URL available for emergency profile, will retry on next launch.

[MemoryMonitor] Emergency profile uploaded successfully.

[MemoryMonitor] Failed to upload emergency profile, will retry on next launch:

[MemoryMonitor] Found ${t.length} orphaned emergency profile(s) to upload.

[MemoryMonitor] No upload URL available for orphaned profiles, keeping on disk.

[MemoryMonitor] Uploaded orphaned emergency profile: ${e}

[MemoryMonitor] Failed to upload orphaned profile ${e}:

[MemoryMonitor] Error scanning for orphaned emergency profiles:

[MemoryMonitor] Manual snapshot requested, proceeding directly to capture.

[Manual snapshot]

[DEV ONLY] Your app is using an abnormal amount of memory. Help the client team by capturing a snapshot. It will freeze the app for a moment.

Heap usage:
- JavaScript heap: ${t.jsHeapUsedMB.toFixed(0)}MB
- ${n} threshold: ${e}MB

Take and upload snapshot

Ignore for this session

Heap Snapshot Description

Briefly describe what you were doing...

[None provided]

Capturing snapshot. The window may briefly freeze.

[MemoryMonitor] Calling captureAndSendDebuggingData for pid ${e}.

[MemoryMonitor] Could not get upload URL for snapshot upload.

Could not upload snapshot: unable to get upload URL.

Uploading snapshot to Cursor...

[MemoryMonitor] Successfully uploaded snapshot.

Snapshot uploaded successfully. Thank you!

[MemoryMonitor] Failed to upload snapshot.

Snapshot upload failed. The snapshot is still saved on disk.

[MemoryMonitor] Error uploading snapshot:

Snapshot upload failed: ${r instanceof Error?r.message:String(r)}. The snapshot is still saved on disk.

Heap snapshot saved to disk.

Reveal in File Explorer

[MemoryMonitor] Snapshot confirmed at ${e} level. Proceeding with capture attempt.

[MemoryMonitor] captureAndSendDebuggingData returned no file path.

[MemoryMonitor] Snapshot saved locally at ${i}.

[MemoryMonitor] Error during snapshot capture:

An error occurred while capturing debug snapshot: ${i instanceof Error?i.message:String(i)}

[User toast snapshot]

[MemoryMonitor] User snapshot requested while another check or snapshot is in progress. Ignoring.

A memory snapshot is already in progress.

[MemoryMonitor] User clicked capture snapshot, proceeding immediately.

[MemoryMonitor] captureAndSendDebuggingData returned no file path.

[MemoryMonitor] User snapshot saved locally at ${i}

Snapshot saved.

Saved to: "${i}"

Memory snapshots can contain sensitive information; please ask your administrator to share your snapshot with Cursor.

Snapshot saved.

Saved to: "${i}"

Sending this snapshot to Cursor will help us diagnose and fix memory issues. Please note that the snapshot may include file contents, conversations, and other workspace data.

Send to Cursor

No thanks

[MemoryMonitor] Error capturing user snapshot:

An error occurred while capturing the snapshot: ${i instanceof Error?i.message:String(i)}

[MemoryMonitor] Manual snapshot triggered while a check or snapshot is in progress. Ignoring.

[MemoryMonitor] Unable to retrieve memory usage for manual snapshot. Ignoring.

[MemoryMonitor] Manual snapshot triggered successfully.

browser webview

browser view

Capture and Upload Process Snapshot

[CpuMonitor] Not starting monitor: mainWindow ID is not 1.

[CpuMonitor] Not monitoring: eligibility conditions not met.

[CpuMonitor] Starting monitoring: total>=${e.totalCpuPercent}% or process>=${e.processCpuPercent}% sustained for ${e.sustainedSeconds}s, interval ${e.checkIntervalSeconds}s.

[CpuMonitor] Skipping check, previous check/capture still in progress.

[CpuMonitor] No process tree snapshot available; skipping check.