Bugzilla

What is the best way to capture cc logs?
I am using the STR from bug 1937398. I get the large memory increase, and then I go to about:memory and click on "save verbose logs". That saved a bunch of log files, but the actual cc was not triggered - the cc got triggered after maybe 15 seconds after the logs had been completely written to disk.

What is the best way to capture cc logs?
- What i saw is that the logs are created and _then_the actual cc runs.
- The "save concise logs" or "save verbose logs" buttons should ideally be "run cc and save logs"
- There is no way to associate the multiple cc logs with a specific process/tab
- What do we do with the gc logs? Are they useful?
- Maybe the tool can pickup more files from the disk as it needs them? The user only should point the tool at the directory where logs are saved

I am using the STR from bug 1937398. I get the large memory increase, and then I go to about:memory and click on "save verbose logs". That saved a bunch of log files, but the actual cc was not triggered - the cc got triggered after maybe 15 seconds after the logs had been completely written to disk.

What is the best way to capture cc logs?
- What i saw is that the logs are created and _then_the actual cc runs.
- The "save concise logs" or "save verbose logs" buttons should ideally be "run cc and save logs"
- There is no way to associate the multiple cc logs with a specific process/tab
- What do we do with the gc logs? Are they useful?
- Maybe the tool can pickup more files from the disk as it needs them? The user only should point the tool at the directory where logs are saved
- Or maybe the user selects ALL the cc-log files and then the tool can use whatever it needs

I am using the STR from bug 1937398. I get the large memory increase, and then I go to about:memory and click on "save verbose logs". That saved a bunch of log files, but the actual cc was not triggered - the cc got triggered after maybe 15 seconds after the logs had been completely written to disk.

What is the best way to capture cc logs?
- What i saw is that the logs are created and _then_ the actual cc runs.
- The "save concise logs" or "save verbose logs" buttons should ideally be "run cc and save logs"
- There is no way to associate the multiple cc logs with a specific process/tab
- What do we do with the gc logs? Are they useful?
- Maybe the tool can pickup more files from the disk as it needs them? The user only should point the tool at the directory where logs are saved
- Or maybe the user selects ALL the cc-log files and then the tool can use whatever it needs

I am using the STR from bug 1937398. I get the large memory increase, and then I go to about:memory and click on "save verbose logs". That saved a bunch of log files, but the actual cc was not triggered - the cc got triggered after maybe 15 seconds after the logs had been completely written to disk.

What is the best way to capture cc logs?
- What i saw is that the logs are created and _then_ the actual cc runs.
- The "save concise logs" or "save verbose logs" buttons should ideally have the functionality of "run cc and save logs"
- There is no way to associate the multiple cc logs with a specific process/tab
- What do we do with the gc logs? Are they useful?
- Maybe the tool can pickup more files from the disk as it needs them? The user only should point the tool at the directory where logs are saved
- Or maybe the user selects ALL the cc-log files and then the tool can use whatever it needs

I am using the STR from bug 1937398. I get the large memory increase, and then I go to about:memory and click on "save verbose logs". That saved a bunch of log files, but the actual cc was not triggered - the cc got triggered after maybe 15 seconds after the logs had been completely written to disk.