Qiime2 view issue with demux visualizations

Dear all

Recently, I have encountered an issue with demux visualizations. Interactive quality details are just collapsing and one can see only the narrow area that can be scrolled on the right side. I just ran 5 batches, with 4 of them having exactly this issue. Decided to report here as a bug.

Tested on Ubuntu 24.04, with qiime2-amplicon-2025.10, and 2025.4.

UPDATE1:

Issue can be reproduced with Chrome, but Firefox works with no issues.

Best,

Timur

1 Like

Hey @timanix,

I notice there's a scrollbar of an absurdly familiar height of 300px in your screenshot. Suggesting that the logic we use to expand an iframe isn't working anymore on the old tabbed templates.

Do you see the same issue with feature table summaries? I'm expecting basically the same thing to happen there.

1 Like

Hi @ebolyen ,

Thank you for your reply.

Only in Chrome, Firefox displays everything correctly.

Nope, so far only with quality plots. I run 5 batches (60-150 samples each). Issue observed:

After demultiplexing: 4/5

After trimming with cutadapt: 1/5

I don’t know how cutadapt affects it. Can it be that the scores distribution is somehow affecting it?

Best,

1 Like

What.

It must be something like that, perhaps the initial size is wrong or the first render when the template measures the height of the container?

Is there anything in your developer console that suggests something bad has happened?

1 Like

There are 114 errors in the console.

Could you also try to open it in Chrome (my version is 142.0.7444.162, 64-bit)? Link.

I don't seem to be able to reproduce this, I have tested the above r5-demux.qzv files on these systems:

OS X (M3): Chrome Version 142.0.7444.176 (Official Build) (arm64)
Linux (Ubuntu 24.04.2 LTS x86): Chrome Version 142.0.7444.175 (Official Build) (64-bit)

That is strange, just tested on another Ubuntu machine, the same issue with r2, r3 and r4 demux.qzv files, while r1 qnd r5 worked as expected.

It must be a timing issue... r1-r5 all work fine on Linux Chrome for me.

Would you be able to send a screenshot of your dev console on one of the problematic plots?

Here is the log from the failed (collapsed) page.

view.qiime2.org-1763644380782.log (9.2 KB)

Long shot, but I think those errors are actually from an ANCOMBC2 Visualization.

Is there any chance you have some of them open at the same time while you are loading these visualizations? I wonder if the service worker is attempting to fetch a URL each time a new Viz loads, and the 404 takes long enough that it times out on the iframe measurement.

Each 404 seems to happen under the same "session id" so that's why I think it might be unrelated visualizations causing this.

1 Like

I had it open previously today, but they were closed by the time of the test.

What I did after closing all other tabs:

  • Updated Chrome to the latest version
  • Cleared history/cashe
  • Restarted my PC

Just checked again and was able to reproduce the issue. I also remember having the same issue with the same batches but analysed with 2025.4 version of q2. Issue was repeated on laptop and PC, with the same version of Ubuntu, but different versions of Chrome. With Firefox, it works well on both.

1 Like

One last option, if you go here:

chrome://serviceworker-internals/

and search for view.qiime2.org you can unregister the worker and then reload the page.

Anything different in that case? Also, are the logs still as long?

1 Like

The issue was still there.

Logs were shortened after updating and clearing the history, but didn’t change after unregistering the worker.

But thank you for your test with Linux + Chrome and not confirming the issue. Previously, I was blaming Chrome (since there were no issues in Firefox), but after your feedback, I tested it in “Incognito” mode. No issues were detected, so I went back to the usual mode and disabled all extensions one by one. After disabling Grammarly, the issue disappeared.

Thank you again for your time and help! I should have thought about “Incognito“ mode earlier.

2 Likes

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.