Downloads & Free Reading Options - Results

“If They Have A Good Reason To Be Mad At You- Then Do Something About It. You Caused The Problem Fix It. But If They're Just Mad #noworries-MiBrtp3vILV.mp4 If They Have A Good Reason To Be Mad At You Then Do Something About It You Caused The Problem Fix It But If Theyre Just Mad Noworries MiBrtp3vILV Mp4 Noworries” Metadata:

• Title: ➤  If They Have A Good Reason To Be Mad At You- Then Do Something About It. You Caused The Problem Fix It. But If They're Just Mad #noworries-MiBrtp3vILV.mp4 If They Have A Good Reason To Be Mad At You Then Do Something About It You Caused The Problem Fix It But If Theyre Just Mad Noworries MiBrtp3vILV Mp4 Noworries
• Author: Kenneth Udut

“If They Have A Good Reason To Be Mad At You- Then Do Something About It. You Caused The Problem Fix It. But If They're Just Mad #noworries-MiBrtp3vILV.mp4 If They Have A Good Reason To Be Mad At You Then Do Something About It You Caused The Problem Fix It But If Theyre Just Mad Noworries MiBrtp3vILV Mp4 Noworries” Subjects and Themes:

• Subjects: noworries - Vine - KennethUdut

Edition Identifiers:

• Internet Archive ID: ➤  IfTheyHaveAGoodReasonToBeMadAtYouThenDoSomethingAboutItYouCausedTheProblemFixI

“Don't Just Do Something, Sit There.” Metadata:

• Title: ➤  Don't Just Do Something, Sit There.
• Author: ➤  Forest Community Church Sermons

Edition Identifiers:

• Internet Archive ID: ➤  rqagqfpmip3dj6ltgxgjc1jtxhkcsyds85knlvph

“JPP B Q4 L01 - Don’t Do Something; Just Stand There!” Metadata:

• Title: ➤  JPP B Q4 L01 - Don’t Do Something; Just Stand There!
• Language: English

“JPP B Q4 L01 - Don’t Do Something; Just Stand There!” Subjects and Themes:

• Subjects: ➤  adventist - junior - sabbath - school - lesson - blessed - presence

Edition Identifiers:

• Internet Archive ID: Junior20171007Q4L1

“BBC Archive - #OnThisDay 1972: Nationwide Showed How You Could Make Sweet Music With Just A Few Hundred Boxes Of Matches. Something To Do If You’re Bored In Isolation, Perhaps?” Metadata:

• Title: ➤  BBC Archive - #OnThisDay 1972: Nationwide Showed How You Could Make Sweet Music With Just A Few Hundred Boxes Of Matches. Something To Do If You’re Bored In Isolation, Perhaps?
• Author: BBC Archive

“BBC Archive - #OnThisDay 1972: Nationwide Showed How You Could Make Sweet Music With Just A Few Hundred Boxes Of Matches. Something To Do If You’re Bored In Isolation, Perhaps?” Subjects and Themes:

• Subjects: Twitter - video - OnThisDay

Edition Identifiers:

• Internet Archive ID: twitter-1254077709338021888

“The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.” Metadata:

• Title: ➤  The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.

