I'm running a Chrome Extension on a Windows 10 computer but sometimes it crashes and it's always when I'm not in front of the computer. I'd like to find a way to see what happened and find out the reason of the crash.
I have started chrome in debug mode with this:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" ---enable-logging --v=1 ---vmmodule ---no-sandbox
I can't find a chrome_debug.log anywhere.
I see a couple of DMP files in the Chrome folder. I have tried to edit them with Windbg but the information I get out of it is very limited:
*** WARNING: Unable to verify checksum for chrome_child.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for chrome_child.dll -
rax=00000000aae79636 rbx=000266be30311920 rcx=000002d27ba72f40
rdx=000002d27ba76380 rsi=000000000000b880 rdi=0000000002b801d0
rip=00007ff802feaf07 rsp=000000f125dfdde0 rbp=000000f125dfde00
r8=0000000000000000 r9=0000000000000140 r10=000002d200005c00
r11=0000000000000000 r12=0000000000000003 r13=00007ff8074875a9
r14=000002d27ddb0820 r15=0000518316a04000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=0000 ds=0000 es=0000 fs=0053 gs=002b efl=00010206
chrome_child!ChromeMain+0x419517:
00007ff8`02feaf07 3b03 cmp eax,dword ptr [rbx] ds:000266be`30311920=????????
That doesnt help me much unfortunately. My browser console crashed with the extension so I can't see there what happened. If I could may be have active logging on the console, that could help but I don't know how to do this.
The extension sometimes run fine for a couple of days and then suddenly it crashes, I don't really see a pattern here.
I have taken the "massage" option from wOxxOm here below and I get more information but again, it's not something that helps me very much as I don't see something related to the chrome extension:
Any idea?
Thanks!
Related
I'm trying to print pdf from Gmail with headless chrome in command line.
I cannot install pupeteer or another tool with the computer that script will run on, due to unability to install anything.
For simple gsuite pages such as https://myaccount.google.com/, my script runs perfectly.
For more complex ones such as gmail, the output PDF I get shows a partially loaded page:
output PDF
I'm already using the --run-all-compositor-stages-before-draw option which should wait for the page to resolve before printing.
I've tried to add --virtual-time-budget=10000 just before --run-all-compositor-stages-before-draw, however if I ask for more than 2000 milliseconds the command runs for ever without producing the output pdf.
See my code so far below (which I put in a .bat file)
Does anyone have encountered that issue ? Any lead on how to solve it ? Any ways to first load the page, then have a timeout command, then print to pdf ?
I couldn't find a solution so far on the web.
Thanks :)
Ps: english isn't my primary language, please excuse any mistake
#set outputFile=C:\Users\MyUserName\Temp\testPDFprintChromeheadless\test.pdf
#set chromeDirectory=C:\Program Files (x86)\Google\Chrome\Application
#set url=https://mail.google.com/mail/
#set userData=C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data
#set profile=MyChromeProfile
#set useragentChrome="Mozilla/5.0 (X11\\; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.50 Safari/537.36"
#cd "%chromeDirectory%"
chrome.exe --headless --disable-gpu --profile-directory="%profile%" --user-data-dir="%userData%" --user-agent=%useragentChrome% --run-all-compositor-stages-before-draw --print-to-pdf="%outputFile%" --print-to-pdf-no-header "%url%"
pause
Edit :
Here are the logs I get.
AccÞs refusÚ means Accès refusé which is french for Access denied.
I don't have administrator rights on this computer, thus not able to write within the Chrome directory, that could explain this access denied.
[0820/101506.995:ERROR:cache_util_win.cc(20)] Unable to move the cache: AccÞs refusÚ. (0x5)
[0820/101506.996:ERROR:cache_util.cc(144)] Unable to move cache folder C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\GPUCache to C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\old_GPUCache_000
[0820/101506.997:ERROR:disk_cache.cc(184)] Unable to create cache
[0820/101506.997:ERROR:shader_disk_cache.cc(606)] Shader Cache Creation failed: -2
[0820/101509.033:ERROR:cache_util_win.cc(20)] Unable to move the cache: AccÞs refusÚ. (0x5)
[0820/101509.034:ERROR:cache_util.cc(144)] Unable to move cache folder C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\Cache to C:\Users\MyUserName\AppData\Local\Google\Chrome\User Data\Default\old_Cache_000
[0820/101509.035:ERROR:disk_cache.cc(184)] Unable to create cache
[0820/101510.020:ERROR:service_worker_storage.cc(1899)] Failed to delete the database: Database IO error
[0820/101513.168:INFO:CONSOLE(1763)] "Deprecated API for given entry type.", source: https://mail.google.com/_/scs/mail-static/_/js/k=gmail.main.fr.YnGL5qwRpj4.O/am=rvxfykdgoP_swM-GUSAcAAM5SAABYIUsYuW09wdKmv8BAwAGoG_F8GAQrnkAdJzCuAQAAAAAAAAAAAAAAAAAAADsAisGAQ/d=1/exm=b/ed=1/im=1/dg=0/br=1/wt=1/rs=AHGWq9AzRZEBJ1Ek7NOabODYvaA7PPmCUQ/cb=loaded_1/m=a (1763)
[0820/101519.465:INFO:headless_shell.cc(648)] Written to file C:\Users\MyUserName\Temp\testPDFprintChromeheadless\test.pdf.
Today when I start report builder from the start menu I see the splash screen then it closes.
I tried deleting temp files and files under "C:\Users\me\AppData\Local\Apps\2.0"
For testing I created a new local windows account and installed it again there and it launched fine.
Any ideas?
In the event viewer I found this:
Application: MSReportBuilder.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
at System.Xml.XmlTextReaderImpl.Throw(System.Exception)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(System.Xml.XmlDocument, System.Xml.XmlReader, Boolean)
at System.Xml.XmlDocument.Load(System.Xml.XmlReader)
at System.Xml.XmlDocument.Load(System.String)
at Microsoft.ReportDesigner.Properties.Settings+RBSettingsProvider.GetReader(System.String)
at Microsoft.ReportDesigner.Properties.Settings+RBSettingsProvider.GetUserScopedReader()
at Microsoft.ReportDesigner.Properties.Settings+RBSettingsProvider.GetPropertyValues(System.Configuration.SettingsContext, System.Configuration.SettingsPropertyCollection)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(System.Configuration.SettingsProvider)
at System.Configuration.SettingsBase.GetPropertyValueByName(System.String)
at System.Configuration.SettingsBase.get_Item(System.String)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(System.String)
at System.Configuration.ApplicationSettingsBase.get_Item(System.String)
at Microsoft.ReportDesigner.Properties.Settings.get_RecentDataSources()
at Microsoft.ReportDesigner.ApplicationSettings.get_Settings()
at Microsoft.ReportDesigner.ReportDesigner.LoadAppConfigWndSize()
at Microsoft.ReportDesigner.ReportDesigner..ctor()
at Microsoft.ReportDesigner.ReportDesigner..ctor(Microsoft.ReportDesigner.AppArguments)
at Microsoft.ReportDesigner.Program.Main(System.String[])
What fixed this for me was the user.config file in the local report builder folder was # 0kb so I replaced it with another one off another computer and it works just fine now.
Yeah look under users home AppData/Local/Microsoft and try deleting or renaming "Report Builder" folder. Sometimes the app messes some preferences and then crashes. That worked for me (might be also localLow or roaming folders) – sproketboy Feb 25 at 22:11
The solution provided by sproketboy in their comment on Feb 25 at 22:11 worked for me. Given that it actually solved this situation for me, I'm re-posting it here as an answer.
I've been searching for a while now and I can't find the exact list of all fail to load error code/error description of google chrome.
I'm talking about this the highlighted text
Can someone give me a link?
I did some digging and I must admit, it's not easy to find a full exhaustive list of all (Chromium) networking error codes.
The full list of all Chromium error codes can be found in the file net_error_list.h:
https://cs.chromium.org/chromium/src/net/base/net_error_list.h
It looks like Google Chrome prepends ERR_ to all the codes listed in the above list.
However, error codes in XHR error responses are slightly different. These codes follow the format of the linux system file errno.h as defined by POSIX.1-2001, or C99:
http://man7.org/linux/man-pages/man3/errno.3.html
Finally, some common NodeJS errors have been listed at the NodeJS API Documentation:
https://nodejs.org/api/errors.html#errors_common_system_errors
I'd like to end this answer with a simple comparison example. The error of an operation timeout would be named as follows by the listed 'standards':
TIMED_OUT internally in Chromium.
ERR_TIMED_OUT displayed in Google Chrome.
ETIMEDOUT in the XHR error object (error.code).
Using your example:
CONNECTION_REFUSED -> internally in Chromium
ERR_CONNECTION_REFUSED -> displayed in Google Chrome
ECONNREFUSED -> in linux (POSIX.1) or network error stacks
By the way for only listing all error codes
USE :
chrome://network-errors/
It's about 220 in total as of now in chrome version (69.0.3497.100)
I have chromium Version 97.0.4692.71 (Official Build), snap (32 bit), on Description: Ubuntu 18.04.6 LTS. The problem was solved using the command in the terminal
chromium --no-sandbox
after that everything worked.
I'm doing automated tests with Chrome.
Part of my suite needs flash to be activated (sight...).
I'm struggling to activate it. Here's what I got:
If I open a regular chrome session, with Flash checked in chrome://plugins, it works there:
When the tests start, the command line executed is:
▶ ps -edf | grep chrome
augustin 24752 24743 2 12:12 pts/0 00:00:07 /opt/google/chrome/chrome --user-data-dir=/tmp/karma-22735678 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling http://test.example.com:8080/?id=22735678
I always get Download failed or sometimes flash version outdated.
Even if I check flash in plugins and reload, even if I allow it specifically for this tab and refresh:
I tried several command line options:
--always-authorize-plugins from there
--enable-plugins from there
without sucess. :(
Thanks for the help
EDIT:
If I click on + details in chrome://plugins, I can see that in a regular session, Location is set to /home/augustin/.config/google-chrome/PepperFlash/23.0.0.207/libpepflashplayer.so
, while, in the command-lined open I get: Location: internal-not-yet-present
This might be the explanation, though I still don't know how to fix it.
I made it by copying the content of /home/augustin/.config/google-chrome/PepperFlash/* into /opt/google/chrome/PepperFlash, chmod -r +rx /opt/google/chrome/PepperFlash and then adding the following flags to the launcher :
customLaunchers: {
Chrome_plugins: {
base: 'Chrome',
flags: ['--ppapi-flash-path=/opt/google/chrome/PepperFlash/23.0.0.207/libpepflashplayer.so', '--enable-plugins', '--always-authorize-plugins']
}
},
Not very plug&play, neither compatible with other laptops, but at least works.
A more robust solution would be welcome!
I am facing some odd situation that when I select/deselect the features in the feature customization wizard, it sometimes crashes the window. It does not give any clue at all. It also not happens consistently.
Do you have any idea or faced such kind of issue? I am able to even trace the root cause using install log.
You may be able to get closer to isolating the problem if you turn on the Debug policy. Do this by setting HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer's Debug value to (dword) 7 in as described on the Windows Installer team blog. You will then need to use a tool like DebugView to view the extra output that Windows Installer will generate. Note you may have to restart the "msiserver" service for the policy to take effect. Best luck making sense of what it shows; often it's just a lot of SQL query dumps.
You can sometimes grab MSI exceptions from out of the event log, but they won't always tell you much.
Instead what you can do is turn on logging of the MSI, this can be done either via the registry, or via the command line. To find out about the registry option, visit this MS Support article. To do it from the command line you can use the same switches, but they obviously will only last for that one install. This is a snapshot as gathered from msiexec:
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
To take advantage of these options, use msiexec directly:
msiexec.exe [path to your msi] /l [your options]