Chrome Inspector: Export Excel closes when we export more than 1000 rows

[srivatsankr]

Chrome Inspector:Export Excel closes when we export more than 1000 rows

Browser with all tab closes without any message.

Any suggestions on how to fix this issue will be helpful

[YogaSrinivash]

Hi @srivatsankr I'm facing same issue.
All pages are getting closed, and we lost all our work without any backup.
Have you found any workaround or any response from them?

[moicarolyn]

Hello @srivatsankr,
I'm also facing the same issue :(
Have you found any workaround or any response from them?

[janhnhi]

Hi @srivatsankr we're facing the same isse. Were you able to find a workaround?

[tprouvot]

Hi guys,

@moicarolyn @srivatsankr @janhnhi
Could you check if you face the same issue with this new version?

https://chrome.google.com/webstore/detail/salesforce-inspector-relo/hpijlohoihegkfehhibggnkbjhoemldh

[TXHBadger]

Hi @tprouvot, I too am experiencing this issue on both Inspector and Inspector Reloaded. Has any workaround been found?

[tprouvot]

@TXHBadger no workaround has been found and source of the error is still unknown.
To help me troubleshooting the issue, could you provide more details such as :

• Does this happen with all SObjects ?
• Does this happen with only Id field in the query ?
• How many fields do you have in the query and does it contains really large fields ?
• Does the same query on the same org provoke the same issue on another computer ?

[TXHBadger]

Hi @tprouvot thank you for getting back so quickly!

Does this happen with all SObjects ? Yes
Does this happen with only Id field in the query ? Yes, at 7150+ records
How many fields do you have in the query and does it contains really large fields ? 17 fields- only 1 text field allowing 255 characters
Does the same query on the same org provoke the same issue on another computer ? - Several users have the same issue, there are users not having this issue. I've compared permission, settings and our IT has reviewed. This happen when records exceed 7150+ records

Many thanks!

[dufoli]

Can you provide some more information ?

• chrome version
• check ressource (memory)
• can you go to extension => Manage extension => then errors button and if there are some provide log here:

[TXHBadger]

Hi @dufoli,

• Version 125.0.6422.61 (Official Build) (64-bit)
• I do not have an Errors option? I think I attached the image file?

[dufoli]

maybe it is only available in developper mode.
Have you enable developper mode on chrome ? on top right of manage extension layout ?

[TXHBadger]

@dufoli validated developer mode was active, still no errors option

[tprouvot]

Hi @tprouvot thank you for getting back so quickly!

Does this happen with all SObjects ? Yes Does this happen with only Id field in the query ? Yes, at 7150+ records How many fields do you have in the query and does it contains really large fields ? 17 fields- only 1 text field allowing 255 characters Does the same query on the same org provoke the same issue on another computer ? - Several users have the same issue, there are users not having this issue. I've compared permission, settings and our IT has reviewed. This happen when records exceed 7150+ records
Many thanks!

@TXHBadger Could you try the same query with the same user on one of your colleague's computer that doesn't crash ?
Last hint I have is the computer specs..

[TXHBadger]

@tprouvot tested with 4 users, 2 "failed" and 2 "successes" which points me more to a computer spec or setting? What is your last hint?

[tprouvot]

@TXHBadger,
I think this might be an issue linked to low computer specs, is there a difference between your and the ones which doesn't crash ?

[dufoli]

@TXHBadger few ideas:

• memory capacity and usage (you can open task manager to check)
• disk capacity and usage.
• swap size if you are on linux.
• do you have antivirus tool ?

[TXHBadger]

Hi @dufoli, checked these within the limits I have with the company security. (arghhh)

What I did find with colleagues that work is they are on Chrome vs 124 and those that don't work have been upgraded to 125? I have requested to have mine down graded back to 124 to see if that might "fix" the issue.

Any thoughts on that? Many thanks!

[tprouvot]

@TXHBadger I don't think that chrome version can be the cause.
Could you compare your Octane score with your colleagues that are not facing the issue ?

[TXHBadger]

@tprouvot Happy Friday!! Compared score with several colleagues and we are all comparable on the score. The only difference is it is working on a MAC and not Windows?