“The Chromium Logo The Chromium Projects Home Chromium ChromiumOS Quick Links Report Bugs Discuss Other Sites Chromium Blog Google Chrome Extensions Except As Otherwise Noted, The Content Of This Page Is Licensed Under A Creative Commons Attribution 2.5 License, And Examples Are Licensed Under The BSD License. Privacy Edit This Page For Developers > How-Tos > Debugging Chromium On Windows First See Get The Code For Checkout And Build Instructions. Getting Started You Can Use Visual Studio's Built-in Debugger Or WinDBG To Debug Chromium. You Don't Need To Use The IDE To Build In Order To Use The Debugger: Autoninja Is Used To Build Chromium And Most Developers Invoke It From A Command Prompt, And Then Open The IDE For Debugging As Necessary. To Start Debugging An Already-built Executable With Visual Studio Just Launch Visual Studio (2019 Or Higher) And Select File-> Open-> Project/Solution (Ctrl+Shift+O) And Select The Executable Of Interest. This Will Create A Solution With That Executable As The 'project'. You Can Then Launch The Debugger With F5 Or F11 Or From The Debug Menu. If You Right-click On The Executable In Solution Explorer And Select Properties Then You Can Edit Things Such As The Executable Path, Command-line Arguments, And Working Directory. You Can Add Additional Executables To The Solution By Using File-> Add-> Existing Project And Selecting Another Already-built Executable. You Can Select Which One To Debug By Right-clicking On One Of Them In Solution Explorer And Selecting Set As Startup Project. When Your Solution File Is Customized To Your Taste You Can Save It To A Directory Such As Out\solutions. Saving It There Helps Ensure That Relative Paths To Source Files, Printed From Build Commands, Will Correctly Identify The Source Files. The Tools Menu Can Be Used To Add Commands To Do Things Like Invoke Autoninja To Build Chrome, Compile The Selected Source File, Or Other Things. Visual Studio 2017 Is Not Recommended For Debugging Of Chromium - Use A Newer Version For Best Performance And Stability. Symbol_level=2 Is The Default On Windows And Gives Full Debugging Information With Types, Locals, Globals, Function Names, And Source/line Information. Symbol_level=1 Creates Smaller PDBs With Just Function Names, And Source/line Information - Source-level Debugging Is Still Supported (new From June 2019), But Local Variables And Type Information Are Missing. Symbol_level=0 Gives Extremely Limited Debugging Abilities, Mostly Just Viewing Call Stacks When Chromium Crashes. Browsing Source Code If You Use A Solution File Generated By Gn (gn Gen --ide=vs) Then Intellisense May Help You Navigate The Code. If This Doesn't Work Or If You Use A Solution Created As Above Then You May Want To Install VsChromium To Help Navigate The Code, As Well As Using Https://source.chromium.org. Profiles It's A Good Idea To Use A Different Chrome Profile For Your Debugging. If You Are Debugging Google Chrome Branded Builds, Or Use A Chromium Build As Your Primary Browser, The Profiles Can Collide So You Can't Run Both At Once, And Your Stable Browser Might See Profile Versions From The Future (Google Chrome And Chromium Use Different Profile Directories By Default So Won't Collide). Use The Command-line Option: --user-data-dir=C:\tmp\my_debug_profile (replace The Path As Necessary) Using The IDE, Go To The Debugging Tab Of The Properties Of The Chrome Project, And Set The Command Arguments. Chrome Debug Log Enable Chrome Debug Logging To A File By Passing --enable-logging --v=1 Command-line Flags At Startup. Debug Builds Place The Chrome_debug.log File In The Out\Debug Directory. Release Builds Place The File In The Top Level Of The User Data Chromium App Directory, Which Is OS-version-dependent. For More Information, See Logging And User Data Directory Details. Symbol Server If You Are Debugging Official Google Chrome Release Builds, Use The Symbol Server: Https://chromium-browser-symsrv.commondatastorage.googleapis.com In Visual Studio, This Goes In Tools > Options Under Debugging > Symbols. You Should Set Up A Local Cache In A Empty Directory On Your Computer. In Windbg You Can Add This To Your Symbol Server Search Path With The Command Below, Where C:\symbols Is A Local Cache Directory: .sympath+ SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Alternately, You Can Set The _NT_SYMBOL_PATH Environment Variable To Include Both The Microsoft And Google Symbol Servers - VS, Windbg, And Other Tools Should Both Respect This Environment Variable: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com Note That Symbol Servers Will Let The Debuggers Download Both The PE Files (DLLs And EXEs) And The PDB Files. Chrome Often Loads Third Party Libraries And Partial Symbols For Some Of These Are Also Public. For Example: AMD: Https://download.amd.com/dir/bin Nvidia: Https://driver-symbols.nvidia.com/ Intel: Https://software.intel.com/sites/downloads/symbols/ For Example, For Completeness, The Following Symbol Server Environment Variable Will Resolve All Of The Above Sources - But This Is More Than Is Normally Needed: _NT_SYMBOL_PATH=SRV\*C:\symbols\*https://msdl.microsoft.com/download/symbols;SRV\*C:\symbols\*https://chromium-browser-symsrv.commondatastorage.googleapis.com;SRV\*C:\symbols\*https://download.amd.com/dir/bin;SRV\*C:\symbols\*https://driver-symbols.nvidia.com/;SRV\*C:\symbols\*https://software.intel.com/sites/downloads/symbols/ Source Indexing You Should Set Up Source Indexing In Your Debugger (.srcfix In Windbg, Tools-> Options-> Debugging-> General-> Enable Source Server Support In Visual Studio) So That The Correct Source Files Will Automatically Be Downloaded Based On Information In The Downloaded Symbols. Additionally, You Must Have Python In Your Path In Order For The Command That Fetches Source Files To Succeed; Launching The Debugger From The Same Environment As Where You Build Chromium Is An Easy Way To Ensure It's Present. This Is Highly Recommended When Debugging Released Google Chrome Builds Or Looking At Crash Dumps. Having The Correct Version Of The Source Files Automatically Show Up Saves Significant Time So You Should Definitely Set This. Multi-process Issues Chromium Can Be Challenging To Debug Because Of Its Multi-process Architecture. When You Select Run In The Debugger, Only The Main Browser Process Will Be Debugged. The Code That Actually Renders Web Pages (the Renderer) And The Plugins Will Be In Separate Processes That's Not (yet!) Being Debugged. The ProcessExplorer Tool Has A Process Tree View Where You Can See How These Processes Are Related. You Can Also Get The Process IDs Associated With Each Tab From The Chrome Task Manager (right-click On An Empty Area Of The Window Title Bar To Open). Automatically Attach To Child Processes There Are Two Visual Studio Extensions That Enable The Debugger To Automatically Attach To All Chrome Processes, So You Can Debug All Of Chrome At Once. Microsoft's Child Process Debugging Power Tool Is A Standalone Extension For This, And VsChromium Is Another Option That Bundles Many Other Additional Features. In Addition To Installing One Of These Extensions, You Must Run Visual Studio As Administrator, Or It Will Silently Fail To Attach To Some Of Chrome's Child Processes. Single-process Mode One Way To Debug Issues Is To Run Chromium In Single-process Mode. This Will Allow You To See The Entire State Of The Program Without Extra Work (although It Will Still Have Many Threads). To Use Single-process Mode, Add The Command-line Flag --single-process This Approach Isn't Perfect Because Some Problems Won't Manifest Themselves In This Mode And Some Features Don't Work And Worker Threads Are Still Spawned Into New Processes. Manually Attaching To A Child Process You Can Attach To The Running Child Processes With The Debugger. Select Tools > Attach To Process And Click The Chrome.exe Process You Want To Attach To. Before Attaching, Make Sure You Have Selected Only Native Code When Attaching To The Process This Is Done By Clicking Select... In The Attach To Process Window And Only Checking Native. If You Forget This, It May Attempt To Attach In "WebKit" Mode To Debug JavaScript, And You'll Get An Error Message "An Operation Is Not Legal In The Current State." You Can Now Debug The Two Processes As If They Were One. When You Are Debugging Multiple Processes, Open The Debug > Windows > Processes Window To Switch Between Them. Sometimes You Are Debugging Something That Only Happens On Startup, And Want To See The Child Process As Soon As It Starts. Use: --renderer-startup-dialog --no-sandbox You Have To Disable The Sandbox Or The Dialog Box Will Be Prohibited From Showing. When The Dialog Appears, Visit Tools > Attach To Process And Attach To The Process Showing The Renderer Startup Dialog. Now You're Debugging In The Renderer And Can Continue Execution By Pressing OK In The Dialog. Startup Dialogs Also Exist For Other Child Process Types: --gpu-startup-dialog, --ppapi-startup-dialog, --utility-startup-dialog, --plugin-startup-dialog (for NPAPI). For Utilities, You Can Add A Service Type --utility-startup-dialog=data_decoder.mojom.DataDecoderService. You Can Also Try The Vs-chromium Plug-in To Attach To The Right Processes. Semi-automatically Attaching The Debugger To Child Processes The Following Flags Cause Child Processes To Wait For 60 Seconds In A Busy Loop For A Debugger To Attach To The Process. Once Either Condition Is True, It Continues On; No Exception Is Thrown. --wait-for-debugger-children[=filter] The Filter, If Provided, Will Fire Only If It Matches The --type Parameter To The Process. Values Include Renderer, Plugin (for NPAPI), Ppapi, Gpu-process, And Utility. When Using This Option, It May Be Helpful To Limit The Number Of Renderer Processes Spawned, Using: --renderer-process-limit=1 Image File Execution Options Using Image File Execution Options (IFEO) Will Not Work Because CreateProcess() Returns The Handle To The Debugger Process Instead Of The Intended Child Process. There Are Also Issues With The Sandbox. Time Travel Debugging You Can Do Time Travel Debugging Using WinDbg Preview (must Be Installed From The Microsoft Store). This Lets You Execute A Program Forward And Backwards. After Capturing A Trace, You Can Set Breakpoints And Step Through Code As Normal, But Also Provides 'backwards' Commands (g-, T-, P-) So That You Can Go Back And Forth Through The Execution. It Is Especially Useful To Set Data Breakpoints (ba Command) And Reverse Continuing, So You Can See When A Certain Variable Was Last Changed To Its Current Value. Chromium Specifics: The Type Of Injection The Time Travel Tracer Needs To Perform Is Incompatible With The Chromium Sandbox. In Order To Record A Trace, You'll Need To Run With --no-sandbox. Chromium Cannot Run Elevated With Administrator Privileges, So The "Launch Executable (advance)" Option Won't Work, You'll Need To Attach After The Process Has Already Launched Via The Checkbox In The Bottom Right. If You Need To Record Startup-like Things, You'll Have To Use --{browser,gpu,renderer,utility}-startup-dialog, Then Attach (and Hope The Relevant Code Hasn't Executed Before That Point). JsDbg -- Data Structure Visualization You Can Install JsDbg As A Plugin For WinDbg Or Visual Studio. It Interactively Lets You Look At Data Structures (such As The DOM Tree, Accessibility Tree, Layout Object Tree, And Others) In A Web Browser As You Debug. See The JsDbg Site For Some Screen Shots And Usage Examples. This Also Works When Examining Memory Dumps (though Not Minidumps), And Also Works Together With Time Travel Debugging. Visual Studio Hints Debug Visualizers Chrome's Custom Debug Visualizers Should Be Added To The Pdb Files And Automatically Picked Up By Visual Studio. The Definitions Are In //tools/win/DebugVisualizers If You Need To Modify Them (the BUILD.gn File There Has Additional Instructions). Don't Step Into Trivial Functions The Debugger Can Be Configured To Automatically Not Step Into Functions Based On Regular Expression. Edit Default.natstepfilter In The Following Directory: For Visual Studio 2015: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2015\Visualizers (for The Current User Only) For Visual Studio 2017 Pro: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Packages\Debugger\Visualizers (for All Users) Or %USERPROFILE%\My Documents\Visual Studio 2017\Visualizers (for The Current User Only) Add Regular Expressions Of Functions To Not Step Into. Remember To Regex-escape And XML-escape Them, E.g. < For < And \. For A Literal Dot. Example: Operator New NoStepInto Operator Delete NoStepInto Std::.* NoStepInto WTF::.*Ptr ::.* NoStepInto This File Is Read At Start Of A Debugging Session (F5), So You Don't Need To Restart Visual Studio After Changing It. More Info: Microsoft Email Thread V8 And Chromium V8 Supports Many Command-line Flags That Are Useful For Debugging. V8 Command-line Flags Can Be Set Via The Chromium Command-line Flag --js-flags; For Instance: Chrome.exe --js-flags="--trace_exception --heap_stats" Note That Some V8 Command-line Flags Exist Only In The Debug Build Of V8. For A List Of All V8 Flags Try: Chrome.exe --js-flags="--help" Graphics Debugging GPU Acceleration Of Rendering Can Be More Easily Debugged With Tools. See: Graphics Debugging In Visual Studio 2013 Graphical Debugging With NVIDIA NSight Debugging On Another Machine Sometimes It's Useful To Debug Installation And Execution On A Machine Other Than Your Primary Build Box. To Run The Installer On Said Other Machine, First Build The Mini_installer Target On Your Main Build Machine (e.g., Autoninja -C Out\Debug Mini_installer). Next, On The Debug Machine: Make The Build Machine's Build Volume Available On The Debug Machine Either By Mounting It Locally (e.g., Z:\) Or By Crafting A UNC Path To It (e.g., \\builder\src) Open Up A Command Prompt And Change To A Local Disk Run Src\tools\win\copy-installer.bat In The Remote Checkout By Way Of The Mount (e.g., Z:\PATHTOCHECKOUT\src\...) Or UNC Path (e.g., \\builder\src\...). This Will Copy The Installer, DLLs, And PDBs Into Your Debug Machine's C:\out Or C:\build (depending On If You're Rocking The Component=shared_library Build Or Not) Run C:\out\Debug\mini_installer.exe With The Flags Of Your Choice To Install Chrome. This Can Take Some Time, Especially On A Slow Machine. Watch The Task Manager And Wait Until Mini_installer.exe Exits Before Trying To Launch Chrome (by Way Of The Shortcut(s) Created By The Installer) For Extra Pleasure, Add C:\out\Debug To Your _NT_SYMBOL_PATH Environment Variable Consider Reading The Documentation At The Top Of Copy-installer.bat To See How You Can Run It. It Tries To Be Smart And Copy The Right Things, But You May Need To Be Explicit (e.g., "copy-installer.bat Out Debug"). It Is Safe To Re-run The Script To Copy Only Modified Files (after A Rebuild, For Example). You Can Also Use The Zip Action Of The Isolate Scripts (tools\mb\mb.py) To Package All The Files For A Target Into A Single Zip File, For Example: Python Tools\mb\mb.py Zip Out/Release Base_unittests Base_unittests.zip Finding All Memory Allocations It Is Possible To Use Heap Snapshots To Get Call Stacks On All Outstanding Allocations That Use The OS Heap. This Works Particularly Well If Heap Snapshots Are Started As Soon As The Chrome Browser Process Is Created, But Before It Starts Running. Details Can Be Found In This Batch File. However, With PartitionAlloc Everywhere Most Chromium Allocations No Longer Use The Windows Heap So This Will Only Find A Subset Of Allocations, Mostly From OS DLLs. Find Memory Leaks Note: As With Heap Snapshots The Utility Of UMDH Is Greatly Reduced Now Because PartitionAlloc Everywhere Has Mostly Replaced The Windows Heap. The Windows Heap Manager Has A Really Useful Debug Flag, Where It Can Be Asked To Capture And Store A Stack Trace With Every Allocation. The Tool To Scrape These Stack Traces Out Of Processes Is UMDH, Which Comes With WinDbg. UMDH Is Great. It Will Capture A Snapshot Of The Heap State As Many Times As You Like, And It'll Do It Fairly Quickly. You Then Run It Again Against Either A Single Snapshot, Or A Pair Of Snapshots, At Which Time It'll Symbolize The Stack Traces And Aggregate Usage Up To Unique Stack Traces. Turning On The User Stack Trace Database For Chrome.exe With Gflags.exe Makes It Run Unbearably Slowly; However, Turning On The User Stack Trace Database On For The Browser Alone Is Just Fine. While It's Possible To Turn On The User Stack Database With The "!gflag" Debugging Extension, It's Too Late To Do This By The Time The Initial Debugger Breakpoint Hits. The Only Reasonable Way To Do This Is To Launch GFlags.exe, Enable The User Stack Trace Database (per Image Below), Launch Chrome Under The Debugger. Set A Breakpont When Chrome.dll Loads With "sxe Ld Chrome.dll". Step Up, To Allow Chrome.dll To Initialize. Disable The Stack Trace Database In GFlags.exe. Continue Chrome, Optionally Detaching The Debugger. Image GFlags.exe Settings For User Mode Stack Trace Database. If You Then Ever Suffer A Browser Memory Leak, You Can Snarf A Dump Of The Process With Umdh -p: > Chrome-browser-leak-umdh-dump.txt Which Can Then Typically Be "trivially" Analyzed To Find The Culprit. Miscellaneous Note That By Default Application Verifier Only Works With Non-official Builds Of Chromium. To Use Application Verifier On Official Builds You Need To Add --disable-features=RendererCodeIntegrity To Avoid Sandbox Crashes In Renderer Processes. See Crbug.com/1004989 For Details. See Also This Page. Application Verifier Is A Free Tool From Microsoft (available As Part Of The Windows SDK) That Can Be Used To Flush Out Programming Errors. Starting With M68 Application Verifier Can Be Enabled For Chrome.exe Without Needing To Disable The Sandbox. After Adding Chrome.exe To The List Of Applications To Be Stressed You Need To Expand The List Of Basics Checks And Disable The Leak Checks. You May Also Need To Disable Handles And Locks Checks Depending On Your Graphics Driver And Specific Chrome Version, But The Eventual Goal Is To Have Chrome Run With Handles And Locks Checks Enabled. When Bugs Are Found Chrome Will Trigger A Breakpoint So Running All Chrome Processes Under A Debugger Is Recommended. Chrome Will Run Much More Slowly Because Application Verifier Puts Every Heap Allocation On A Separate Page. Note That With PartitionAlloc Everywhere Most Chromium Allocations Don't Actually Go Through The Windows Heap And Are Therefore Unaffected By Application Verifier. You Can Check The Undocumented 'Cuzz' Checkbox In Application Verifier To Get The Windows Thread Scheduler To Add Some Extra Randomness In Order To Help Expose Race Conditions In Your Code. To Put A Breakpoint On CreateFile(), Add This Break Point: {,,kernel32.dll}_CreateFileW@28 {,,kernel32.dll} Specifies The DLL (context Operator). _ Prefix Means Extern "C". @28 Postfix Means _stdcall With The Stack Pop At The End Of The Function. I.e. The Number Of Arguments In BYTES. You Can Use DebugView From SysInternals Or Sawbuck To View LOG() Messages That Normally Go To Stderr On POSIX.” Subjects and Themes:

