Large, single gene queries crash on Chrome, but not Firefox

Skip to first unread message

Zachary Whitfield (WHITFIEZ)

Jul 23, 2021, 11:37:15 AMJul 23
to cBioPortal for Cancer Genomics Discussion Group
Some colleagues and I have been troubleshooting crashes we see on our own instance of cBioPortal.
When using Chrome to query a highly mutated gene on a fairly large dataset (~28,000 samples corresponding to ~35,000 alterations), Chrome will hang at the "Annotating with OncoKB and Cancer Hotspots" for ~3-4 minutes. It will then just freeze, or display a mostly blank page (still has some of the header images and tabs, but no actual oncoprint). Monitoring the network requests within the browser shows one of the 'fetch' steps as "(failed)

However, Firefox consistently returns results for the same query.

Performing a query with a less mutated gene (~28,000 samples corresponding to ~23,000 alterations), returns results in both browsers no problem.

Has anyone experienced a similar issue? Are there any ideas why Chrome might fail here? Please let me know if I can provide any more information that would be helpful (or if it would be better to post this as an issue on GitHub).
Thanks so much,

JJ Gao

Jul 26, 2021, 3:22:15 PMJul 26
to Zachary Whitfield (WHITFIEZ), cBioPortal for Cancer Genomics Discussion Group
Hi Zack,

Thanks for contacting us. Was this problem on the public portal? If so, could you send us the URL after submitting the query? 


You received this message because you are subscribed to the Google Groups "cBioPortal for Cancer Genomics Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Zachary Whitfield (WHITFIEZ)

Jul 26, 2021, 4:23:13 PMJul 26
to cBioPortal for Cancer Genomics Discussion Group
Thank you so much for responding JJ. This was not on the public portal, but rather our own deployed instance with our own internal datasets (I realize that makes it more difficult to help troubleshoot).

It seems we have this issue when the query will return a large (>~30,000) number of alterations for a single gene. I was unable to find a single gene to return such a large number of alterations on the public site (though I definitely could have overlooked something). I was, however, able to return that large of a query on the public Genie site with no issue on Chrome.

Any information or clues on why we might be experiencing such an issue would be greatly appreciated. Are you aware of any difference with how the public site (or an internal deployment based on the public site) fetches data (in particular the OncoKB annotations) compared to the public Genie site?

Reply all
Reply to author
0 new messages