New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 797872 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
dgozman@chromium.org
█ vamshi.k...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

PHP session_start causes Chrome to loose cache so that DevTools can no longer show source code

Reported by brand.pe...@gmail.com, Dec 28 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. Open the attached file
2. Open DevTools and observe source code is blank
3. Comment out the session_start line
4. Reopen file and observe source code is now available

What is the expected behavior?
Source code should still be available in cache with or without session_start

What went wrong?
Source code was lost necessitating reload of page in order to be able to debug.

Did this work before? N/A 

Chrome version: 63.0.3239.84  Channel: n/a
OS Version: 10.0
Flash Version: 

This is a follow on of  issue 795023  which was flagged as wont-fix, raised as a separate bug as I now have evidence of the cause of the loss of cache.

Comment 1 by brand.pe...@gmail.com, Dec 28 2017

testCache.php
241 bytes View Download

Comment 2 by krajshree@chromium.org, Dec 28 2017

Labels: Needs-Triage-M63

Comment 3 by vamshi.k...@techmahindra.com, Jan 1 2018

Cc: dgozman@chromium.org vamshi.k...@techmahindra.com
Labels: Triaged-ET
CC'ing dgozman@chromium.org from https://bugs.chromium.org/p/chromium/issues/detail?id=795023 for further inputs.

Thanks!

Comment 4 by eostroukhov@chromium.org, Jan 10 2018

Status: WontFix (was: Unconfirmed)
This looks like PHP issue, e.g. the server may not be returning the source.
►

Sign in to add a comment