• Subjects: ➤  Debug - Build - Run - Compile - Chromium - Google - Chrome - Microsoft - Windows

Edition Identifiers:

• Internet Archive ID: debugging-chromium-on-windows

“BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?” Metadata:

• Title: ➤  BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?
• Author: BBC Archive

“BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?” Subjects and Themes:

• Subjects: Twitter - video - OnThisDay

Edition Identifiers:

• Internet Archive ID: twitter-1294657600684822531

“Paul Reas, "Myself, I Don't Think Any Job We Do Here Is Interesting, Because We Do Not See An End Product. We're Just Doing Little Bits For Something Else"” Metadata:

• Title: ➤  Paul Reas, "Myself, I Don't Think Any Job We Do Here Is Interesting, Because We Do Not See An End Product. We're Just Doing Little Bits For Something Else"
• Author: Reas, Paul (1955-)

Edition Identifiers:

• Internet Archive ID: FG0012309

“Don't Just Do Something, STAND THERE!” Metadata:

• Title: ➤  Don't Just Do Something, STAND THERE!
• Author: Pastor John Utley

“Don't Just Do Something, STAND THERE!” Subjects and Themes:

• Subjects: ➤  Bible - Jesus - God - Hurt - Pain - Worry - Suicide - Peace - Global Warming - Tree - Radiant - John - Utley - Radiant Word - Life - Hillary - Clinton - Britnay - Spears

