Seems this happens only with conjunction with VirtualTimePolicy, which is experimental. Will investigate further.

Would you mind providing us with a sample testcase for repro?

Hi, I have similar problem which I'm able to reproduce using system WebView
I make small test application to reproduce this problem:

```
package com.example.alex.myapplication;

import android.os.Handler;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.view.ViewGroup;
import android.webkit.WebChromeClient;
import android.webkit.WebView;
import android.webkit.WebViewClient;

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        ViewGroup vg = findViewById(R.id.main_activity);
        final WebView wv = new WebView(this);
        wv.setWebChromeClient(new WebChromeClient() {
            @Override
            public void onProgressChanged(WebView view, int newProgress) {
                System.out.println("onProgressChanged: " + newProgress);
            }
        });
        vg.addView(wv);
        wv.loadUrl("https://www.washingtonpost.com/");
        final Handler handler = new Handler();
        handler.postDelayed(new Runnable() {
            @Override
            public void run() {
                System.out.println("StopLoading");
                wv.stopLoading();
            }
        }, 1000);
    }
}

```

On Android Emulator with Network type: GPRS and signal strength: Poor (to slow down loading process) I have the following output:
```
 11-15 11:11:31.475 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 10
11-15 11:11:31.755 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 10
11-15 11:11:32.050 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 21
11-15 11:11:32.084 20426-20426/com.example.alex.myapplication I/System.out: StopLoading
11-15 11:11:32.173 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 70
11-15 11:11:32.173 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 100
11-15 11:11:32.173 20426-20426/com.example.alex.myapplication I/System.out: onProgressChanged: 100
```

As you can see, StopLoading was called before 70%, but WebView continued to load.

This is just smallest example, in real life I got this problem from time to time on different sites (most often on heavy sites, which tends to load a long while

Have you tried to call stopLoading twice? I've noticed that it always works on the second call.

Well, it looks like, that if I call stopLoading twice it work better, but seems still it doesn't work on _some_ sites (with lots of redirects or something else - not sure I understand which sites work and which are not)

StopLoading is equivalent to pressing Stop next to the address bar. I'll schedule stop action, but due to asynchronous nature of loading, its effect is not immediate.