(In reply to rhill@raymondhill.net from comment #6) > Thanks for the repro steps. I had a look at the verbose memory report and I have to admit I am at a lost about all those `data:` URI strings -- these are not created by uBO, so I have to find out where they come from. I will investigate using your steps. > > Question re. repro steps: > - do I have to leave the tab active and/or visible, or can it be inactive while another tab is visible? I opened it up and let it load, then left it inactive and it kept running its JS or whatever in the background. > - did you scroll down or just left the tab as is untouched after reload? I think I scrolled down a bit. It typically has ads at the top of the viewport though. > - when you "come back later", roughly what delay are we talking about? minutes? hours? I think at least an hour is enough. You might not need that long, since it eats an absurd amount of memory.
Bug 1652925 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to rhill@raymondhill.net from comment #6) > Thanks for the repro steps. I had a look at the verbose memory report and I have to admit I am at a lost about all those `data:` URI strings -- these are not created by uBO, so I have to find out where they come from. I will investigate using your steps. > > Question re. repro steps: > - do I have to leave the tab active and/or visible, or can it be inactive while another tab is visible? I opened it up and let it load, then left it inactive and it kept running its JS or whatever in the background. > - did you scroll down or just left the tab as is untouched after reload? I think I scrolled down a bit. It typically has ads at the top of the viewport though. > - when you "come back later", roughly what delay are we talking about? minutes? hours? I think at least an hour is enough. You might not need that long, since it eats an absurd amount of memory.