Edition Identifiers:

• Internet Archive ID: ➤  PastorJohnUtleyDon_tJustDoSomething_STANDTHERE_

“Did Francis Just Do Something WORSE THAN PACHAMAMA?” Metadata:

• Title: ➤  Did Francis Just Do Something WORSE THAN PACHAMAMA?
• Author: Return To Tradition

“Did Francis Just Do Something WORSE THAN PACHAMAMA?” Subjects and Themes:

• Subjects: ➤  Youtube - video - People & Blogs - We Were Warned - Anthony Stein - Anthony Stine - Words for Eternal Life - Catholicism - God - pope francis latest news - pope francis retirement

Edition Identifiers:

• Internet Archive ID: youtube-8VRf32cHdI0

“Gal 14 Don't Do Something Just Stand There” Metadata:

• Title: ➤  Gal 14 Don't Do Something Just Stand There
• Author: Michael Cocoris

“Gal 14 Don't Do Something Just Stand There” Subjects and Themes:

• Subjects: Galatians - Bible - In depth

Edition Identifiers:

• Internet Archive ID: ➤  Gal14DontDoSomethingJustStandThere

“Hehe I'm Not #hacking - Just Learning How To Do Something New To Me. #Virtual OS On My Windows Computer - A Computer In A Computer -eJdrlYdH0ul” Metadata:

• Title: ➤  Hehe I'm Not #hacking - Just Learning How To Do Something New To Me. #Virtual OS On My Windows Computer - A Computer In A Computer -eJdrlYdH0ul
• Author: Kenneth Udut

“Hehe I'm Not #hacking - Just Learning How To Do Something New To Me. #Virtual OS On My Windows Computer - A Computer In A Computer -eJdrlYdH0ul” Subjects and Themes:

• Subjects: hacking - Vine - KennethUdut - Virtual

Edition Identifiers:

• Internet Archive ID: ➤  HeheIMNotHackingJustLearningHowToDoSomethingNewToMeVirtualOsOnMyWindowsComputer

“Drew Hernandez - Just Another Violent BLM Protester In NYC, Threatening Citizens For Driving On A Public Road Get Out Of The Street And Do Something Productive With Your Life Idiot, You Don’t Own The Street” Metadata:

