Ran a generation at 1824 x 1024, then upscaled it with the default settings in 3.1. The upscale went very well, and the file was saved properly, but when Invoke attempts to refresh the page to display the results, several of the icons at the top show the "loading" icon, and then the browser displays the browser generic "page failed to load" info.
Additionally, restarting InvokeAI does not appear to fix this issue, as it is still trying to load something.
#Displaying upscaled results causes page load error
1 messages · Page 1 of 1 (latest)
console log from the point at which I restarted Invoke to try and clear the error
additionally: I can't find the location where it is storing the images that may be causing the problem. Ran invoke.bat with option 7 and it's still having the page load issue. Is there a way to purge gallery data from the console?
Can you open your console (F12) and see if there are any errors?
Will see if I can. There’s no means of interacting with invoke when it’s trying to load the page.
(Clicking things with mouse)
Console should still work - it’s in the browser
No - should have a “console” tab in that panel
https://gyazo.com/ebb9047c7d0e2922e1cd60f65c79214e this is the console log itself, but what is visible there showed up before it started trying to load the upscaled info
So no errors there… hm
How about the network requests tab? It might be choking on trying to load the image in
https://gyazo.com/83832303a4d04d5307d29bb932ecb0af if that's the right info. seems to get to the thumbnail then has issues.
it does load the upscaled image. seems to get stuck trying to load the icons across the top (for instance the use prompt icon)
need to head back to RL a while. Thank you for looking into this. 🙂
Hmm, there's nothing out of the ordinary here. It all seems to be happy. If the UI logic has a problem, we'd see errors or warnings.
It sounds like the browser tab itself is crashing, which really shouldn't be possible. I wonder if the image file itself ended up corrupted, and the browser cannot open it?
Can you please try a different browser with a different engine? To clarify many browsers use the chromium engine, so we want to test on a totally different browser. For example, google chrome, microsoft edge and brave all use chromium - so if you were using a chromium browser, I'll ask you to try firefox. And if you were using Firefox, I'll ask you to use a chromium-based browser.
Another thing to try is to move the image file out of the outputs directory. I imagine it's the newest one in the folder. Generally it's best not to manually move images, but this is an extenuating circumstance. Restart the application after moving it out of that folder and see if the app loads.
Ok, so here's the test results
deleted the images from the output folder, opened in Brave, and the prolem persisted, even though the gallery was showing two grey thumbnails (apparently deleting them manually out of the folder doesn't clear some reference to them?).
opened Firefox
firefox started everything correctly, but grey thumbnails were still showing in the "images" panel
used the red trash can icon and deleted them
if images are gone, empty thumbnails make sense
it now starts properly in Brave
very interesting.
will test again to see if it's just something with the images, or if it has to be a large image
side note: it is only the "load workflow, use prompt, use seed, use all" icons that get stuck with loading. Not sure if that's significant or not
Ok, I tested with the 2x upscaler, and while it does trigger the four icons to loop a bit with the loading icon, it does not cause the page to fail to load, so it may be tied in to the file size produced before which was at 4x
those are probably trying to hit the image's metadata
7296 x 4096 was the 4x image, with a file size of 31.4mb (.png format)
Firefox is a workaround for fixing any issues though, so that's a plus. 🙂
I did a 4x upscale which resulted in an image that was over 6000 x 2048. I have not tested to see if that causes the crash, but, I believe that disabling the option in the gallery that automatically switches to the new image is the reason it didn't crash things.
Sorry for the late response, I missed your reply. I did some testing and confirmed that the issue is the metadata parsing logic not playing well with large images. I've created a bug report to track this:
https://github.com/invoke-ai/InvokeAI/issues/4570
@blissful ore
❤️
No worries. not that it's a total celebration to find a bug, but I'm glad it's been identified. 🙂
e