microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4
Graph Explorer response downgrades for multiple instances and a lot of activity
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 260
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I test APIs quite a bit while doing docs and investigating customer issues so in the process, I'm also quickly running queries, copy-pasting, replacing etc. I also usually end up opening multiple GE tabs to help me retain context as I test a series of related endpoints. And with these two actions, GE starts hanging. If I have at least 3-4 GE tabs open, it will start misbehaving. Takes at least a minute to respond, sometimes more. Sometimes it forces me to restart the browser (I use Chrome). I started experiencing the issue sometime in January 2024.
When GE becomes unresponsive, the other open non-GE tabs on the same browser are still working well.
Also, when I open just one or two tabs and use them lightly (like run a query, inactivity for many minutes), GE just responds well.
To Reproduce
Steps to reproduce the behavior:
- Open at least 3 instances of Graph Explorer on a Chrome browser.
- Shift between the tabs as you run queries, copying, pasting, replacing quickly etc.
- One tab decides to hang. If you try to switch to another of the open GE tabs, they've hung as well. However, other non-GE tabs are still responsive.
Expected behavior
GE to be stable even during heavy usage.
Screenshots
Not available as of now. I'll grab a video/gif next time I'm using GE and the issue recurs, then upload it to this issue.
See below
- The whole time, I was trying to highlight to copy and the tab was unresponsive.As you can see, other GE tabs had crashed.
Desktop (please complete the following information):
- OS: Windows 11
- Browser: Chrome
- Version: 122.0.6261.112
Additional context
n/a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.