• Title: ➤  Drew Hernandez - Just Another Violent BLM Protester In NYC, Threatening Citizens For Driving On A Public Road Get Out Of The Street And Do Something Productive With Your Life Idiot, You Don’t Own The Street
• Author: Drew Hernandez

“Drew Hernandez - Just Another Violent BLM Protester In NYC, Threatening Citizens For Driving On A Public Road Get Out Of The Street And Do Something Productive With Your Life Idiot, You Don’t Own The Street” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1295155150189805568

“Just Do Something - Khalil-Ghibran” Metadata:

• Title: ➤  Just Do Something - Khalil-Ghibran
• Author: Khalil-Ghibran

“Just Do Something - Khalil-Ghibran” Subjects and Themes:

• Subjects: self help - motivation - inspiration - laws of success - law of attraction

Edition Identifiers:

• Internet Archive ID: ➤  video20190302151640850byvideoshow

“Ninja McTits - Although I Hate It When Titles Look Like This, And Much Prefer Them Like This, I Wont Capitalize Every Word As Its Incredibly Annoying To Do With Titles This Long. Anyways Though, This Is Another Overly Long Lo-bit (low-bit) 8kbps Wall Thats Very Long With A Long Title That Nobody Will Bother To Listen To Nor Read, Yet I Feel Some Bizarre Drive To Make, When In Reality, I Would Rather Be Watching Anime Or Playing A Game (the Game) Instead (also, Lol, How Many Tracks Have I Made With That Theme?). Honestly Though, Isn't It Annoying When Like, You Want To Relax And Do Something, But Your Mind Is Just Too Dead Or Stressed To Do It? It Happens Far Too Often And Drives Me Insane. Also, I Forgot That I Wanted This Title To Just Be Nonsense And Not One Of These "noise Diaries". Does It Really Matter Though? I Feel Only A Few Will Read Titles Like This, Probably Just Antimatter Prism, Since They Like Absurdly Long Titles As Well. Maybe I Should Revive An Old Split Idea I Had With A Friend Where We Were Using Like, Entire Book PDFs As Titles, But My Titles Were So Incredibly Long That I Kept Having Problems Where Stuff Would Literally Just Crash (and You Thought These Song Titles Were Long, Lol). At Least The Songs Now Are [i]also[/i] (lol, How Else To Italicize Words In Titles?) Super Long Too, And Not Like, A Four Paragraph Title For A Second Long Track (which Is Honestly Funnier Though, Maybe This Should've Been One Of Those 0:00 Tracks, Which Btw, Got Me Featured In A Book Lol). [FULL TITLE IN DL]” Metadata:

• Title: ➤  Ninja McTits - Although I Hate It When Titles Look Like This, And Much Prefer Them Like This, I Wont Capitalize Every Word As Its Incredibly Annoying To Do With Titles This Long. Anyways Though, This Is Another Overly Long Lo-bit (low-bit) 8kbps Wall Thats Very Long With A Long Title That Nobody Will Bother To Listen To Nor Read, Yet I Feel Some Bizarre Drive To Make, When In Reality, I Would Rather Be Watching Anime Or Playing A Game (the Game) Instead (also, Lol, How Many Tracks Have I Made With That Theme?). Honestly Though, Isn't It Annoying When Like, You Want To Relax And Do Something, But Your Mind Is Just Too Dead Or Stressed To Do It? It Happens Far Too Often And Drives Me Insane. Also, I Forgot That I Wanted This Title To Just Be Nonsense And Not One Of These "noise Diaries". Does It Really Matter Though? I Feel Only A Few Will Read Titles Like This, Probably Just Antimatter Prism, Since They Like Absurdly Long Titles As Well. Maybe I Should Revive An Old Split Idea I Had With A Friend Where We Were Using Like, Entire Book PDFs As Titles, But My Titles Were So Incredibly Long That I Kept Having Problems Where Stuff Would Literally Just Crash (and You Thought These Song Titles Were Long, Lol). At Least The Songs Now Are [i]also[/i] (lol, How Else To Italicize Words In Titles?) Super Long Too, And Not Like, A Four Paragraph Title For A Second Long Track (which Is Honestly Funnier Though, Maybe This Should've Been One Of Those 0:00 Tracks, Which Btw, Got Me Featured In A Book Lol). [FULL TITLE IN DL]
• Author: Ninja McTits

Edition Identifiers:

• Internet Archive ID: ninja-mc-tits-462023

“Not Often Do You Get To Actually See The Exact Moment Someone Says Something That Just Kills The Vibe” Metadata:

• Title: ➤  Not Often Do You Get To Actually See The Exact Moment Someone Says Something That Just Kills The Vibe
• Author: streisandeffectbot

Edition Identifiers:

• Internet Archive ID: 855568002.mp4

“Love Is Just Something Lonely People Do” Metadata:

• Title: ➤  Love Is Just Something Lonely People Do
• Author: godoflaundrybasekts

“Love Is Just Something Lonely People Do” Subjects and Themes:

• Subjects: a: WitchyBee - f: the magnus archives - e: itpe2019

Edition Identifiers:

• Internet Archive ID: ➤  loveisjustsomethinglonelypeopledo

“192 Dont Just Do Something” Metadata:

• Title: 192 Dont Just Do Something
• Author: Osho
• Language: English

Edition Identifiers:

• Internet Archive ID: 192dontjustdosomething

“033-04 FOCUS: Don't Just Sit There, Do Something” Metadata:

• Title: ➤  033-04 FOCUS: Don't Just Sit There, Do Something
• Author: Jeff Mikels

“033-04 FOCUS: Don't Just Sit There, Do Something” Subjects and Themes:

• Subjects: sermon - christian - bible - church

Edition Identifiers:

• Internet Archive ID: ➤  033_04__FOCUS__Don_t_Just_Sit_There__Do_Something_video

“Don'y Just Do Something. Sit There!” Metadata:

• Title: ➤  Don'y Just Do Something. Sit There!
• Author: ➤  Westside Church of Christ: Bakersfield

Edition Identifiers:

• Internet Archive ID: ➤  pwo8bcm1dzlvcgs6mta8xufsblcjt3szwauq8bgg

“Just Do Something” Metadata:

• Title: Just Do Something
• Author: Wanita's War Room

Edition Identifiers:

• Internet Archive ID: ➤  pz8wq3ltdfu77dmo4apsx6doivwe4nknsrqluq9z

“033-04 FOCUS: Don't Just Sit There, Do Something” Metadata:

