Using developer tools in private window creates ghost processes



  • When I use the developer tools in a private window this creates "ghost" processes, which aren't terminated after closing the private window.
    In detail:
    I open a private window, open some tabs in it and use the developer tools in one (or more) of them. When I have closed the private window I can still see the processes of the developer tools and all private tabs which where open when I closed the private window in Vivaldi's task manager. When I close all Vivaldi windows this processes keep Vivaldi running in the background, I have to kill them with Window's task manager.

    Can someone reproduce this or is this something with my installation?
    I am using Vivaldi 1.13.1008.30 64-bit on Windows 7.


  • Moderator

    Can confirm this on Windows 10 x64 with 1.13 Stable.

    But happens for me only if the Developer Tools were previously used as Docked.

    Bug reported as: VB-34924 "ghost processes after using Developer Tools with tabs in Private Window"



  • @gwen-dragon Thank you, I have reported this bug, VB-34926.

    edit: That's not fair, you added the part that you already reported the bug 😞 😛


  • Moderator

    @rexfahrer said in Using developer tools in private window creates ghost processes:

    reported this bug, VB-34926.

    Thanks for report, but i was faster. I marked your one as a duplicate in bugtracker.


  • Moderator

    I hope this issue can be investigated and fixed quickly as most using Developer Tools never realize the zombies in their OS.



  • @gwen-dragon said in Using developer tools in private window creates ghost processes:

    I hope this issue can be investigated and fixed quickly as most using Developer Tools never realize the zombies in their OS.

    Yes, I only found this, because restarting Vivaldi didn't help when my mouse cursor kept disappearing in the 'Save file to...' dialog (btw. a very annoying bug, but I'm still searching for a way to reproduce it).



  • I did a quick test in Debian 9.2 and it is happening there, too.


  • Moderator

    @rexfahrer said in Using developer tools in private window creates ghost processes:

    quick test in Debian 9.2 and it is happening there, too.

    Thanks for test. I will add it to bugtracker.



  • @gwen-dragon Hi, is this bug still open?

    I reproduce with default settings + enabling "Use native window" 100% of the time on 2.1.1337.47.

    It's most likely related to that bug where pretty much the same manipulation would crash vivaldi main window (so now instead of crashing, we have ghost processes?) which was fixed (and came back and was fixed again). I had opened VB-30185 for it at the time.

    I reproduce even when developper tools are docked (I did undock it at first when trying to find why I wouldn't reproduce, since Gwen-Dragon mentionned that, but can reproduce from a clean state without undocking afterward).

    If I close the debugging tools windows before closing the private windows (when undocked), the problem does not seems to trigger. Visiting a site (opening the developpers tools from a site and not juste the empty private windows) is also necessary otherwise it does not trigger.

    Thanks


  • Moderator

    @gwen-dragon said in Using developer tools in private window creates ghost processes:

    VB-34926

    Was a duplicate of VB-34924 "ghost processes after using Developer Tools with tabs"
    and was Fixed in 2017.

    VB-30185 was closed as not reproducible.



  • @gwen-dragon the bug applies to native window mode on 1.15.1147.64 (Linux), current 2.1.1337.47 (Linux) and 2.2.1360.4 (Win10).

    Since this is a reproducible non-fixed cross-platform multi-version bug

    1. should we create a new report or
    2. will one of the old ones be (re)opened/amended?

    Any closing of a non-last window leads to ghost processes for open Devtools contexts.
    In docked mode both processes (site+devtools) become ghosts.
    The 1.15 version closes windowed DevTools, but the process remains.
    In 2.x+ the detached DevTools manual window close at least terminates the inspection process.

    Seems to indicate a general problem with missing/racy cleanup operations in native window mode.


  • Moderator

    @becm Ah, native Window. i had not tested with the mode.


  • Moderator

    @becm Please make a new bug report and do not forget to describe it very precisely step-by-step. And give as much information as you can.

    If the new bugreport is related to the closed one, the devs may link to the older one – but that is their job to decide which belongs to what.



  • @gwen-dragon submitted as VB-46257 with simple case to trigger condition.
    More regular failure mode when using multiple windows with tabs should be covered by description (hopefully).


  • Moderator

    @becm Bug internally confirmed by me for 2.1 Stable, 2.2 Snapshot on Windows.

    I investigated such issue was in 1.xx versions and fixed in Dezember 2017.
    Bug regressed in newer 2.x.



  • @gwen-dragon regression/bug is also in 1.13.1008.32 (2017-11-22) and 1.13.1008.44 (2018-01-22).
    So no obvious indication where a fix would have been applied during this time.

    All tested versions since first 1.13 release show same behaviour when using Native Window (verified for 1.14.1077.60).

    Preceding versions 1.10.867.48, 1.11.917.43 and 1.12.955.48 not affected.
    Did not (yet) test 1.9 branch due to its Gtk2 dependency…



  • @gwen-dragon Yeah, my bug (VB-30185) was missing the "Use native windows" step in the reproduction (I didn't know it was important at the time) but it did was "fixed" (I would say between oct-dec 2017) then came back (at least very similar) this year and re-fixed again relatively quickly. This seems related to what you're talking about.

    Thanks for filling the report becm.

    Here is how I reproduce the current one in case it's different from you (on 1.11 I get a crash instead of ghost processes, which is basically what I reported at the time. You didn't even need to go to a site to trigger it, just developer tools. Now it is needed).

    -Enable "Use native windows"
    -Having a normal vivaldi window open
    -Open a new private window
    -From that private window go to a site (google.com) and open developer tools (F12)
    -close the private window
    -Close the normal window

    On an unrelated note gwen-dragon, do you know what's the status of VB-26686 (paste and go trigger a search even if the option search in address field is disabled)? Not very important, just want to be sure it wasn't also closed since we don't get an email (I reproduce in current version).


  • Moderator


 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.