UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Example URL:
http://www.pixiv.net/search.php?word=%E5%B5%90%E9%87%8E%E3%81%AE%E6%88%A6%E3%81%84

Steps to reproduce the problem:
1. Go to the given pixiv.net URL
2. Let page finish loading
3. Let page just sit there for a while

What is the expected behavior?
Page should finish loading in a reasonable amount of time, and the memory the page takes (according to Chrome's built-in task manager (Shift-Esc)) should remain constant over time as the page just sits there.

What went wrong?
1. The page makes repeated XHR GET requests for the same resources, over and over again.

2. The memory the page takes expands over time.  If left there for long enough it will die because it consumes too  much memory.

(NOTE: I think the above two points are two separate bugs, but I haven't been able to get them to reproduce separately)

Does it occur on multiple sites: No

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.87  Channel: stable
OS Version: Fedora 25
Flash Version: Shockwave Flash 24.0 r0

0. Attached is a bzip2'd tar file containing:
* pixiv.log: the console log of the XHR requests
* search.html: the HTML of the page displaying the problem
* ad_source.js: One of the JavaScript files issuing the XHR requests
* cedato_player_108.56_d.js: the other JavaScript file issuing the XHR requests

1. The problem might be specific to a single pixiv.net ad partner, so the page might have to be reloaded a few times before the problem shows.

2. The problems don't go away with either Shift-Ctrl-R or when all pixiv.net cookies are deleted with the EditThisCookie extension.

3. The problems *did* go away when I cleared the cache via chrome://settings/clearBrowserData, but this only worked once, and it came back when I did a Shift-Ctrl-R (hence why I think it might be restricted to just one of the ad partners of the site)

4. The problem goes away entirely if the page is loaded in a brand new user profile: there are no repeated XHRs, and the memory usage of the page remains stable.

5. If I start chrome with "--disable-extensions", the memory leak problem goes away, but the repeated XHR requests still remain.

6. If I start chrome with "--no-experiments", no difference is seen.

7. If I disable only the Stylish extension, the memory leak goes down a lot.

8. I have the following extensions installed and enabled:

<<<<<<
Vimium 1.57
1 Click Translator 8.4
EditThisCookie 1.4.1
eHistory 1.14
Extensions 1.0
Frame by Frame for YouTube™ 1.1.0
Image Properties Context Menu 0.7.6
Lazarus: Form Recovery 3.0.6
middle button new tab 0.9
Mute Tab Shortcuts 1.2.0
Mute Tabs By Url 2.5
Password Alert 1.23
Playing Favourites for Fallen London 0.3.1
Quick Javascript Switcher 1.4.1
Recently Closed Tabs 1.3.0.2
Session restore 0.6.2
Stylish - Custom themes for any website 1.7.3
Tabs to the front! 0.2.4
Vimium 1.57
Your Quality for YouTube™ 1.9
YouTube AutoFocus 0.5
>>>>>>>

9. I have a HAR (HTTP Archive) file of the network activity from when the page is displaying the bug, but I'm not attaching it here since it contains my cookies.  I will provide it to Chrome developers upon request.

 

Deleted: FILES.tar.bz2 120 KB

FILES.tar.bz2 120 KB Download