• Title: ➤  033-04 FOCUS: Don't Just Sit There, Do Something
• Author: Jeff Mikels

“033-04 FOCUS: Don't Just Sit There, Do Something” Subjects and Themes:

• Subjects: sermon - christian - bible - church

Edition Identifiers:

• Internet Archive ID: ➤  033_04__FOCUS__Don_t_Just_Sit_There__Do_Something_audio

“N3KN-H5H7: Don’t Just Do Something—Stand There! A Modest Pro…” Metadata:

• Title: ➤  N3KN-H5H7: Don’t Just Do Something—Stand There! A Modest Pro…

Edition Identifiers:

• Internet Archive ID: perma_cc_N3KN-H5H7

“AEE 916: Just A Friendly Reminder! 5 Ways To Get Someone To Do Something In English” Metadata:

• Title: ➤  AEE 916: Just A Friendly Reminder! 5 Ways To Get Someone To Do Something In English
• Author: All Ears English Podcast

“AEE 916: Just A Friendly Reminder! 5 Ways To Get Someone To Do Something In English” Subjects and Themes:

• Subjects: ➤  Podcast - american - conversation - english - esl - everydayenglish - ielts - instruction - language - learn - lessons - real - teacher - toefl - universityvocabulary

Edition Identifiers:

• Internet Archive ID: ➤  8kiuhojsrollszk3y7klfffwd4xuculjucxrzd4e

“Don't Just Do Something” Metadata:

• Title: Don't Just Do Something
• Language: English

Edition Identifiers:

• Internet Archive ID: dontjustdosometh0000unse_m8i5

“Don't Just Do Something” Metadata:

• Title: Don't Just Do Something
• Author: Center Magazine
• Language: English

Edition Identifiers:

• Internet Archive ID: dontjustdosometh0000cent

“When I Suddenly Have To Do Something I Didn't Know About Until Just Now And I Have To Act Immediately. -eI6jad7FQZm” Metadata:

• Title: ➤  When I Suddenly Have To Do Something I Didn't Know About Until Just Now And I Have To Act Immediately. -eI6jad7FQZm
• Author: Kenneth Udut

“When I Suddenly Have To Do Something I Didn't Know About Until Just Now And I Have To Act Immediately. -eI6jad7FQZm” Subjects and Themes:

• Subjects: Vine - KennethUdut

Edition Identifiers:

• Internet Archive ID: ➤  WhenISuddenlyHaveToDoSomethingIDidnTKnowAboutUntilJustNowAndIHaveToActImmediate

“Something I Do When I Use Movie Maker Just For Fun” Metadata:

• Title: ➤  Something I Do When I Use Movie Maker Just For Fun
• Author: Firey Plush

Edition Identifiers:

• Internet Archive ID: ➤  somethingidowheniusemoviemakerjustforfun

“END OF THE CENTURY "I Just Wanna Have Something To Do" At Elysium, Austin, Tx. July 26, 2013” Metadata:

• Title: ➤  END OF THE CENTURY "I Just Wanna Have Something To Do" At Elysium, Austin, Tx. July 26, 2013
• Author: rAwTiMe

“END OF THE CENTURY "I Just Wanna Have Something To Do" At Elysium, Austin, Tx. July 26, 2013” Subjects and Themes:

• Subjects: ➤  Youtube - video - Music - davetv - capzeyez - indie - diy - hd - live - music - unsigned - local - Texas - Austin - rock - metal - punk - blues - folk - comedy - ramones - tribute - cover - ramones tribute band - ramones tribute - Ramones (Musical Group) - ramones cover - ramones cover band

Edition Identifiers:

• Internet Archive ID: youtube-sSMl04p0ZIg

“Oh There You Are Professor I Was Just Wondering If I Do Something For Some Extra Cred| !merch” Metadata:

• Title: ➤  Oh There You Are Professor I Was Just Wondering If I Do Something For Some Extra Cred| !merch
• Author: Scarra

“Oh There You Are Professor I Was Just Wondering If I Do Something For Some Extra Cred| !merch” Subjects and Themes:

• Subjects: TwitchVod - video

Edition Identifiers:

• Internet Archive ID: twitch-vod-v1890368682

“I Had To. I Just Can't Get Enough Of #snoopy And The #bunnies #dubstep #dropthebass #dog I Should Do Something Else Now XD It's So Much Fun!-MqrFOeeziU3.mp4 I Had To I Just Cant Get Enough Of Snoopy And The Bunnies Dubstep Dropthebass Dog I Should Do Something Else Now XD Its So Much Fun MqrFOeeziU3 Mp4 Snoopy Bunnies Dubstep Dropthebass Dog” Metadata:

• Title: ➤  I Had To. I Just Can't Get Enough Of #snoopy And The #bunnies #dubstep #dropthebass #dog I Should Do Something Else Now XD It's So Much Fun!-MqrFOeeziU3.mp4 I Had To I Just Cant Get Enough Of Snoopy And The Bunnies Dubstep Dropthebass Dog I Should Do Something Else Now XD Its So Much Fun MqrFOeeziU3 Mp4 Snoopy Bunnies Dubstep Dropthebass Dog
• Author: Kenneth Udut

“I Had To. I Just Can't Get Enough Of #snoopy And The #bunnies #dubstep #dropthebass #dog I Should Do Something Else Now XD It's So Much Fun!-MqrFOeeziU3.mp4 I Had To I Just Cant Get Enough Of Snoopy And The Bunnies Dubstep Dropthebass Dog I Should Do Something Else Now XD Its So Much Fun MqrFOeeziU3 Mp4 Snoopy Bunnies Dubstep Dropthebass Dog” Subjects and Themes:

• Subjects: ➤  support - pursue - catch - snoopy - bunnies - dubstep - dropthebass - dog - Vine - KennethUdut

Edition Identifiers:

• Internet Archive ID: ➤  IHadToIJustCantGetEnoughOfSnoopyAndTheBunniesDubstepDropthebassDogIShouldDoSom

“ABC News - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."” Metadata:

• Title: ➤  ABC News - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."
• Author: ABC News

“ABC News - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1310253959685246976

“2fy A.k.a K-rock And Mike Watson Just Do In Just A Little Something... 3g2” Metadata:

• Title: ➤  2fy A.k.a K-rock And Mike Watson Just Do In Just A Little Something... 3g2
• Author: 2fy
• Language: English

“2fy A.k.a K-rock And Mike Watson Just Do In Just A Little Something... 3g2” Subjects and Themes:

