breakpad | Google Breakpad , a multi-platform crash reporting system | Code Inspection library

I'm using Puppeteer.js to crawl some URL. I'm using the default Chromium browser of Puppeteer.
All is working well, but the problem is, that when I run the crawling script, and doing other things in the background and the focus is no longer on the Chromium browser of Puppeteer, it's not working: waiting for elements way too long, and abort operations, or in other words: puppeteer is paused (or freeze).

P.S, I'm also using puppeteer-extra and puppeteer-extra-plugin-stealth NPM packages for advance options.

Here is how I create the browser and the page:

I'm trying to create this lambda function in AWS using Amplify however when I try to launch the chromium the lambda function does not return any value and the function end up timing up:

"errorMessage": "2020-12-09T02:56:56.210Z 57402f8e-9fb2-4341-837d-bdf2ee6e9262 Task timed out after 25.57 seconds" I add the Layer as suggested by @James Shapiro, now I'm getting a URL return for the chromium but it still not launching it:

This is my function:

I'm trying to run a simple Azure Function that would enter page and generate a PDF depending on what is visible in a browser.

I created a NodeJS 12 Azure Function with Linux Consumption Plan (B1). I set PLAYWRIGHT_BROWSERS_PATH to 0.

Function code looks like this:

Tell us about your environment:

Puppeteer version: 1.11.0 Platform / OS version: Windows 10 1709 URLs (if applicable): Node.js version: 10.x.x as well as 11.4.0 What steps will reproduce the problem?

const puppeteer = require("puppeteer"); puppeteer.launch(); What is the expected result? A headless browser launching in the background and no console error.

What happens instead? chrome.exe is run without any command line switch, opening a non-headless window and eventually the tab also crashes, until it is killed by Puppeteer.

• OS : win10 64 bits
• compiler : vc2017 64bits
• vlc version : 3.0.9.2 from here

Source codes

Following the VLC macOSCompile wiki page. Using the single command build instructions. I'm running 10.14.6 with Xcode 11.3.1 commandline tools, developer signed, etc.

Important note -- my MacOSX.sdk file is located here: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk

All is good through build to create makefile, completes bootstrap and runs make. Then I get the following error -- how do I point VLC to the location where my MacOSX.sdk file is located?

IOW how do I set vlc's "contrib environment"?

Please note in the code snip below, that contrib sets the MacOSX.sdk file pointer to the WRONG location - how do I fix?

Do I need to edit something in the vlc source? Thanks. errors:

I have a C++ application that is crashing on startup for some Windows 7 users. I can't reproduce the error on my own machine, but used breakpad to generate a .dmp file, which shows that the code is crashing with "Illegal instruction" initializing a static std::vector array. What could this possibly mean?

Exception: Unhandled exception at 0x000000013F121362 (myApp.exe) in myApp.exe.4328.dmp: 0xC000001D:

Illegal Instruction.myApp.exe! dynamic initializer for Keyboard::key_freqs_() Line 11 C++

The source at that line:

I am running chrome driver over selenium on a ubuntu server. Behind a residential proxy network . Yet my selenium is being detected . Is there a way to make chrome driver and selenium 100% undetectable ?

I have been trying for so long I lost track of the many things I have done including:

1. Trying different versions of chrome
2. Adding several flags and removing some words from the chrome driver file.
3. Running it behind a proxy (residential ones also) using incognito mode.
4. Loading profiles.
5. Random mouse movements.
6. Randomising everything.

I am looking for a true version of selenium that is 100% undetectable . if that ever existed .or another automation way that is not detectable by bot trackers .

This is part of the starting of the browser

The following comment in breakpad suggests that resetting the signal handler forces the signal to be rethrown. However, I wasn't able to find any documentation online that describes this behaviour.

Additionally, the comment here says once the signal handler returns, the signal will be rethrown. Is this also as a result of the signal handler being restored or reset to the default?