Unable to save session as JSON or generate report after creating 2-4 bugs

[couby2060]

First, thank you for this excellent extension! I used it previously and everything worked perfectly.

After reinstalling it after a longer break, I'm experiencing an issue where I can no longer save the session as JSON or generate a report after creating 2-4 bugs (including crop screenshots).

Environment
Browser: Chrome 137.0.7151.104 (latest version)
OS: macOS 15.5
Device: M4 MacBook

Steps to Reproduce
Install/reinstall the extension
Create 2-4 bug reports including crop screenshots
Attempt to save session as JSON or generate a report

Error Messages
Error loading data: Could not get full session data

Additional Information
I have cleared Chrome cache and other data to ensure no interference

Any assistance would be greatly appreciated!

[morvader]

Thanks for reaching out . I'm sorry to hear you're experiencing an issue.

To help me diagnose and fix the problem, could you please send me the error logs from the extension? These logs will give me the technical details I need to understand what's going wrong.

Please follow the steps below.

Open Chrome and copy-paste this address into your address bar, then press Enter:
chrome://extensions

Find Exploratory Testing in the list of extensions.

If there have been any errors, you will see a red button labeled "Errors". Please click it.

If this button is not there or is grayed out, it means no errors have been recorded this way.
Please copy all the text on this page and paste it in your reply to me.

[morvader]

Have you refresh the page before adding bugs?. Could you try it, please? @couby2060

[couby2060]

Thanks for the quick feedback!

Regarding the error logs: I don't see anything showing up as errors on the extension overview page - no red "Errors" button is visible or grayed out.

Update after further testing:
I managed to make it work and identified the pattern:

• Working scenario: When I start by reporting a bug on an open tab, then report bugs on other tabs, and check the bug report - it works fine.

• Crashing scenario: If I open a tab, report a bug, then open another tab and try to look at the bug report immediately - it crashes.

It seems the extension works correctly when I'm on the same tab where I originally reported a bug. However, if I switch to a different tab and try to open the report immediately, it crashes.

My workflow context:
I open ~50 URLs for testing, use a regex search extension to highlight issues like double blanks, then create bug reports for problematic pages.

Thanks again for looking into this!

[morvader]

I've just publish a new version in the store. Could you check if it solves the issue?. @couby2060

Thanks!

[couby2060]

Hi, i did some short test and there didn't occure any error. Looks good to me on the first glance.
thanks alot :)