• Subjects: ➤  Animation - Robotic - Waves - Jeans - Head - dance

Edition Identifiers:

• Internet Archive ID: ➤  2fy-a.k.a-k-rock-and-mike-watson-just-doin-just-a-little-something...-3g-2

“All Good No Worries - Searching For Something To Watch While You Get Ready Today? You Just Found It. 😉 Watch @RIPmika & @ElyseWillems Do Their Makeup (as Well As Jennifer Coolidge Impressions?) In The Newest Let's Blend! Tap Here For The Best Vibes: ✨” Metadata:

• Title: ➤  All Good No Worries - Searching For Something To Watch While You Get Ready Today? You Just Found It. 😉 Watch @RIPmika & @ElyseWillems Do Their Makeup (as Well As Jennifer Coolidge Impressions?) In The Newest Let's Blend! Tap Here For The Best Vibes: ✨
• Author: All Good No Worries

“All Good No Worries - Searching For Something To Watch While You Get Ready Today? You Just Found It. 😉 Watch @RIPmika & @ElyseWillems Do Their Makeup (as Well As Jennifer Coolidge Impressions?) In The Newest Let's Blend! Tap Here For The Best Vibes: ✨” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1676956576228474883

“Just Because Government CAN Do Something Doesn't Mean It Should. And Usually It Shouldn't. #shorts” Metadata:

• Title: ➤  Just Because Government CAN Do Something Doesn't Mean It Should. And Usually It Shouldn't. #shorts
• Author: Tenth Amendment Center

“Just Because Government CAN Do Something Doesn't Mean It Should. And Usually It Shouldn't. #shorts” Subjects and Themes:

• Subjects: Youtube - video - News & Politics

Edition Identifiers:

• Internet Archive ID: youtube-82zWku3u2tc

“Don't Just Do Something, Stand There! : Ten Principles For Leading Meetings That Matter” Metadata:

• Title: ➤  Don't Just Do Something, Stand There! : Ten Principles For Leading Meetings That Matter
• Author: Weisbord, Marvin Ross
• Language: English

“Don't Just Do Something, Stand There! : Ten Principles For Leading Meetings That Matter” Subjects and Themes:

• Subjects: Business meetings - Meetings

Edition Identifiers:

• Internet Archive ID: dontjustdosometh0000weis

“Illinois Just Became First State To Do Something EVERY Other Country Does” Metadata:

• Title: ➤  Illinois Just Became First State To Do Something EVERY Other Country Does
• Author: Dangerous Ideas with Lee Camp

“Illinois Just Became First State To Do Something EVERY Other Country Does” Subjects and Themes:

• Subjects: ➤  Youtube - video - Entertainment - jimmy dore - russel brand - comedy news

Edition Identifiers:

• Internet Archive ID: youtube-VnFyjCC6WQU

“ABC News Politics - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."” Metadata:

• Title: ➤  ABC News Politics - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."
• Author: ABC News Politics

“ABC News Politics - Joe Biden Urges Senators To Listen To Voters Before Voting On Confirmation Of Amy Coney Barrett For The Supreme Court: "Just Because You Have The Power To Do Something Doesn't Absolve You Of Your Responsibility To Do Right By The American People."” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1310254016052559872

“05 28 2017 Phelps Milestones Dont Just Do Something Stand There” Metadata:

• Title: ➤  05 28 2017 Phelps Milestones Dont Just Do Something Stand There
• Author: Dean Phelps

Edition Identifiers:

• Internet Archive ID: ➤  05282017PhelpsMilestonesDontJustDoSomethingStandThere

“BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?” Metadata:

• Title: ➤  BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?
• Author: BBC Archive

“BBC Archive - #OnThisDay 1974: Stickleback Fishing, Gardening, Electrical Engineering And Driving Miniature Steam Engines... ...just Some Of The Things Boys Were Doing Instead Of Watching Why Don't You Just Turn Off Your Television Set And Go And Do Something Less Boring Instead?” Subjects and Themes:

• Subjects: Twitter - video - OnThisDay

Edition Identifiers:

• Internet Archive ID: twitter-1161994108526825472

“Kamala Harris - Sat Down With @FullFrontalSamB To Talk About Why An Investment In Our Nation's Teachers Is Just The Right Thing To Do. Paying Teachers Their Value Should Be Something We Can All Agree On.” Metadata:

• Title: ➤  Kamala Harris - Sat Down With @FullFrontalSamB To Talk About Why An Investment In Our Nation's Teachers Is Just The Right Thing To Do. Paying Teachers Their Value Should Be Something We Can All Agree On.
• Author: Kamala Harris

“Kamala Harris - Sat Down With @FullFrontalSamB To Talk About Why An Investment In Our Nation's Teachers Is Just The Right Thing To Do. Paying Teachers Their Value Should Be Something We Can All Agree On.” Subjects and Themes:

• Subjects: Twitter - video

Edition Identifiers:

• Internet Archive ID: twitter-1129025302489980929

“Just Do Something : A Liberating Approach To Finding God's Will” Metadata:

• Title: ➤  Just Do Something : A Liberating Approach To Finding God's Will
• Author: DeYoung, Kevin
• Language: English

“Just Do Something : A Liberating Approach To Finding God's Will” Subjects and Themes:

• Subjects: ➤  Young adults - God (Christianity) - Discernment (Christian theology) - Christian life

Edition Identifiers:

• Internet Archive ID: isbn_9780802458384

“It Brings Us So Much Joy To See How Popular The Kufiya Has Become Around The World! People From Every Corner Of The World Are Wearing Their Kufiyas As An Expression Of Protest Against Injustice And Oppression. Omar Shares His Experience, Seeing Numerous People Wearing The Kufiya, Something That Previously Was Uncommon On A Global Scale. Just This Past Weekend, Huge Demonstrations Took Place, Including One In Washington D.C., Where Over 400,000 Pro-Palestinians Protested Against The Ongoing Genocide In Palestine. We Urge All Of You To Continue Wearing Your Kufiyas And To Acknowledge Those Who Do So With A Smile, A Kind Comment, Or Any Form Of Appreciation For Their Courage And Solidarity With The Palestinian Cause. @MEST #hirbawi #kufiya #keffiyeh #kuffiyeh #kuffiyah” Metadata:

• Title: ➤  It Brings Us So Much Joy To See How Popular The Kufiya Has Become Around The World! People From Every Corner Of The World Are Wearing Their Kufiyas As An Expression Of Protest Against Injustice And Oppression. Omar Shares His Experience, Seeing Numerous People Wearing The Kufiya, Something That Previously Was Uncommon On A Global Scale. Just This Past Weekend, Huge Demonstrations Took Place, Including One In Washington D.C., Where Over 400,000 Pro-Palestinians Protested Against The Ongoing Genocide In Palestine. We Urge All Of You To Continue Wearing Your Kufiyas And To Acknowledge Those Who Do So With A Smile, A Kind Comment, Or Any Form Of Appreciation For Their Courage And Solidarity With The Palestinian Cause. @MEST #hirbawi #kufiya #keffiyeh #kuffiyeh #kuffiyah
• Author: hirbawikufiya

“It Brings Us So Much Joy To See How Popular The Kufiya Has Become Around The World! People From Every Corner Of The World Are Wearing Their Kufiyas As An Expression Of Protest Against Injustice And Oppression. Omar Shares His Experience, Seeing Numerous People Wearing The Kufiya, Something That Previously Was Uncommon On A Global Scale. Just This Past Weekend, Huge Demonstrations Took Place, Including One In Washington D.C., Where Over 400,000 Pro-Palestinians Protested Against The Ongoing Genocide In Palestine. We Urge All Of You To Continue Wearing Your Kufiyas And To Acknowledge Those Who Do So With A Smile, A Kind Comment, Or Any Form Of Appreciation For Their Courage And Solidarity With The Palestinian Cause. @MEST #hirbawi #kufiya #keffiyeh #kuffiyeh #kuffiyah” Subjects and Themes:

• Subjects: TikTok - video

Edition Identifiers:

• Internet Archive ID: TikTok-7324431899546356999

“Don't Just Do Something, Sit There : New Maxims To Refresh And Enrich Your Life” Metadata:

• Title: ➤  Don't Just Do Something, Sit There : New Maxims To Refresh And Enrich Your Life
• Author: Eyre, Richard M
• Language: English

“Don't Just Do Something, Sit There : New Maxims To Refresh And Enrich Your Life” Subjects and Themes:

• Subjects: Maxims - Proverbs

Edition Identifiers:

• Internet Archive ID: dontjustdosometh00eyre

“Mike Bloomberg - I Know If I Were Black My Success Would Have Been A Lot Harder To Achieve. That's Just A Fact, And We've Got To Do Something About It Rather Than Just Demagogue About It. #DemDebate” Metadata:

• Title: ➤  Mike Bloomberg - I Know If I Were Black My Success Would Have Been A Lot Harder To Achieve. That's Just A Fact, And We've Got To Do Something About It Rather Than Just Demagogue About It. #DemDebate
• Author: Mike Bloomberg

“Mike Bloomberg - I Know If I Were Black My Success Would Have Been A Lot Harder To Achieve. That's Just A Fact, And We've Got To Do Something About It Rather Than Just Demagogue About It. #DemDebate” Subjects and Themes:

• Subjects: Twitter - video - DemDebate

Edition Identifiers:

• Internet Archive ID: twitter-1232477919810850816

“Darshan Diary: Don't Just Do Something, Sit There” Metadata:

• Title: ➤  Darshan Diary: Don't Just Do Something, Sit There
• Author: Rajneesh, Bhagwan Shree
• Language: English

Edition Identifiers:

• Internet Archive ID: gtu_32400001196389

“Unless We Do Something, They'll Just Keep Killing Us” Metadata:

• Title: ➤  Unless We Do Something, They'll Just Keep Killing Us
• Author: The Jolly Heretic

“Unless We Do Something, They'll Just Keep Killing Us” Subjects and Themes:

• Subjects: ➤  Youtube - video - Science & Technology - evolution - intelligence - personality - psychology - evolutionary psychology - selection - race - sex - religion

Edition Identifiers:

• Internet Archive ID: youtube-KzMhDyVKkeo

“"Don’t Just Talk About Standing With Veterans—don’t Just Talk About Me—do Something To Support Our Veterans" —@POTUS Https://t.co/MQJiRQ5CRQ” Metadata:

• Title: ➤  "Don’t Just Talk About Standing With Veterans—don’t Just Talk About Me—do Something To Support Our Veterans" —@POTUS Https://t.co/MQJiRQ5CRQ
• Author: The White House

“"Don’t Just Talk About Standing With Veterans—don’t Just Talk About Me—do Something To Support Our Veterans" —@POTUS Https://t.co/MQJiRQ5CRQ” Subjects and Themes:

• Subjects: ➤  videobot - archiveteam - twitter - twitter.com - 760192921643515905 - The White House

Edition Identifiers:

• Internet Archive ID: ➤  archiveteam_videobot_twitter_com_760192921643515905

“Don't Just Stand There, Do Something!” Metadata:

• Title: ➤  Don't Just Stand There, Do Something!
• Author: Ty Orr

“Don't Just Stand There, Do Something!” Subjects and Themes:

• Subjects: ➤  Mark - Bible - Gospel - Jesus - Christ - Church - Sermon - Watersprings

Edition Identifiers:

• Internet Archive ID: DontJustStandThereDoSomething

“It Just Got A WHOLE LOT WORSE! Will We Do Something NOW!! CPS Wants Your Kids” Metadata:

• Title: ➤  It Just Got A WHOLE LOT WORSE! Will We Do Something NOW!! CPS Wants Your Kids
• Author: Our Free Society

“It Just Got A WHOLE LOT WORSE! Will We Do Something NOW!! CPS Wants Your Kids” Subjects and Themes:

• Subjects: ➤  Youtube - video - Nonprofits & Activism - CPS - Tyranny - Stolen Kids - Child Trafficking - Medical Tyranny - Sexual Abuse - Child Protection Agency - don't talk to CPS

Edition Identifiers:

• Internet Archive ID: youtube-RDYMrLcVzyc

“BBC Archive - #OnThisDay 1973: Why Don't You... Just Switch Off Your Television Set And Go And Do Something Less Boring Instead? Was First Broadcast. It Looked Like This. No Theme Tune.” Metadata:

• Title: ➤  BBC Archive - #OnThisDay 1973: Why Don't You... Just Switch Off Your Television Set And Go And Do Something Less Boring Instead? Was First Broadcast. It Looked Like This. No Theme Tune.
• Author: BBC Archive

“BBC Archive - #OnThisDay 1973: Why Don't You... Just Switch Off Your Television Set And Go And Do Something Less Boring Instead? Was First Broadcast. It Looked Like This. No Theme Tune.” Subjects and Themes:

• Subjects: Twitter - video - OnThisDay

Edition Identifiers:

• Internet Archive ID: twitter-1163711010596892672