status
stringclasses 1
value | repo_name
stringlengths 9
24
| repo_url
stringlengths 28
43
| issue_id
int64 1
104k
| updated_files
stringlengths 8
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 37
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
timestamp[ns, tz=UTC] | language
stringclasses 5
values | commit_datetime
timestamp[us, tz=UTC] |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,744 |
["shell/browser/net/system_network_context_manager.cc"]
|
Flash SWF content not correctly loaded in Electron 7
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0
* **Operating System:**
* Windows 10 (1803)
* **Last Known Working Electron version:**
* 6.1.2
### Expected Behavior
Loading flash content through an swf file results in the correct visualization of said content
### Actual Behavior
An error "GET http://interactive-mirror3.nfb.ca/FrameLoader.swf net::ERR_INVALID_ARGUMENT" appears:
### To Reproduce
Try embedding this flash website in an electron project (http://bear71.nfb.ca/#/bear71) following this tutorial: https://electronjs.org/docs/tutorial/using-pepper-flash-plugin
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/20744
|
https://github.com/electron/electron/pull/22072
|
058222a9f1527698180e18e2ad64f1b714451d60
|
43592f8b719f8d5ec7031f0e1e664d63e42ca064
| 2019-10-25T15:07:38Z |
c++
| 2020-02-09T01:50:07Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,737 |
["shell/browser/api/atom_api_menu.cc", "shell/browser/api/atom_api_menu.h", "shell/browser/api/atom_api_menu_mac.h", "shell/browser/api/atom_api_menu_mac.mm", "shell/browser/api/atom_api_menu_views.cc", "shell/browser/api/atom_api_menu_views.h", "shell/browser/ui/cocoa/atom_menu_controller.h", "shell/browser/ui/cocoa/atom_menu_controller.mm", "spec-main/api-menu-spec.ts"]
|
crash in AtomMenuController.menuDidClose
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 --> 7.0.0, 6.1.2, 5.0.11
* **Operating System:**
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 --> macOS 10.15
* **Last Known Working Electron version:**
* <!-- (if applicable) e.g. 3.1.0 --> unknown
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
When using the Menu.popup API, Electron should not crash in AtomMenuController.menuDidClose.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
When using the Menu.popup API, Electron will sometimes crash in AtomMenuController.menuDidClose.
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->
Add this to main.js after creating mainWindow:
```javascript
mainWindow.webContents.on('context-menu', () => {
Menu.buildFromTemplate([{role: 'paste'}]).popup(mainWindow);
});
```
Here is a gist with that change: https://gist.github.com/jeremyspiegel/53afd0127ec3fc3e1cad5bbef0e4c390
Then keep right-clicking to invoke the menu repeatedly until you see a crash.
You can make the crash happen reliably on the first time invoking the menu by forcing garbage collection — add `setTimeout(() => global.gc(), 0);` after running `Menu.popup`, and run Electron with `--js-flags="--expose-gc"` on the command line.
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Additional Information
<!-- Add any other context about the problem here. -->
@MarshallOfSound added a speculative fix in https://github.com/electron/electron/pull/20111 but it doesn't fix the issue.
The problem isn't that `model_` is null, but rather it appears to be that the `MenuMac` API object is destroyed while `MenuMac::PopupOnUI` is running (inside the `[menu popUpMenuPositioningItem:item atLocation:position inView:view]` call).
I added the following to the top of `MenuMac::PopupOnUI` to try to make it so that the object could not be garbage collected while in that function:
```c++
v8::HandleScope handle_scope(isolate());
GetWrapper();
```
That seemed to make the problem go away.
|
https://github.com/electron/electron/issues/20737
|
https://github.com/electron/electron/pull/21169
|
ea23f18e94bde3c0f1d8f7cf2f3536ce410e3a80
|
50f2d2b5abfa1124dd49f41de8251952bc946307
| 2019-10-25T05:12:28Z |
c++
| 2019-11-20T11:17:39Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,729 |
["docs/api/process.md"]
|
Process getSystemVersion() - wrong return type (typescript)
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v7.0.0
* **Operating System:**
* macOS 10.13.6
* **Last Known Working Electron version:**
* v6.1.1
### Expected Behavior
_getSystemVersion()_ should return a string,
as suggested in _Examples_ part of the method's documentation.
```typescript
/**
* The version of the host operating system.
*
* Examples:
*
* * `macOS` -> `10.13.6`
* * `Windows` -> `10.0.17763`
* * `Linux` -> `4.15.0-45-generic`
*
* **Note:** It returns the actual operating system version instead of kernel
* version on macOS unlike `os.release()`.
*/
```
### Actual Behavior
return type is defined as ```('macOS' | 'Windows' | 'Linux')```
### To Reproduce
1. Install electron 7 ```npm i -d electron@latest```
2. Navigate to ```./node_modules/electron/electron.d.ts``` and see declaration of
_getSystemVersion()_ in line 13270
### Screenshots
N/A
### Additional Information
N/A
|
https://github.com/electron/electron/issues/20729
|
https://github.com/electron/electron/pull/20736
|
e8d85b6ded54d8642666917cc416eeaa240b61ac
|
cdff1bde22f99f99c2273c2dea3b7a4a3adea09d
| 2019-10-24T20:13:03Z |
c++
| 2019-10-27T16:40:41Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,705 |
["docs/api/ipc-main.md"]
|
Electron 7.0 typescript definitions on ipcMain.removeListener are bad
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0
* **Operating System:**
* Windows 10 (1903) x64
* **Last Known Working Electron version:**
* 6.0.0
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
The types in electron.d.ts for `IpcMain`.`removeListener` should match `on`/`once`, but while `on` is declared correctly
```ts
/**
* Listens to `channel`, when a new message arrives `listener` would be called with
* `listener(event, args...)`.
*/
on(channel: string, listener: (event: IpcMainEvent, ...args: any[]) => void): this;
```
`removeListener` is declared incorrectly
```ts
/**
* Removes the specified `listener` from the listener array for the specified
* `channel`.
*/
removeListener(channel: string, listener: () => void): this;
```
which causes compile errors when i try to remove my listeners.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
I can only get this to compile by adding the following in my file attempting to use `removeListener`
```ts
declare module 'electron' {
class IpcMain {
removeListener(event: string, listener: (...args: any[]) => void): this;
}
}
```
|
https://github.com/electron/electron/issues/20705
|
https://github.com/electron/electron/pull/20712
|
baaf0583804e8d5d232f150a219f35ba6b66c054
|
375e612ac5a7da51d1c77f837dd9f9cfd1945911
| 2019-10-23T18:15:55Z |
c++
| 2019-10-29T04:18:39Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,698 |
["lib/browser/api/browser-window.js", "lib/browser/guest-view-manager.js"]
|
(electron) 'isMenuBarAutoHide function' is deprecated and will be removed.
|
### Issue Details
* **Electron Version:** v7.0.0
* **Operating System:** Windows 10.0.18362.418
* **Last Known Working Electron version:** 6.x
### Expected Behavior
`npx electron .` runs without printing to console.
### Actual Behavior
`npx electron .` prints `(electron) 'isMenuBarAutoHide function' is deprecated and will be removed.` to console even though this API is not being called in user code.
### To Reproduce
```
git clone https://github.com/lutzroeder/netron.git
npm install
npx electron .
[ click "Open Model..." button ]
```
### Additional Information
Happens on Windows but not on macOS.
|
https://github.com/electron/electron/issues/20698
|
https://github.com/electron/electron/pull/20793
|
bd5a5b3ae61ef12ed7ebe7fddb2d59471d6a8b65
|
0c870775c4a825e7a79e334f7a304f47495e5d06
| 2019-10-23T05:28:42Z |
c++
| 2019-10-29T04:16:10Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,688 |
["shell/browser/api/atom_api_cookies.cc", "spec-main/api-net-spec.ts", "spec-main/api-session-spec.ts"]
|
session.cookies.set is broken in 7.0
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0
* **Operating System:**
* Windows 10 (1903)
* **Last Known Working Electron version:**
* 6.0.12
### Expected Behavior
session.defaultSession.cookies.set(cookie) should set a cookie that can be then retrieved using session.defaultSession.cookies.get(filter)
### Actual Behavior
session.defaultSession.cookies.set doesnt seem to be doing anything.
### To Reproduce
Gist:
This gist logs an empty array in 7.0.0, In 6.0.12, it logs the cookie object that was set:
https://gist.github.com/sgd2z/af6abf3cea4bddb1cd62a3e8265c359f
|
https://github.com/electron/electron/issues/20688
|
https://github.com/electron/electron/pull/21454
|
cbe1e3a1d091e210ccceae5c4c8b13877e1f3ab4
|
d5192853f9dbc8c41d98fb3bddb22e30dd34410d
| 2019-10-22T20:48:54Z |
c++
| 2019-12-11T07:44:49Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,685 |
["lib/browser/api/browser-window.js", "lib/browser/guest-view-manager.js"]
|
Electron uses of getZoomFactor with Webview
|
### Issue Details
It seems Electron itself uses some deprecated functions. It's using 'getZoomFactor' with Webview
instead of the new zoomFactor parameter.
* **Electron Version:**
7.0.0
* **Operating System:**
Mac
* **Last Known Working Electron version:**
6.x
### Expected Behavior
No warning
### To Reproduce
Create a webview in a Browser window
Trace: 'getZoomFactor function' is deprecated and will be removed. Please use 'zoomFactor property' instead.
at Object.log (electron/js2c/browser_init.js:6812:28)
at electron/js2c/browser_init.js:6791:23
at WebContents.getZoomFactor (electron/js2c/browser_init.js:6863:17)
at attachGuest (electron/js2c/browser_init.js:4899:26)
at electron/js2c/browser_init.js:5040:5
at electron/js2c/browser_init.js:5026:14
at callHandler (electron/js2c/browser_init.js:5652:30)
at EventEmitter.<anonymous> (electron/js2c/browser_init.js:5661:9)
at EventEmitter.emit (events.js:203:13)
at WebContents.<anonymous> (electron/js2c/browser_init.js:3761:23)
|
https://github.com/electron/electron/issues/20685
|
https://github.com/electron/electron/pull/20793
|
bd5a5b3ae61ef12ed7ebe7fddb2d59471d6a8b65
|
0c870775c4a825e7a79e334f7a304f47495e5d06
| 2019-10-22T20:25:52Z |
c++
| 2019-10-29T04:16:10Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,683 |
["shell/browser/native_window_views_win.cc"]
|
Resizable: false causes incorrect window sizes on differently scaled monitors
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0 beta 4+ (including 7.0 release), 6.0.6+
* **Operating System:**
* Windows 10 (1903)
* **Last Known Working Electron version:**
* 7.0.0 beta 3, 6.0.5
### Expected Behavior
Non resizable windows should have proper bounds on Monitors with display scales that are different from the primary.
### Actual Behavior
Non-resizable windows have bounds that are off by the ratio of the display scale of the secondary monitor to the primary monitor. e.g. if primary monitor is 200% scaled and secondary is 100%, the windows are 200/100 = twice the width and height.
### To Reproduce
Set your left monitor to primary with 200% scale
Set your right monitor to 100% scale
Then run this gist. Based on the resolution of your monitors, you might have to adjust the x position:
https://gist.github.com/sgd2z/7f92316b5fc920a59a55ee85c56011f4
### Screenshot
Here is a 200 x 200 window (the Hello World! from the reproducer) next to a correctly sized 400 x 400 window.
### Additional Information
We believe that this is caused by this PR:
https://github.com/electron/electron/pull/19928
based on the version boundaries of where the dimensions cease to be incorrect.
|
https://github.com/electron/electron/issues/20683
|
https://github.com/electron/electron/pull/21100
|
46c12308cd296ec05bcb2c7afbda7a67ae2a6ae1
|
fbc3bb872b0631e8655397e739b546287104470e
| 2019-10-22T16:42:06Z |
c++
| 2019-11-15T17:28:11Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,679 |
["lib/browser/guest-view-manager.js", "lib/common/web-view-methods.ts", "lib/renderer/web-view/web-view-impl.ts"]
|
The new audioMuted property should work on WebViews
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0
* 8.0.0
* 8.0.1
* 9.0.0-beta.1
* 9.0.0-beta.2
* **Operating System:**
* MacOS: 10.14.06
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
`webview.audioMuted = true` should mute the webview.
`webview.audioMuted = false` should unmute the webview.
### Actual Behavior
`webview.audioMuted = true` does nothing but triggers the following warning:
```log
(electron) 'setAudioMuted function' is deprecated and will be removed. Please use 'audioMuted property' instead.
```
### To Reproduce
Check out the following electron fiddle
https://gist.github.com/e80bbbc93d80be9889d8aceb4b8c20a2
|
https://github.com/electron/electron/issues/20679
|
https://github.com/electron/electron/pull/22485
|
8352c39c6580c0432f60bfc5e01b8fc2f2e1c572
|
efc11563e8562e87ed56e1e961434730334e9826
| 2019-10-22T10:46:15Z |
c++
| 2020-03-03T22:25:14Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,677 |
["lib/renderer/chrome-api.ts", "spec-main/extensions-spec.ts", "spec/fixtures/extensions/chrome-api/main.js"]
|
Devtools extensions no longer load in 7.0.0
|
### Issue Details
* **Electron Version:** 7.0.0
* **Operating System:** Ubuntu 18.04 x64 and macOS
* **Last Known Working Electron version:** 6.0.12
### Expected Behavior
In electron 6.x and previous version, devtools extensions would show up in the devtools.
### Actual Behavior
In Electron 7.x, devtools extensions are listed correctly when calling `BrowserWindow.getDevToolsExtensions`, but they don't show up in the devtools. Additionally, the following errors are sent to stout:
```
[10536:1022/102744.440460:ERROR:CONSOLE(2153)] "Uncaught Error: Connect to unknown extension [object Object]", source: electron/js2c/sandbox_bundle.js (2153)
[10536:1022/102744.712049:ERROR:CONSOLE(24)] "Empty response arrived for script 'devtools://devtools/remote/serve_file/@65dc90a9851d018b9423492f01b15f06cc34beba/product_registry_impl/product_registry_impl_module.js'", source: devtools://devtools/bundled/shell.js (24)
[10536:1022/102744.727679:ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: devtools://devtools/bundled/shell.js (109)
```
The last line is repeated many times. This seems similar to the errors seen in #13008, which seems to indicate the `devtools://devtools/remote/*` path actually resolves to an online endpoint. In that case that hash might refer to a not-yet-available M78 version of devtools? I wouldn't expect Electron to be dependent on that.
### To Reproduce
I'll try to get a Fiddle up later, but any app using devtools extensions (like ones using `electron-devtools-installer`) updating to 7.0.0 will not show devtools extensions anymore.
|
https://github.com/electron/electron/issues/20677
|
https://github.com/electron/electron/pull/20791
|
0ab9cc30d2cc9376a6e7105a7e0228d75155159b
|
3d56e13b38a743f7605e4326c2a9957e8fa7465c
| 2019-10-22T08:42:49Z |
c++
| 2019-10-30T05:46:52Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,631 |
["lib/browser/api/net.js", "shell/browser/api/atom_api_url_loader.cc", "spec-main/api-net-spec.ts"]
|
Electron 7, request using net module never contains cookies in response
|
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta.7
* **Operating System:**
* Windows 10
* **Last Known Working Electron version:**
* 6
### Expected Behavior
Cookies are received
### Actual Behavior
response.headers["set-cookie"] never contains cookies
### To Reproduce
Do a request using the net module as described here: https://electronjs.org/docs/api/net
to any site that will return cookies.
|
https://github.com/electron/electron/issues/20631
|
https://github.com/electron/electron/pull/21552
|
2d0bf81bd430acf13823eec015054a730940d46d
|
ceacadb4f4444b39cb00255263a509e3331de637
| 2019-10-18T10:07:57Z |
c++
| 2020-01-14T17:36:08Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,606 |
["docs/api/shell.md", "shell/browser/ui/inspectable_web_contents_impl.cc", "shell/common/api/atom_api_shell.cc", "shell/common/platform_util.h", "shell/common/platform_util_linux.cc", "shell/common/platform_util_mac.mm", "shell/common/platform_util_win.cc", "spec/ts-smoke/electron/main.ts"]
|
shell.openItem returns always true on Linux
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
```js
let ret = shell.openItem('file:///noexistent');
console.log(ret);
```
`ret` is always `true` on Linux even if opening fails, e.g.
```sh
xdg-open 'file:///noexistent'
echo $?
```
Shows nonzero error code.
* **Electron Version:**
* v6.0.11
* **Operating System:**
*Linux / Ubuntu 16.04 x64
### Expected Behavior
`ret` should be `false`, if `xdg-open` returns non-zero code.
Optional: It would be very nice if the `xdg-open` error (catch stderr) would be displayed in `dialog.showErrorBox` if it returns non-zero code. Just take care that `xdg-open` may write some warnings to stderr even if it returns 0.
|
https://github.com/electron/electron/issues/20606
|
https://github.com/electron/electron/pull/20682
|
fd70ac117394bee04296295462c4edeb15f2b314
|
d3622f9c37e8cd94e47206bb6211346011d5f76b
| 2019-10-16T15:10:07Z |
c++
| 2019-11-08T07:08:43Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,599 |
["docs/api/system-preferences.md", "shell/browser/api/atom_api_system_preferences.h", "shell/browser/api/atom_api_system_preferences_mac.mm", "shell/browser/api/atom_api_system_preferences_win.cc", "spec-main/api-system-preferences-spec.ts"]
|
systemPreferences.getColors() throws exceptions with some macOS colors
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 -->
v7.0.0-beta.6
* **Operating System:**
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 -->
macOS 10.14.6
* **Last Known Working Electron version:**
* <!-- (if applicable) e.g. 3.1.0 -->
the bug exists in all recent betas
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
a color value as a string
no exception thrown
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
exception thrown
```
"Error: Unknown color: disabled-control-text
at Function.updateAppearanceTheme (/Users/iac/Desktop/gluon/dist/App.js:138:54)
at App.createWindow (/Users/iac/Desktop/gluon/dist/App.js:9:13)
at App.emit (events.js:208:15)"
```
### To Reproduce
```
systemPreferences.getColor('disabled-control-text');
systemPreferences.getColor('scrubber-textured-background');
systemPreferences.getColor('selected-menu-item');
```
For reference, here are the macOS headers for these colors and their availability in the macOS 10.14 SDK
```
@property (class, strong, readonly) NSColor *disabledControlTextColor; // Text on disabled controls
@property (class, strong, readonly) NSColor *scrubberTexturedBackgroundColor NS_AVAILABLE_MAC(10_12_2); // Patterned background color for use in NSScrubber
@property (class, strong, readonly) NSColor *selectedMenuItemColor NS_DEPRECATED_MAC(10_0, API_TO_BE_DEPRECATED, "Use NSVisualEffectMaterialSelection");
```
All three are available in macOS 10.14 (one is deprecated, but still available).
But even if they weren't, the Electron docs don't specify limitations on the macOS version for this function. Shouldn't I expect *some* value rather than throwing an exception even when colors are not available on the user's system.
Or perhaps the documentation should reflect that in some cases the function will throw an exception -- and what those cases are.
A fiddle for such basic stuff seems overkill, but it also took me about 1 minute -- so why not. 😃
https://gist.github.com/yourhead/1db43ba064651648c673d686775b7afc
|
https://github.com/electron/electron/issues/20599
|
https://github.com/electron/electron/pull/20611
|
9a5cd4c8d2061e4b6dad4ba6af0c3a9cf79bc369
|
aa26e8b946260fc04cb696a5e546a123cf2bf620
| 2019-10-16T05:49:34Z |
c++
| 2019-10-21T21:31:03Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,557 |
["patches/chromium/.patches", "patches/chromium/worker_feat_add_hook_to_notify_script_ready.patch", "shell/browser/electron_browser_client.cc", "shell/browser/electron_browser_client.h", "shell/renderer/electron_renderer_client.cc", "shell/renderer/electron_renderer_client.h", "shell/renderer/web_worker_observer.cc", "shell/renderer/web_worker_observer.h", "spec-main/chromium-spec.ts"]
|
SharedWorker broken in 7.0 beta
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [X ] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [X ] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [X ] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
This is a bug report specifically for the 7.0 beta.
* **Electron Version:**
* 7.0.0-beta.6
* **Operating System:**
* Ubuntu 18.04 x64, Windows 10
* **Last Known Working Electron version:**
* 6.0.12
### Expected Behavior
SharedWorker should be functional and *shared* when using
a custom protocol to provide a proper origin.
### Actual Behavior
SharedWorker does not execute when loaded from custom protocol.
It does execute when page is loaded with the `file://` protocol, but this
defeats the purpose, since it is not shared between contexts.
Also noticed while diagnosing the issue:
Creating a SharedWorker with node integration enabled using a Data URL crashes
the renderer. I verified that this works in Electron 6, figured the cause might be related.
### To Reproduce
Install and run the following repo:
https://github.com/krisdages/electron-7-shared-worker-broken
$ git clone https://github.com/krisdages/electron-7-shared-worker-broken
$ npm install
$ npm start
Sorry, had it implemented before seeing the "electron fiddle" option. May try that next time.
Thanks for looking into this :)
|
https://github.com/electron/electron/issues/20557
|
https://github.com/electron/electron/pull/20625
|
4829b0f816d760eac6b8369f60912aaa42744a27
|
76e3ee6fe673ef70a4c5a8874ba77977c70f0c82
| 2019-10-13T23:53:15Z |
c++
| 2020-07-28T01:48:37Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,527 |
["shell/browser/native_window_views_win.cc"]
|
BrowserWindow: minHeight/minWidth broken on mixed DPI monitors on Windows in Electron 6.0.6
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.6, 6.0.12
* **Operating System:**
* Microsoft Windows [Version 10.0.18362.418]
* **Last Known Working Electron version:**
* 6.0.5
### Expected Behavior
minHeight/minWidth is the same value on all monitors
### Actual Behavior
minHeight/minWidth are much larger in size on lower DPI monitors
### To Reproduce
Sample app: https://github.com/ToadKing/dpi-bug
To reproduce, you must have multiple monitors on Windows with different DPI levels. The primary monitor on your desktop should be a high DPI one, while a secondary monitor should be lower DPI.
### Screenshots
High DPI primary monitor:
Lower DPI secondary monitor (stretches off the monitor):
### Additional Information
The behavior works in 6.0.5, but is broken in 6.0.6. Might be #19928/#20001 or the Chromium upgrade?
|
https://github.com/electron/electron/issues/20527
|
https://github.com/electron/electron/pull/21100
|
46c12308cd296ec05bcb2c7afbda7a67ae2a6ae1
|
fbc3bb872b0631e8655397e739b546287104470e
| 2019-10-10T19:31:22Z |
c++
| 2019-11-15T17:28:11Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,517 |
["shell/browser/atom_browser_client.cc"]
|
Memory leak in process.registerSchemesAsPrivileged
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v7.0.0-beta.6
* **Operating System:**
* macOS Mojave 10.14.5
* **Last Known Working Electron version:**
* v6.0.12
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
The electron helper process should not eat up memory.
<img width="815" alt="Screenshot 2019-10-10 at 11 29 35" src="https://user-images.githubusercontent.com/1265681/66556996-7b98ca80-eb51-11e9-894f-7f6323deab7f.png">
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
An electron helper process eats up memory in a linear way
<img width="898" alt="Screenshot 2019-10-10 at 11 23 35" src="https://user-images.githubusercontent.com/1265681/66557157-b438a400-eb51-11e9-954a-56cc236c72c6.png">
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
#### Example Repositiory
Here is a minimal reproduction example: https://github.com/HaNdTriX/electron-memory-leak
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
```sh
$ git clone [email protected]:HaNdTriX/electron-memory-leak.git
$ cd electron-memory-leak
$ npm install
$ npm start
```
After starting the app please take a look at its memory usage.
#### Code
```js
const { session, app, protocol, BrowserWindow } = require('electron')
const { join } = require('path')
protocol.registerSchemesAsPrivileged([{
scheme: 'atom',
privileges: {
// The following setting
// is causing the memoryleak
standard: true
}
}])
app.on('ready', () => {
session.defaultSession.protocol.registerFileProtocol('atom', (request, callback) => {
callback({
path: join(__dirname, 'index.html')
})
})
mainWindow = new BrowserWindow({
width: 800,
height: 600
})
mainWindow.loadURL(`atom://foobar`)
})
```
### Screenshots
See above...
### Additional Information
I've tracked down the bug to `registerSchemesAsPrivileged` and its `standard` setting.
|
https://github.com/electron/electron/issues/20517
|
https://github.com/electron/electron/pull/20546
|
5bd7b6ad50581983d34780d887c32f21bbafcba5
|
5c2c30142c7540339433ee90df9f90a9c921f0bd
| 2019-10-10T09:40:07Z |
c++
| 2019-10-14T01:21:41Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,503 |
["BUILD.gn", "build/rules.gni", "script/zip_manifests/dist_zip.mac.x64.manifest", "script/zip_manifests/dist_zip.mac_mas.x64.manifest", "shell/browser/atom_browser_main_parts.cc", "shell/browser/atom_browser_main_parts.h", "shell/browser/atom_browser_main_parts_mac.mm", "shell/browser/resources/mac/Info.plist", "shell/browser/ui/cocoa/atom_menu_controller.mm", "shell/common/resources/mac/MainMenu.xib"]
|
Regression of recentDocuments file list on macOS
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.12
* **Operating System:**
* macOS 10.14.6
* **Last Known Working Electron version:**
* 5.0.11
### Expected Behavior
Using `app.addRecentDocument`, should add files to the `recentDocuments` menu.
### Actual Behavior
The files are missing from the `recentDocuments` menu (the files, however, show up correctly when right-clicking on the dock icon--assuming that `addRecentDocument` works fine).
* `recentDocuments` seems like it is still broken in 6.0.12. The menu items work (are now enabled) but the `recentDocuments` menu does not populate with files.
### To Reproduce
```sh
$ git clone [email protected]:bigtimebuddy/electron-recent-docs-bug.git -b master
$ npm install
$ npm start || electron .
```
### Screenshots
**v6.0.12**
**v5.0.11**
### Additional Information
Follow up to #20364 & #20398
cc @codebytere
|
https://github.com/electron/electron/issues/20503
|
https://github.com/electron/electron/pull/20615
|
138af75ff81efeba0b066bf57b9db9c682b002c0
|
9a5cd4c8d2061e4b6dad4ba6af0c3a9cf79bc369
| 2019-10-09T14:45:26Z |
c++
| 2019-10-21T21:11:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,443 |
["docs/api/touch-bar-button.md", "docs/api/touch-bar-label.md", "lib/browser/api/touch-bar.js", "shell/browser/ui/cocoa/atom_touch_bar.mm"]
|
Accessibility at touchbar
|
Greetings,
at the current electron version, I see no way to label controls for a screenreader correctly. I haven't access at the NSAccessibility protocol and the attrebutes for set e.g. a description.
This makes all electron-apps inaccessible for voiceover on the touchbar. This course that the buttons aren't labeled and the visual impered user don't knows, what this button does. The only way to show a text for the voiceover user, is to set the label property. But this label is also print out on the control. In many situations, the developer only wants to use icons. Well, way not to add a binding to the nsaccessibility protocol? Or to the nsaccessibility.ateributes?
see [here](https://developer.apple.com/documentation/appkit/nsaccessibilityattributename?language=objc)
Hopeful you can do this and give the developers the tools to improve the accessibility of apps. Electron is used in many apps, there are could useful for blind users for example vscode or slack.
If you need help or more informations, I will try to help you.
all the best,
Christopher
|
https://github.com/electron/electron/issues/20443
|
https://github.com/electron/electron/pull/20454
|
8da9a3c4166e8a764cd4d86cbbe77afb3b86b488
|
c16a186de045a644c9c59628fa9b6442650334bc
| 2019-10-06T01:16:26Z |
c++
| 2019-10-08T15:13:57Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,435 |
["lib/browser/api/web-contents.js"]
|
Please support fitToPageEnabled option in webContents.printToPDF()
|
### Problem Description
Page content alway overflow, I need `fitToPage` to print the page correctly like in chrome.
### Proposed Solution
```javascript
WebContents.prototype.printToPDF = function (options) {
const printingSetting = Object.assign({}, defaultPrintingSetting)
...
if (options. fitToPageEnabled) {
printingSetting. fitToPageEnabled = options. fitToPageEnabled
}
...
```
|
https://github.com/electron/electron/issues/20435
|
https://github.com/electron/electron/pull/20436
|
19223952a86e7e25bdf1413e1efed5428c9ac2f1
|
825e67140e9e1a2318883e6c3887fe8ffe427fc7
| 2019-10-05T06:21:47Z |
c++
| 2019-10-18T00:40:19Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,392 |
["shell/browser/api/atom_api_cookies.cc", "shell/browser/api/atom_api_cookies.h", "spec-main/api-session-spec.ts"]
|
Filter cookies by domain is not working in 7.0.0
|
### Issue Details
* **Electron Version:**
* 7.0.0-beta.5
* **Operating System:**
* Windows
* **Last Known Working Electron version:**
* 6
### Expected Behavior
```js
const filter = {
domain: 'facebook.com'
}
const cookies = await webContents.session.cookies.get(filter) // will resolve with actual cookies
```
### Actual Behavior
```js
const filter = {
domain: 'facebook.com',
// url: 'https://facebook.com' - NOTE: filtering by url is working
}
const cookies = await webContents.session.cookies.get(filter) // is returning empty array
```
### To Reproduce
```js
const filter = {
domain: 'facebook.com'
}
const cookies = await webContents.session.cookies.get(filter)
```
Filter by `domain` is returning empty array, but if I try to filter using `url` is returning the actual cookies.
Tested on all `7` beta versions.
On `6` filtering by domain was worked.
|
https://github.com/electron/electron/issues/20392
|
https://github.com/electron/electron/pull/20471
|
ebd55c1147cd4c6bdd81810f989b39906e0ec2f9
|
5e11be689851d9bb1e658832680c57b49e3e8cf8
| 2019-10-01T10:59:21Z |
c++
| 2019-10-09T06:57:40Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,367 |
["lib/browser/api/web-contents.js", "spec-main/api-web-contents-spec.ts"]
|
Calling win.webContents.printToPDF multiple times
|
Calling win.webContents.printToPDF causes a crash the second time I do it.
The code is simply:
1)I have some html, i call ipc.Main.on, this has a callback function, inside I have a win.webContents.printToPDF and a callback function for it. If I call it the first time everything goes smooth, then if I change dinamically my HTML page with javascript and try to call the ipc.Main.on again the win.webContents.printToPDF gives me an error and crashes my application:
npm ERR! code ELIFECYCLE
npm ERR! errno 3221225477
npm ERR! [email protected] start: `electron .`
npm ERR! Exit status 3221225477
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\(MY NAME)\AppData\Roaming\npm-cache\_logs\2019-09-28T23_17_42_726Z-debug.log
|
https://github.com/electron/electron/issues/20367
|
https://github.com/electron/electron/pull/20769
|
b6246dcf122e584c672566877cb60d33dbc4705e
|
bd5a5b3ae61ef12ed7ebe7fddb2d59471d6a8b65
| 2019-09-28T23:18:36Z |
c++
| 2019-10-29T02:36:29Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,364 |
["shell/browser/ui/cocoa/atom_menu_controller.mm"]
|
Regression of recentDocuments Menu role on macOS
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
Defining a menu item like this no longer works in v6 where prior versions worked correctly. In v6, the menu item shows up in the menu disabled and does not have a submenu.
```js
{
label: 'Open Recent',
role: 'recentDocuments',
submenu: [
{ role: 'clearRecentDocuments' }
]
}
```
* **Electron Version:**
* 6.0.10
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* 5.0.11
### Expected Behavior
`Open Recent` menu item should be enabled and contain a submenu that is expandable.
### Actual Behavior
`Open Recent` menu item is disabled without a submenu.
### To Reproduce
Example, see `main.js` for the menu setup.
```sh
$ git clone [email protected]:bigtimebuddy/electron-recent-docs-bug.git -b master
$ npm install
$ npm start || electron .
```
### Screenshots
v6.x
v5.x
|
https://github.com/electron/electron/issues/20364
|
https://github.com/electron/electron/pull/20398
|
2470ef2e911fa4984ad2a5067d6a810a59a051f4
|
e543fe702cd1ab9db41eb100473495eb5f87de7b
| 2019-09-28T00:25:55Z |
c++
| 2019-10-03T05:25:14Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,346 |
["patches/angle/.patches", "patches/angle/gles2_use_constant_initialization_for_g_mutex.patch", "patches/config.json", "patches/perfetto/.patches", "patches/perfetto/metatrace_remove_memset_and_trivial_ctor_assumption.patch", "patches/quiche/.patches", "patches/quiche/include_ostream_in_quic_ip_address_h.patch", "patches/v8/.patches", "patches/v8/include_string_in_v8_h.patch"]
|
Building with Visual Studio 2019 fails (angle dependency)
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v8.0.0-nightly.20190924
* **Operating System:**
* Windows 10 (1803)
### Expected Behavior
Successful build of Electron on Visual Studio 2019.
### Actual Behavior
Fails with :
```
CXX obj/third_party/angle/libGLESv2/global_state.obj
FAILED: obj/third_party/angle/libGLESv2/global_state.obj
...
../../third_party/angle/src/libGLESv2/global_state.cpp(39,1): error: static_assert failed due to requirement 'std::is_trivially_constructible<std::atomic<std::mutex *>>::value' "global mutex is not trivially constructible"
static_assert(std::is_trivially_constructible<decltype(g_Mutex)>::value,
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
```
### To Reproduce
Follow the build instructions from: https://electronjs.org/docs/development/build-instructions-windows to build with Visual Studio Community Edition 2019. Fails for both the Debug and Release builds.
### Additional Information
Upstream bug report in angle: https://bugs.chromium.org/p/angleproject/issues/detail?id=3936
This doesn't affect upstream Chromium since it doesn't use MS STL (`use_custom_libcxx` = `true` for Chromium).
Reported the issue in order to track it.
|
https://github.com/electron/electron/issues/20346
|
https://github.com/electron/electron/pull/20465
|
94ec4ecabe23fa5967adef8470bcdd9e83df8395
|
de3c1fae7f96d0cb0c8871d9df421da7d385a085
| 2019-09-25T20:00:59Z |
c++
| 2019-10-08T19:49:38Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,267 |
["electron_strings.grdp"]
|
DesktopCapturerSource API document says `Entire Screen` but code run to `Entire screen`
|
version 6.0.9. The character `s` is in wrong case.
|
https://github.com/electron/electron/issues/20267
|
https://github.com/electron/electron/pull/20276
|
26014d19e10bbfa2f351599e60216229c4c0932b
|
ae6f08d56e9f36e80ff23740dab0c1c0793fbe05
| 2019-09-18T06:33:36Z |
c++
| 2019-09-20T14:16:47Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,256 |
["lib/sandboxed_renderer/init.js"]
|
process.on('document-start', ...) not emitted in sandbox mode
|
When attempting to listen to `'document-start'` with `process.on('document-start', () => { ... })`, I can see output when I have sandbox mode off, even if I have contextIsolation enabled and nodeIntegration disabled, but as soon as sandbox is enabled this doesn't work.
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta4
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* Couldn't find one where it worked
### Expected Behavior
Code in the event handler should run after the document exists
### Actual Behavior
The callback is never called
### To Reproduce
Run `process.on('document-start', () => console.log("Test"))` in the preload script in a window with sandbox mode on
https://gist.github.com/samiskin/01ea5d1bb5b72bd9247384a8a75ad784
|
https://github.com/electron/electron/issues/20256
|
https://github.com/electron/electron/pull/20987
|
5b7382765c3fedc8c1b1d5354a1a4ae2e79dcb0c
|
d91cc257f9f309ac974a766b41d2af231b58dc0b
| 2019-09-17T16:00:17Z |
c++
| 2019-11-06T01:53:03Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,248 |
["shell/browser/api/electron_api_protocol.cc", "shell/browser/electron_browser_client.cc", "spec-main/api-protocol-spec.ts", "spec-main/index.js"]
|
Cannot use service worker in html document served from custom protocol: The document is in an invalid state.
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta.4
* **Operating System:**
* macOS 10.14.6
* **Last Known Working Electron version:**
* NA
### Expected Behavior
Serve up a simple html page inside an iframe using a custom protocol (`test-scheme` in this example). The html page should be able to register a service worker to handle requests
Here's the example main process code:
```js
protocol.registerSchemesAsPrivileged([
{ scheme: 'test-scheme', privileges: { allowServiceWorkers: true, standard: true, secure: true } }
]);
```
```js
protocol.registerStringProtocol('test-scheme, (request, cb) => {
cb({
mimeType: 'text/html',
charset: 'utf-8',
data: `<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Heey World!</title>
</head>
<body>
Hello iframe!
<script>
window.navigator.serviceWorker.register('service-worker.js', {scope: './'}).then(function(registration) {
console.log('All good')
})
</script>
</body>
</html>`
})
});
```
### Actual Behavior
The service worker cannot be registered. In the dev tools console, I see the error:
```
DOMException: Failed to register a ServiceWorker: The document is in an invalid state.
```
### To Reproduce
Use the electron fiddle: https://gist.github.com/98ead2337cf17febffa64f731a8cc3e8
Look at the devtools output to see the errors
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
### Additional Information
<!-- Add any other context about the problem here. -->
/cc @deepak1556 - This is blocks migrating VS Code to use normal iframes for its webviews
|
https://github.com/electron/electron/issues/20248
|
https://github.com/electron/electron/pull/28326
|
7c3646308507633532a200addfa1e54d0691d03c
|
1e9e2f8cf69e1ec739b3f8e60658896042f65e2e
| 2019-09-16T23:32:13Z |
c++
| 2021-03-23T15:16:53Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,238 |
["patches/boringssl/.patches", "patches/boringssl/expose_blowfish_ciphers.patch", "patches/chromium/boringssl_build_gn.patch", "spec/node-spec.js"]
|
Add support for bf-cbc cipher
|
As per #16195, it has been suggested to ask for missing cipher algo when needed and open an issue.
Please add support for it, I need to for some third party buffer decryption.
|
https://github.com/electron/electron/issues/20238
|
https://github.com/electron/electron/pull/32356
|
de436f040fa6125bafbbabc459e88f97cdbc97c9
|
0a7bc4f5d147f0aafe5a8ada0054485bc2a45514
| 2019-09-15T20:45:03Z |
c++
| 2022-01-12T18:44:28Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,233 |
["shell/common/crash_reporter/crash_reporter_win.cc", "spec/api-crash-reporter-spec.js", "spec/fixtures/crash-app/main.js", "spec/fixtures/crash-app/package.json"]
|
High CPU on Windows upon crash when not starting crash reporter
|
This is a regression from 4.x as far as I can tell.
Steps:
* `git clone https://github.com/bpasero/electron-crashreporter`
* `yarn`
* open `constants.js` and configure:
* `enableCrashReporter: false`
* `crashMain` (or renderer, or child process): `true`
* `tmpDir`: some location that exists
* `yarn start`
=> 🐛 the process that crashes goes to 100% CPU and does not terminate. My feeling is that this is a regression from adopting crashpad for Windows.
This is a blocker for shipping E6 for VSCode.
//cc @deepak1556
|
https://github.com/electron/electron/issues/20233
|
https://github.com/electron/electron/pull/20388
|
969b4d1dd3588d9fa315f64e7f4255d3fb0b0fff
|
ef690c035dc1fa783f12da1cbecfaa3cc46c48db
| 2019-09-14T07:43:13Z |
c++
| 2019-10-01T17:20:21Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,185 |
["script/release/uploaders/upload-node-headers.py"]
|
6.0.8 node.lib linking issues
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.8
* **Operating System:**
* Windows Server 2016 and 2019
* **Last Known Working Electron version:**
* 6.0.7
With the 6.0.8 binaries, native module builds are now failing with:
```
node.lib(node.exe) : fatal error LNK1223: invalid or corrupt file: file contains invalid .pdata contributions
```
|
https://github.com/electron/electron/issues/20185
|
https://github.com/electron/electron/pull/20192
|
fd31a99ef04af7900f3f6b65bc354a92c25f1237
|
5ccc043d869738ea9be94768b5d19efb02d8648d
| 2019-09-10T14:36:05Z |
c++
| 2019-09-10T21:14:58Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,182 |
["shell/browser/net/atom_url_loader_factory.cc", "spec-main/api-protocol-spec.ts"]
|
Content type charset headers break registerStreamProtocol api
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta.4
* **Operating System:**
* MacOS 10.14.5
* **Last Known Working Electron version:**
* 7.0.0-beta.3
### Tltr
| Header | Result |
|------------------------------------------|--------------|
| `content-type: text/html; charset=UTF-8` | doesn't work |
| `content-type: text/html` | works |
### Expected Behavior
`protocol.registerStreamProtocol` should work with content-type charset headers
#### `BrowserWindow` Result Screenshot
<img width="113" alt="Bildschirmfoto 2019-09-10 um 11 47 20" src="https://user-images.githubusercontent.com/1265681/64603483-c8597c00-d3c0-11e9-9410-517c9f3e79bf.png">
### Actual Behavior
`protocol.registerStreamProtocol` doesn't work with content-type charset headers
#### `BrowserWindow` Result Screenshot
<img width="218" alt="Bildschirmfoto 2019-09-10 um 11 47 30" src="https://user-images.githubusercontent.com/1265681/64603559-e58e4a80-d3c0-11e9-9044-e487a3ebd88c.png">
### To Reproduce
```sh
$ git clone [email protected]:HaNdTriX/electron-content-type-bug.git
$ npm install
$ npm start
```
or use the following code
```js
const { app, protocol, BrowserWindow } = require('electron')
const { PassThrough } = require('stream')
function createStream (text) {
const rv = new PassThrough() // PassThrough is also a Readable stream
rv.push(text)
rv.push(null)
return rv
}
app.on('ready', () => {
protocol.registerStreamProtocol('atom', (request, callback) => {
callback({
statusCode: 200,
headers: {
'content-type': 'text/html; charset=UTF-8'
// 'content-type': 'text/html' -> is working
},
data: createStream('<h5>Response</h5>')
})
})
let win = new BrowserWindow({ width: 800, height: 600 })
win.loadURL('atom://app')
})
```
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
|
https://github.com/electron/electron/issues/20182
|
https://github.com/electron/electron/pull/20538
|
67642312f427ce0b87f12a84557b34b08946d2b6
|
1b2c6a33b32a5753e6ca9fe352beb4e3e4625bcb
| 2019-09-10T09:51:40Z |
c++
| 2019-10-11T18:54:50Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,181 |
["shell/browser/atom_browser_main_parts.cc", "shell/browser/atom_browser_main_parts.h", "shell/browser/atom_browser_main_parts_mac.mm", "shell/browser/mac/atom_application.h", "shell/browser/mac/atom_application.mm"]
|
The open-url Event doesn't fire anymore
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v7.0.0-beta.4
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* v6.0.8
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
The [`open-url`-Event](https://electronjs.org/docs/api/app#event-open-url-macos) should fire and the application instance gains focus.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
The [`open-url`-Event](https://electronjs.org/docs/api/app#event-open-url-macos) doesn't fire, but the application instance gains focus.
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->
Implement the following code:
```js
const { app } = require('electron')
app.once('ready', () => {
app.setAsDefaultProtocolClient('foo')
app.on('open-url', (event, url) => {
console.log('this should be logged')
})
})
```
From your terminal run:
```bash
$ open foo://some/url
```
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
|
https://github.com/electron/electron/issues/20181
|
https://github.com/electron/electron/pull/20518
|
ec2c1db0e439954e7764853f6b9bd0d5a3518cc2
|
812de5d3bff295f67cae8a4cae0a947d50247406
| 2019-09-10T09:24:06Z |
c++
| 2019-10-10T15:54:03Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,086 |
["lib/browser/remote/objects-registry.ts", "lib/browser/remote/server.ts", "lib/renderer/api/remote.js", "spec-main/api-remote-spec.ts", "spec-main/fixtures/api/send-on-exit.html"]
|
Closing child window hangs main window
|
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
I have enabled nativeWindowOpen and nodeIntegrationInSubFrames for main window, and I have a preload script which required a remote from electron. Which this configuration I open a child window and then I close it. The main window render process hangs for ever so I have to restart whole app. Here is and example app https://github.com/zarubond/electron-quick-start/tree/child_hang
* **Electron Version:**
6.0.7, 7.0.0-beta3
* **Operating System:**
Windows, Linux, MacOS
* **Last Known Working Electron version:**
5.0.10
### Expected Behavior
Closing child window should not hang main window for ever
### Actual Behavior
Main window hangs after closing child window.
### To Reproduce
Open child window and then close it
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/20086
|
https://github.com/electron/electron/pull/20632
|
2abea22b4bffa1626a521711bacec7cd51425818
|
ba8f80267c2874307357cf0bf99457a29b9a9d19
| 2019-09-03T13:38:48Z |
c++
| 2019-10-23T04:44:21Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 20,027 |
["patches/chromium/.patches", "patches/chromium/mas_disable_remote_layer.patch", "shell/app/electron_main_delegate.cc"]
|
Mac App Store Private API Rejection: Electron 5.0.10
|
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
### Issue Details
* **Electron Version:** 5.0.10
### Rejection Email
ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework: CAContext, CALayerHost, NSAccessibilityRemoteUIElement, NSNextStepFrame, NSThemeFrame, NSURLFileTypeMappings . If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
|
https://github.com/electron/electron/issues/20027
|
https://github.com/electron/electron/pull/20965
|
1502ecf9f71624cb1b2a63c5d169f01558469b7e
|
41931aa5fa83e4b5cbb935e10ce67a5caea37ce0
| 2019-08-29T15:46:29Z |
c++
| 2020-02-24T03:08:57Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,984 |
["shell/browser/atom_browser_main_parts.cc"]
|
In 7-0-x and master, Electron on Linux gives a gtk_disable_setlocale() warning on startup
|
The warning is
> (electron:23955): Gtk-WARNING **: 10:41:01.876: gtk_disable_setlocale() must be called before gtk_init()
Looks like this is caused by gtk_init() being accidentally called twice.
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7-0-x, v8.0.0-nightly.20190827
* **Operating System:**
* Linux
* **Last Known Working Electron version:**
* 6-0-x
|
https://github.com/electron/electron/issues/19984
|
https://github.com/electron/electron/pull/19986
|
538c4763cf33db72c4842ce3a27d7790e4558de8
|
217ed9aabc1186fa5fdd0ddd7c7d85710bf34a5c
| 2019-08-27T15:47:49Z |
c++
| 2019-08-28T17:36:03Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,911 |
["shell/app/atom_content_client.cc"]
|
command-line scheme switches' values spill over into other switches
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v8.0.0-nightly.20190821
* **Operating System:**
* Ubuntu 19.04 x64
* **Last Known Working Electron version:**
* Unknown. Broken in `4-1-x` upwards.
### Expected Behavior
Passing additional schemes on the command line, e.g. `--standard-schemes=foo,bar,mum`, should not affect other schemes, e.g. cors enabled schemes or secure schemes.
### Actual Behavior
The schemes from earlier checks bleed into all the following switches checked.
This happens due to the "splitted" variable in `shell/app/atom_content_client.cc`'s `AtomContentClient::AddAdditionalSchemes()` being reused for each switch without being cleared first.
### To Reproduce
On the command line, add schemes for one of the argument switches handled in `AtomContentClient::AddAdditionalSchemes()`.
|
https://github.com/electron/electron/issues/19911
|
https://github.com/electron/electron/pull/19912
|
181f663cf1da6eb073a0073312c0cfbcad37bb94
|
080fdb3817318afbf627feda919a6753997a6d74
| 2019-08-23T15:58:49Z |
c++
| 2019-08-26T00:40:44Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,908 |
["lib/browser/desktop-capturer.ts", "shell/browser/api/atom_api_desktop_capturer.cc"]
|
desktopCapturer.getSources memory leaks
|
### Issue Details
* **Electron Version:**
* v4.0.0
* **Operating System:**
* Ubuntu 18.04.3 LTS
* **Last Known Working Electron version:**
* Unknown
### Expected Behavior
The Resident set size of the Main process when using desktopCapturer.getSources not growing.
### Actual Behavior
Memory leak in the Main process (rss memory growing) when using the desktopCapturer.getSources method in the Rendering process.
### To Reproduce
> main.js
```javascript
const {
app,
BrowserWindow
} = require('electron');
const url = require('url');
const path = require('path');
let win;
const logBytes = x => `${x[0]}=${x[1] / (1000.0 * 1000)}MB`;
const logMemory = () => {
console.log(
Object.entries(process.memoryUsage())
.map(logBytes)
.join(', ')
);
};
const createWindow = () => {
win = new BrowserWindow();
win.loadURL(url.format({
pathname: path.join(__dirname, 'index.html'),
protocol: 'file:',
slashes: true
}));
};
try {
app.on('ready', createWindow);
} catch (e) {
console.err(e);
}
logMemory();
setInterval(logMemory, 10000);
```
> index.html
```html
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Hello World!</title>
</head>
<body>
<h1>Hello World!</h1>
We are using Node.js <span id="node-version"></span>,
Chromium <span id="chrome-version"></span>,
and Electron <span id="electron-version"></span>.
<!-- You can also require other files to run in this process -->
<script src="./renderer.js"></script>
</body>
```
> renderer.js
```javascript
const electron = require('electron');
const desktopCapturer = electron.desktopCapturer;
const getSourcesLoop = () => {
console.log('getSources() call');
desktopCapturer.getSources({
types: ['screen', 'window']
}).then(sources => {
console.log('getSources() success', sources);
setTimeout(getSources, 5000);
});
};
getSourcesLoop();
```
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
|
https://github.com/electron/electron/issues/19908
|
https://github.com/electron/electron/pull/20156
|
42999f42f206f1acd0d0aa8be23fdc7fc0f8cf6f
|
d2a94e6b1374809fdcda9bbf41fa16dfd56848c8
| 2019-08-23T10:49:49Z |
c++
| 2019-09-17T16:48:31Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,875 |
["shell/browser/native_window_mac.h", "shell/browser/native_window_mac.mm"]
|
Clipped view with MacOS native tabs
|
### Issue Details
* **Electron Version:**
4.2.9 , 5.x , 6.x
* **Operating System:**
macOS 10.14.6
### To Reproduce
https://gist.github.com/deepak1556/5edd25929a0a3077a89328eaf60ec0f9
### Screenshots
### Additional Information
This is a regression from https://github.com/electron/electron/pull/19319
|
https://github.com/electron/electron/issues/19875
|
https://github.com/electron/electron/pull/19878
|
6667969887cbace3ff091e2ad0bc4c73da325a0f
|
ab0bf6d2380e16c37db73013d27943d8648b2ac2
| 2019-08-21T23:08:45Z |
c++
| 2019-08-22T21:16:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,858 |
["patches/chromium/.patches", "patches/chromium/chore_add_debounce_on_the_updatewebcontentsvisibility_method_to.patch", "patches/chromium/disable_compositor_recycling.patch", "spec-main/api-browser-window-spec.ts"]
|
White screen appears quickly when the app focus from background.
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v6.0.3
* **Operating System:**
* macOS 10.14.6
* **Last Known Working Electron version:**
* v1.8.3
### Expected Behavior
The same behavior as other APPs
### Actual Behavior
White screen appears quickly when the app focus from background, Ensure that the app is in the background for a while.
### To Reproduce
https://github.com/electron/electron-quick-start
Put the app in the background for a while and focus main window, the issue will be reproduced.
### Screenshots
Screen recording: https://s0.static.lunkr.cn/cab/publish/electron_bug_report.mov
### Additional Information
none
|
https://github.com/electron/electron/issues/19858
|
https://github.com/electron/electron/pull/19873
|
ab0bf6d2380e16c37db73013d27943d8648b2ac2
|
f7e3e1f97a204f8e734536b5a2380b7e57dab472
| 2019-08-21T04:47:32Z |
c++
| 2019-08-22T22:16:06Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,847 |
["shell/browser/api/electron_api_web_contents.cc", "spec/api-web-contents-spec.ts"]
|
[Bug]: loadURL after did-start-loading crashes electron
|
### Preflight Checklist
* [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 5.0.10 , 6 ,7
* **Operating System:**
* Windows 10
* **Last Known Working Electron version:** ?
### Expected Behavior
No crash
### Actual Behavior
In electron 5 it crashes with the following code: 2147483651
in electron 6 and 7 it just seems to hang but is basically dead
### To Reproduce
```
const { app, BrowserWindow, BrowserView } = require("electron");
const init = () => {
let browserWindow = new BrowserWindow({
show: true,
});
browserWindow.loadURL("https://www.google.com");
let browserWindow2 = new BrowserWindow({
show: true,
});
browserWindow2.webContents.once("did-start-loading", () => {
browserWindow2.loadURL("https://www.google.com");
});
browserWindow2.loadURL("https://www.test.com");
};
app.on("ready", () => {
init();
});
```
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/19847
|
https://github.com/electron/electron/pull/40143
|
563c370d51f302b6d4a7fee8b47e1cc3e1ca2fe3
|
86df4db6f10afbe5872f8ecbcbfe6191374fc1f7
| 2019-08-20T20:05:40Z |
c++
| 2023-10-10T10:46:04Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,842 |
["shell/browser/api/atom_api_notification.cc"]
|
Crash on exit
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 4.2.9
* 5.0.10
* 6.0.2
* 6.0.3
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* N/A
Hi,
I intercept the app shutdown using `before-quit` event handler and call `preventDefault` when I receive the event in the very first time. Then I do some clean up and call `app.quit()` once again to make sure that the normal termination happens.
The app terminates and a crash report dialog appears (excerpt below)
```
Process: Electron [13005]
Path: /Users/USER/*/Electron.app/Contents/MacOS/Electron
Identifier: com.github.Electron
Version: 5.0.10 (5.0.10)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Electron [13005]
User ID: 501
Date/Time: 2019-08-20 17:56:13.682 +0200
OS Version: Mac OS X 10.14.5 (18F203)
Report Version: 12
Bridge OS Version: 3.5 (16P5200)
Anonymous UUID: A6609847-C7B4-9C4A-35BF-39025881C86C
Sleep/Wake UUID: CC7BA0DC-7A56-49AC-AC04-7B847DDBA7B1
Time Awake Since Boot: 20000 seconds
Time Since Wake: 95 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [13005]
VM Regions Near 0:
-->
__TEXT 00000001077ec000-0000000107815000 [ 164K] r-x/rwx SM=COW /Users/USER/*/Electron.app/Contents/MacOS/Electron
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.github.Electron.framework 0x0000000109a43c8f 0x107821000 + 35794063
1 com.github.Electron.framework 0x0000000109a4220e 0x107821000 + 35787278
2 com.github.Electron.framework 0x0000000109a43d9f 0x107821000 + 35794335
3 com.github.Electron.framework 0x0000000109a436e0 0x107821000 + 35792608
4 com.github.Electron.framework 0x0000000109a05f07 0x107821000 + 35540743
5 com.github.Electron.framework 0x0000000109a05f9e 0x107821000 + 35540894
6 com.github.Electron.framework 0x000000010782379f AtomMain + 95
7 com.github.Electron 0x00000001077ed9b0 0x1077ec000 + 6576
8 libdyld.dylib 0x00007fff5c0553d5 start + 1
```
Symbolicated crash report:
[crash.txt](https://github.com/electron/electron/files/3525362/crash.txt)
Based on the crash report, the `Notification` destructor triggers the crash. So I've poked around creating Notifications in JS and somehow I've managed to crash the app when creating notifications from the `before-quit` handler.
I can't really explain why creating notifications from the `before-quit` does crash the app, because in the case of my own app, it does crash regardless that, i.e I can just create one notification at the start and the app will crash on exit anyway.
It's possible that the amount of allocated memory plays its role. Perhaps some of notifications are being evicted from memory sooner when more JS objects are being allocated. It's possible that it's a double-release issue.
Also, I think the fact that I retain the notifications in array affects the garbage collection somehow.
The crash itself is not 100% reproducible but it happens often enough. So if you run my branch a few times in a row, you should see the crash dialog.
You can observe the `ReportCrash` process in activity monitor (see the screenshot I've attached to the issue). If you see the `ReportCrash` spike in CPU usage, wait a little before it pops the crash report dialog. It takes some time to symbolicate the crash log if you have DSYMs installed.
I've also tried to `destroy()` notifications manually which caused the following output in console:
```
Electron(64844,0x10ce985c0) malloc: Incorrect checksum for freed object 0x7fc124259c00: probably modified after being freed.
Corrupt value: 0x701124226b4
Electron(64844,0x10ce985c0) malloc: *** set a breakpoint in malloc_error_break to debug
```
and such output too:
```
Electron(64867,0x105c925c0) malloc: *** error for object 0x7fc797ecd490: pointer being freed was not allocated
Electron(64867,0x105c925c0) malloc: *** set a breakpoint in malloc_error_break to debug
```
So I suppose something is over-releasing the memory...
### Expected Behavior
No crash
### Actual Behavior
Crash
### To Reproduce
1. Clone the repo and run the app
```sh
$ git clone https://github.com/pronebird/electron.git -b issue19842
$ npm install
$ npm start
```
2. Press "quit" button in the application window
3. See the crash report dialog appear (with a certain success rate)
### Screenshots
<img width="1632" alt="Screenshot 2019-08-22 at 14 44 38" src="https://user-images.githubusercontent.com/704044/63515912-314d8280-c4ec-11e9-9fcc-08a2c12864a7.png">
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/19842
|
https://github.com/electron/electron/pull/21709
|
bd923838c108c0ea693f3a158a5d1ca09cd317b3
|
f5e202a89871ff50a95e3113cf246e226257fac0
| 2019-08-20T15:57:03Z |
c++
| 2020-01-09T17:42:20Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,816 |
["shell/browser/native_window_views_win.cc"]
|
Electron 6 - restore after minimize has wrong window size
|
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* `6.0.2`
* **Operating System:**
* Windows 10 (1903)
* **Last Known Working Electron version:**
* `5.0.7`
### Expected Behavior
1. App is not maximized
2. click minimize
3. click on taskbar icon
4. **app restores to original size**
### Actual Behavior
1. App is not maximized
2. click minimize
3. click on taskbar icon
4. **screen flickers as the app returns from _minimum allowed window size_ to the original (not maximized) size.**
### To Reproduce
I logged the behavior:
```ts
win.on('minimize', (e) => {
console.log('minimizing');
const bounds: any = win.getBounds();
console.log(bounds);
});
win.on('restore', (e) => {
console.log('restoring');
const bounds: any = win.getBounds();
console.log(bounds);
});
```
Result:
```
minimizing
{ x: 100, y: 200, width: 1400, height: 800 }
restoring
{ x: 100, y: 200, width: 420, height: 250 }
```
The dimensions come from
```ts
win = new BrowserWindow({
...
minWidth: 420,
minHeight: 250,
frame: false // this line might be relevant for the current issue
```
I have the problem happening in my app, in `master` - tracking with https://github.com/whyboris/Video-Hub-App/issues/260
Can be reproduced by cloning the repository, running `npm install`, having _Angular CLI_ installed (`npm i -g @angular/cli`), and running the app `npm start`. Needless to say the error occurs in the built version of the app (`npm run electron:windows`).
_Note:_ the error does _not_ occur when the window is _maximized_, minimized, and restored.
Error might not occur on Mac -- can't be sure because the Mac has a stupid minimize/maximize animation 🤷♂
Thank you _Electron Team_ for your amazing work 🙇 my app would be impossible without you ❤️
### Possibly related tickets:
https://github.com/electron/electron/issues/19423
https://github.com/electron/electron/issues/13043
https://github.com/electron/electron/issues/16900
### Possible solution:
https://github.com/electron/electron/issues/19423#issuecomment-521621266
|
https://github.com/electron/electron/issues/19816
|
https://github.com/electron/electron/pull/19928
|
832c926712802913d7f48f84015d394d62281338
|
27ce6a9cd3445ce7c405fb3abebb472e7bc2bd0f
| 2019-08-18T22:49:54Z |
c++
| 2019-08-28T00:34:34Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,795 |
["shell/browser/web_dialog_helper.cc"]
|
Can't show file chooser dialog when clicking <input type="file"> after canceled the dialog.
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta.3
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* 6.0.2
### Expected Behavior
Show file chooser dialog when clicking input type="file" after canceled the dialog.
### Actual Behavior
Can't show file chooser dialog when clicking input type="file" after canceled the dialog.
### To Reproduce
1. Clone and Install source code.
```sh
$ git clone https://github.com/agata/electron-quick-start.git -b bug-for-file-chooser-after-canceled
$ npm install
$ npm start || electron .
```
2. Click <input type="file"> -> Show file chooser dialog.
3. Click cancel button of the dialog -> Close the dialog
4. Click <input type="file"> again -> Can't show file chooser dialog.
### Screenshots
### Additional Information
WebView has same problem.
|
https://github.com/electron/electron/issues/19795
|
https://github.com/electron/electron/pull/19897
|
c61020e9d3928eaa74b6d134778923efd7ebc4b5
|
698120daf07b3bdbd3a2c2ffcace39782131490f
| 2019-08-16T14:53:32Z |
c++
| 2019-08-23T21:18:30Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,779 |
["lib/browser/api/dialog.js"]
|
bug: open file dialog doesn't allow selecting files
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v8.0.0-nightly.20190814, master
* **Operating System:**
* macOS 10.14.6
* **Last Known Working Electron version:**
* v8.0.0-nightly.20190813
### Expected Behavior
Should be able to select files or folders.
### Actual Behavior
Selecting is disabled (greyed out).
### To Reproduce
```js
const { app, dialog } = require('electron')
app.on('ready', () => {
dialog.showOpenDialogSync({
title: 'Hello!',
properties: ['openFile'],
})
})
```
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
### Additional Information
|
https://github.com/electron/electron/issues/19779
|
https://github.com/electron/electron/pull/19781
|
2c002a334283a2b4e788fb7a5a6343bd412cbf54
|
6a76540cb6a9ec2b8e9c15af130b4e97981e6baa
| 2019-08-15T16:48:27Z |
c++
| 2019-08-16T15:55:01Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,772 |
["docs/api/dialog.md"]
|
showOpenDialogSync returns wrong type in Electron.d.ts
|
should be string[] , is void
|
https://github.com/electron/electron/issues/19772
|
https://github.com/electron/electron/pull/19778
|
6a76540cb6a9ec2b8e9c15af130b4e97981e6baa
|
56d10aeef7d5b20b84d87722008c977bba65a69b
| 2019-08-15T10:33:16Z |
c++
| 2019-08-16T16:24:17Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,755 |
["shell/browser/ui/file_dialog_gtk.cc"]
|
Keyboard shortcuts broken in GTK+ dialogs
|
Introduced in PR #19725 to address issue #19663
That change drops the underscores from the strings passed to the GTK dialog, which breaks the keyboard shortcuts for those dialog buttons.
See this similar [Chromium discussion](https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/select_file_dialog_impl_gtk.cc?type=cs&q=SelectFileDialogImplGTK::CreateFileOpenHelper&sq=package:chromium&g=0&l=40):
```c++
#if GTK_CHECK_VERSION(3, 90, 0)
// GTK stock items have been deprecated. The docs say to switch to using the
// strings "_Open", etc. However this breaks i18n. We could supply our own
// internationalized strings, but the "_" in these strings is significant: it's
// the keyboard shortcut to select these actions. TODO(thomasanderson): Provide
// internationalized strings when GTK provides support for it.
const char kCancelLabel[] = "_Cancel";
const char kOpenLabel[] = "_Open";
const char kSaveLabel[] = "_Save";
#else
G_GNUC_BEGIN_IGNORE_DEPRECATIONS
const char* const kCancelLabel = GTK_STOCK_CANCEL;
const char* const kOpenLabel = GTK_STOCK_OPEN;
const char* const kSaveLabel = GTK_STOCK_SAVE;
G_GNUC_END_IGNORE_DEPRECATIONS
#endif
```
tl;dr the underscores are important.
Also relevant to the previous PR, Chromium appears to not suffer from the same translation issues. I don't know why that is but it may be worth investigating. Chromium [uses](https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/select_file_dialog_impl_gtk.cc?type=cs&q=SelectFileDialogImplGTK::CreateFileOpenHelper&sq=package:chromium&g=0&l=327) those `kFooLabel`s from above this way:
```c++
GtkWidget* SelectFileDialogImplGTK::CreateFileOpenHelper(
const std::string& title,
const base::FilePath& default_path,
gfx::NativeWindow parent) {
GtkWidget* dialog = gtk_file_chooser_dialog_new(
title.c_str(), nullptr, GTK_FILE_CHOOSER_ACTION_OPEN, kCancelLabel,
GTK_RESPONSE_CANCEL, kOpenLabel, GTK_RESPONSE_ACCEPT, nullptr);
SetGtkTransientForAura(dialog, parent);
AddFilters(GTK_FILE_CHOOSER(dialog));
```
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
|
https://github.com/electron/electron/issues/19755
|
https://github.com/electron/electron/pull/19756
|
ca0cf5415e362bb2b75677017a8805f3c1945bab
|
12df0e8994818810ba970d8695db537be6cd8ead
| 2019-08-14T16:46:33Z |
c++
| 2019-08-15T17:31:07Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,751 |
["docs/api/session.md", "shell/browser/net/cert_verifier_client.cc", "shell/browser/net/cert_verifier_client.h", "shell/common/gin_converters/net_converter.cc"]
|
No root CA provided in the certificate chain (session.defaultSession.setCertificateVerifyProc)
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
`allElectronVersionsList.every(version => version <= 6.02)`
* **Operating System:**
macOS 10.14.4
* **Last Known Working Electron version:**
`null`
### Expected Behavior
A certificate chain _always_ contains a root CA in the last `issuerCert` property
### Actual Behavior
A certificate chain does _not always_ contain a root CA. Sometimes there is no last `issuerCert` property with the root CA.
### To Reproduce
```javascript
import { session } from "electron";
session.defaultSession.setCertificateVerifyProc((request, callback) => {
console.log(request)
})
// go to https://www.google.com
```
Output:
```json
{
"hostname": "www.google.com",
"certificate": {
"data": "-----BEGIN CERTIFICATE-----[...]-----END CERTIFICATE-----\n",
"issuer": {
"commonName": "Google Internet Authority G3",
"organizations": ["Google Trust Services"],
"organizationUnits": [],
"locality": "",
"state": "",
"country": "US"
},
"issuerName": "Google Internet Authority G3",
"subject": {
"commonName": "www.google.com",
"organizations": ["Google LLC"],
"organizationUnits": [],
"locality": "Mountain View",
"state": "California",
"country": "US"
},
"subjectName": "www.google.com",
"serialNumber": "4C0285FE64D38AE9CF0D9E7529683F13",
"validStart": 1564425802,
"validExpiry": 1571682180,
"fingerprint": "sha256/7eN7eGinc3BpdbZckdcZUqBYxGOmqbSnGnw3/tAKT7k=",
"issuerCert": {
"data": "-----BEGIN CERTIFICATE-----[...]-----END CERTIFICATE-----\n",
"issuer": {
"commonName": "GlobalSign",
"organizations": ["GlobalSign"],
"organizationUnits": ["GlobalSign Root CA - R2"],
"locality": "",
"state": "",
"country": ""
},
"issuerName": "GlobalSign",
"subject": {
"commonName": "Google Internet Authority G3",
"organizations": ["Google Trust Services"],
"organizationUnits": [],
"locality": "",
"state": "",
"country": "US"
},
"subjectName": "Google Internet Authority G3",
"serialNumber": "01E3A9301CFC7206383F9A531D",
"validStart": 1497484842,
"validExpiry": 1639526442,
"fingerprint": "sha256/vgzNVNTOzaG9Xl2ezIWgTCwfk6UiDXf96I/prQgfZBs="
}
},
"verificationResult": "net::OK",
"errorCode": 0
}
```
**There are only the leaf and intermediate certificates in the _request_ object above**
### Additional Information
But for some domains root certificate exists.
e.g. for `www.example.org`:
```json
{
"hostname": "www.example.org",
"certificate": {
"data": "-----BEGIN CERTIFICATE-----[...]-----END CERTIFICATE-----\n",
"issuer": {
"commonName": "DigiCert SHA2 Secure Server CA",
"organizations": ["DigiCert Inc"],
"organizationUnits": [],
"locality": "",
"state": "",
"country": "US"
},
"issuerName": "DigiCert SHA2 Secure Server CA",
"subject": {
"commonName": "www.example.org",
"organizations": ["Internet Corporation for Assigned Names and Numbers"],
"organizationUnits": ["Technology"],
"locality": "Los Angeles",
"state": "California",
"country": "US"
},
"subjectName": "www.example.org",
"serialNumber": "0FD078DD48F1A2BD4D0F2BA96B6038FE",
"validStart": 1543363200,
"validExpiry": 1606910400,
"fingerprint": "sha256/klBxHFTeVG9DcODD06PsRbyWCSolpKcaGvo5avcEfrg=",
"issuerCert": {
"data": "-----BEGIN CERTIFICATE-----[...]-----END CERTIFICATE-----\n",
"issuer": {
"commonName": "DigiCert Global Root CA",
"organizations": ["DigiCert Inc"],
"organizationUnits": ["www.digicert.com"],
"locality": "",
"state": "",
"country": "US"
},
"issuerName": "DigiCert Global Root CA",
"subject": {
"commonName": "DigiCert SHA2 Secure Server CA",
"organizations": ["DigiCert Inc"],
"organizationUnits": [],
"locality": "",
"state": "",
"country": "US"
},
"subjectName": "DigiCert SHA2 Secure Server CA",
"serialNumber": "01FDA3EB6ECA75C888438B724BCFBC91",
"validStart": 1362744000,
"validExpiry": 1678276800,
"fingerprint": "sha256/FUxDPEkZKcXvaG6DjjI2ZKAOag2CLMyVj7TasD5JoI8=",
"issuerCert": {
"data": "-----BEGIN CERTIFICATE-----[...]-----END CERTIFICATE-----\n",
"issuer": {
"commonName": "DigiCert Global Root CA",
"organizations": ["DigiCert Inc"],
"organizationUnits": ["www.digicert.com"],
"locality": "",
"state": "",
"country": "US"
},
"issuerName": "DigiCert Global Root CA",
"subject": {
"commonName": "DigiCert Global Root CA",
"organizations": ["DigiCert Inc"],
"organizationUnits": ["www.digicert.com"],
"locality": "",
"state": "",
"country": "US"
},
"subjectName": "DigiCert Global Root CA",
"serialNumber": "083BE056904246B1A1756AC95991C74A",
"validStart": 1163116800,
"validExpiry": 1952035200,
"fingerprint": "sha256/Q0ig6URMeMsmXgWNXolEtNhPlmK9Jtslf4k0pEPHAWE="
}
}
},
"verificationResult": "net::OK",
"errorCode": 0
}
```
**The full chain, including the root CA, exists in the _request_ object above**
I think [this](https://github.com/electron/electron/pull/7917/files) PR somehow related to this issue (if it is an issue (?))
My problem is that I cannot pin all root CA into my application to avoid a MITM attack.
|
https://github.com/electron/electron/issues/19751
|
https://github.com/electron/electron/pull/21890
|
f34cbe66a0dcd2d5c8941ab7adde776b8bd112fa
|
37feeb8e5ffafa60b5da731ad94e57a485b0f53a
| 2019-08-14T12:09:27Z |
c++
| 2020-01-27T18:48:29Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,738 |
["patches/node/inherit_electron_crashpad_pipe_name_in_child_process.patch", "patches/node/refactor_alter_child_process_fork_to_use_execute_script_with.patch"]
|
ELECTRON_RUN_AS_NODE can be erroneously set for render processes
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v4.2.5
* **Operating System:**
* macOS 10.13.6 / Windows 10 (1803)
* **Last Known Working Electron version:**
* N/A
### Expected Behavior
ELECTRON_RUN_AS_NODE should never be set in the Electron main `process.env`.
### Actual Behavior
`ELECTRON_RUN_AS_NODE` is set in the Electron main `process.env` after calling `child_process.fork()`, passing in `process.env` directly as `options.env`.
This can cause a number of problems, the main symptom is that reloading the browser window will no longer work. It is likely that creating additional browser windows will also no longer work after this point.
### To Reproduce
See fiddle:
https://gist.github.com/cdc803312b25b151d53629d0c13bc896
The console output is:
```
Before fork, ELECTRON_RUN_AS_NODE is undefined
After fork, ELECTRON_RUN_AS_NODE is 1
Hello world
```
ELECTRON_RUN_AS_NODE should not be set!
### Additional Information
The Electron version of Node gets patched to set `ELECTRON_RUN_AS_NODE=1` in the environment of the child process:
https://github.com/electron/electron/blob/9713fa09e75342094e382399be87633246e5437b/patches/node/refactor_alter_child_process_fork_to_use_execute_script_with.patch
It's quite common though for code to pass in `process.env` as an option to child_process.fork() (worker-farm does this for instance). In this case, this line changes the actual process.env for the current process, not a copy:
https://github.com/electron/electron/blob/9713fa09e75342094e382399be87633246e5437b/patches/node/refactor_alter_child_process_fork_to_use_execute_script_with.patch#L21
Initially this is harmless, however the next time any new process is spawned it will inherit the current environment including `ELECTRON_RUN_AS_NODE`, even if it should be run as Electron. This causes all sorts of malfunctions.
I suspect the solution will be to ensure we modify a copy of the environment we have been passed, for instance changing:
```
// When forking a child script, we setup a special environment to make
// the atom-shell binary run like the upstream node.
if (!options.env) {
options.env = Object.create(process.env);
}
options.env.ELECTRON_RUN_AS_NODE = 1;
```
to something like:
```
// When forking a child script, we setup a special environment to make
// the atom-shell binary run like the upstream node.
if (options.env) {
options.env = Object.create(options.env);
} else {
options.env = Object.create(process.env);
}
options.env.ELECTRON_RUN_AS_NODE = 1;
```
As a workaround, callers can explicitly pass a copy of `process.env` (worker-farm supports this for instance).
Reported by several people here:
https://github.com/electron/electron/issues/18412
|
https://github.com/electron/electron/issues/19738
|
https://github.com/electron/electron/pull/19742
|
680399f47657bc9767ffe7b7c5146a7eb107cf4d
|
33f2ec6355be52f2bf19a9d98ea290aa5180d046
| 2019-08-13T21:46:44Z |
c++
| 2019-08-15T15:01:58Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,687 |
["docs/api/web-contents.md", "patches/chromium/printing.patch", "spec-main/api-web-contents-spec.ts", "spec/fixtures/pages/window-print.html"]
|
`window.print()` not working in electron 7.0.0-beta.2
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 7.0.0-beta-2
* **Operating System:**
* MacOs Mojave 10.14.6
* **Last Known Working Electron version:**
* 7.0.0-beta.1
### Expected Behavior
Show system print dialog.
### Actual Behavior
Nothing happens.
### To Reproduce
Add `<script>window.print();</script>` into `index.html` in [*Electron Fiddle*](https://electronjs.org/fiddle).
|
https://github.com/electron/electron/issues/19687
|
https://github.com/electron/electron/pull/19690
|
ba5ee79af8b230088b9f9172dcb1c4054e3869e0
|
e8fa248571e755cdfbb8d377dba320e68a138112
| 2019-08-08T19:22:20Z |
c++
| 2019-08-13T06:44:14Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,663 |
["shell/browser/ui/file_dialog_gtk.cc"]
|
Feature Request: support localization of button labels in Open and Save dialogs
|
### Problem Description
I use ubuntu linux. my system language is Chinese, but the dialog button labels is English by default. I found the buttonLabel option from the API to set the label of the save or open button, but the label of the cancel button is not supported.
### Proposed Solution
Support customizing cancel button label in Open and Save dialogs
|
https://github.com/electron/electron/issues/19663
|
https://github.com/electron/electron/pull/19725
|
49fe2604b38a52ff59ea7d3c142485db42898ba3
|
5d892a557f0b29f595a85d354c3f912964418e12
| 2019-08-07T08:18:53Z |
c++
| 2019-08-14T03:22:25Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,613 |
["docs/api/browser-window.md", "shell/browser/ui/cocoa/atom_ns_window_delegate.mm"]
|
Implement BrowserWindow "will-move" for mac
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
This event is needed for window management. and resetting the bounds after a move has happened makes the window flicker badly.
### Proposed Solution
Please implement this event (with the ability to prevent default) for Mac as well.
### Alternatives Considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/19613
|
https://github.com/electron/electron/pull/19641
|
cd1b15a155a42f74b127e0b99ba71f824ee313e0
|
145b4fae94c2c46864f456bc4a7bbfb188864b9f
| 2019-08-03T22:06:47Z |
c++
| 2019-08-20T14:53:43Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,611 |
["shell/browser/ui/cocoa/atom_ns_window_delegate.mm"]
|
BrowserWindow's "will-resize" event's callback is provided with bizarre newBounds value
|
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0
* **Operating System:**
* MacOS any
* **Last Known Working Electron version:**
* none that I know of
### Expected Behavior
The actual new bounds (correct x, y, width and height) to be provided as the new bounds to the callback of `will-resize` event
### Actual Behavior
On mac (and only mac) it provides some very bizarre values. It seems that the `y` and `x` are actually calculated from the BOTTOM-RIGHT corner of the DISPLAY bounds to the BOTTOM-RIGHT of the window bounds. Instead of the usual (by that I mean what you get from `getBounds`) `x` and `y` that is calculated from the TOP-LEFT of the DISPLAY to the TOP-LEFT of the window.
in other words imagine this:
My display is 100x100 and I have a window at 10, 20 with width: 30, and height 40
the `getBounds` function gives me (10, 20, 30, 40) all good.
when I resize from the TOP, UP for 1 pixel, the new bounds would be: (10, 19, 10, 41)
because the height is increased by one, while the `y` is reduced by one.
however the `will-resize` event on MAC gives me: (60, 40, 10, 41)
60 is the `display.width - bounds.width - bounds.x`.
40 is the `display.height - bounds.height - bounds.y`. why?!
and what's worse? there is no way to transform these, because not only the `x` and the `y` are wrong, they never reflect what is going on, that means, even if I resize from BOTTOM in the UP direction, it still gives me the same WRONG newBounds.
this means, there is absolutely no way to even work around this issue. I have no way of knowing whether the user dragged the TOP edge down or the BOTTOM edge down. the data is so bizarre that I spent a whole day trying to figure out what the values meant and how I could fix them. there is no way. It has to be fixed here
### To Reproduce
Simply listen to `will-resize` of any window and log the `newBounds` argument.
|
https://github.com/electron/electron/issues/19611
|
https://github.com/electron/electron/pull/19639
|
fec54c9c5ddf587febc11027d79ca70b0e6b3dac
|
9eb89b4ac712adfc23b7dbd4fc5dea9853988e73
| 2019-08-03T19:41:35Z |
c++
| 2019-08-08T02:58:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,602 |
["patches/chromium/.patches", "patches/chromium/expose_setuseragent_on_networkcontext.patch", "shell/browser/api/atom_api_session.cc", "spec-main/api-session-spec.ts"]
|
network serviceification followup
|
Since #19488, the network service is enabled and the old path has been deleted. Some features are broken as a result and will need to be fixed before 8.0.0. This is a tracking issue for those features.
- [x] webRequest API (zcbenz)
- [x] service workers on file protocol (#20132)
- [x] session.clearAuthCache - tests (#20015)
- [x] session.getBlobData (#20041)
- [x] session.setUserAgent (#20014)
- [x] custom standard schemes / registerSchemesAsPrivileged
- [x] Rewire Login Handler from NetworkDelegate into ProxyingURLLoaderFactory
- [x] fix 'login' event not firing on net requests
cc @deepak1556 @jkleinsc @zcbenz
|
https://github.com/electron/electron/issues/19602
|
https://github.com/electron/electron/pull/20014
|
b3947d6a83208971cfdaa1442ebcf8c8c82183ec
|
90d62e5b98302915a0b70bd0f748684b4f108e5e
| 2019-08-03T00:03:45Z |
c++
| 2019-08-29T06:50:14Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,588 |
["shell/browser/browser_win.cc"]
|
Win: app.clearRecentDocuments does not work
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
app.clearRecentDocuments does not work on Windows.
* **Electron Version:**
* 5.0.8
* **Operating System:**
* Windows 10 pro; build 1903
* **Last Known Working Electron version:**
* <!-- (if applicable) e.g. 3.1.0 -->
### Expected Behavior
List of recent documents should be cleared
### Actual Behavior
List of recent documents continues to accumulate
### To Reproduce
Try `app.clearRecentDocuments();` on Windows
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/19588
|
https://github.com/electron/electron/pull/19599
|
33a9d898a6a3ddfa110d43a9b07205e07383e853
|
f0396c19be63d0e73cfc69867accffe2bd0d9dad
| 2019-08-02T03:55:46Z |
c++
| 2019-08-05T22:11:43Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,539 |
["patches/chromium/printing.patch"]
|
Crash when printing to PDF in 5.0.5+
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 5.0.5
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 -->
* **Operating System:** macOS 10.14.4
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 -->
* **Last Known Working Electron version:** 5.0.4
* <!-- (if applicable) e.g. 3.1.0 -->
### To Reproduce
Clone electron-quick-start, and put this in index.html:
```
<script>
window.print()
</script>
```
When the print dialog opens, choose "PDF" in the bottom-left corner, then "open in preview". The PDF will open successfully, but shortly after that Electron will crash.
Crash report:
<details>
Process: Electron [85956]
Path: /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron
Identifier: com.github.Electron
Version: 5.0.5 (5.0.5)
Code Type: X86-64 (Native)
Parent Process: ??? [85955]
Responsible: Electron [85956]
User ID: 501
Date/Time: 2019-07-31 01:49:14.439 -0500
OS Version: Mac OS X 10.14.4 (18E227)
Report Version: 12
Anonymous UUID: 0C9E7938-A39B-A861-CC7F-2E5F772F8BE2
Sleep/Wake UUID: 295EAED6-D13E-4E07-AFA5-1C45B0B7A57B
Time Awake Since Boot: 1200000 seconds
Time Since Wake: 3400 seconds
System Integrity Protection: enabled
Crashed Thread: 23 TaskSchedulerBackgroundBlockingWorker
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fa70000020a
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [85956]
VM Regions Near 0x7fa70000020a:
Stack 0000700012c3e000-0000700013440000 [ 8200K] rw-/rwx SM=COW thread 33
-->
MALLOC_TINY 00007fa758400000-00007fa758800000 [ 4096K] rw-/rwx SM=PRV
Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_platform.dylib 0x00007fff67322d09 _platform_memmove$VARIANT$Haswell + 41
1 com.github.Electron.framework 0x000000010c0f1ca5 0x10c0ea000 + 31909
2 com.github.Electron.framework 0x000000010e39c73a 0x10c0ea000 + 36382522
3 com.github.Electron.framework 0x000000010e39c62c 0x10c0ea000 + 36382252
4 com.github.Electron.framework 0x000000010cec6d72 0x10c0ea000 + 14536050
5 com.github.Electron.framework 0x000000010e398a39 0x10c0ea000 + 36366905
6 com.github.Electron.framework 0x000000010e3b7953 0x10c0ea000 + 36493651
7 com.github.Electron.framework 0x000000010e3d23cf 0x10c0ea000 + 36602831
8 com.github.Electron.framework 0x000000010e3d2933 0x10c0ea000 + 36604211
9 com.github.Electron.framework 0x000000010e4791a3 0x10c0ea000 + 37286307
10 com.github.Electron.framework 0x000000010e3b2b1a 0x10c0ea000 + 36473626
11 com.github.Electron.framework 0x000000010e478b0f 0x10c0ea000 + 37284623
12 com.apple.CoreFoundation 0x00007fff3ace45e3 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
13 com.apple.CoreFoundation 0x00007fff3ace4589 __CFRunLoopDoSource0 + 108
14 com.apple.CoreFoundation 0x00007fff3acc7f3b __CFRunLoopDoSources0 + 195
15 com.apple.CoreFoundation 0x00007fff3acc7505 __CFRunLoopRun + 1189
16 com.apple.CoreFoundation 0x00007fff3acc6e0e CFRunLoopRunSpecific + 455
17 com.apple.HIToolbox 0x00007fff39fb39db RunCurrentEventLoopInMode + 292
18 com.apple.HIToolbox 0x00007fff39fb3715 ReceiveNextEventCommon + 603
19 com.apple.HIToolbox 0x00007fff39fb34a6 _BlockUntilNextEventMatchingListInModeWithFilter + 64
20 com.apple.AppKit 0x00007fff3834dffb _DPSNextEvent + 965
21 com.apple.AppKit 0x00007fff3834cd93 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
22 com.apple.AppKit 0x00007fff38346eb0 -[NSApplication run] + 699
23 com.github.Electron.framework 0x000000010e47999c 0x10c0ea000 + 37288348
24 com.github.Electron.framework 0x000000010e4784df 0x10c0ea000 + 37283039
25 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
26 com.github.Electron.framework 0x000000010cc449f3 0x10c0ea000 + 11905523
27 com.github.Electron.framework 0x000000010cc44830 0x10c0ea000 + 11905072
28 com.github.Electron.framework 0x000000010cc46852 0x10c0ea000 + 11913298
29 com.github.Electron.framework 0x000000010cc41704 0x10c0ea000 + 11892484
30 com.github.Electron.framework 0x000000010e005d9e 0x10c0ea000 + 32619934
31 com.github.Electron.framework 0x000000010e005a11 0x10c0ea000 + 32619025
32 com.github.Electron.framework 0x000000010fbb026f 0x10c0ea000 + 61629039
33 com.github.Electron.framework 0x000000010e004e64 0x10c0ea000 + 32616036
34 com.github.Electron.framework 0x000000010c0ecd14 AtomMain + 84
35 com.github.Electron 0x000000010c0bc9b0 0x10c0bb000 + 6576
36 libdyld.dylib 0x00007fff671403d5 start + 1
Thread 1:
0 libsystem_pthread.dylib 0x00007fff6732d3f0 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x00007fff6732d3f0 start_wqthread + 0
Thread 3:
0 libsystem_pthread.dylib 0x00007fff6732d3f0 start_wqthread + 0
Thread 4:
0 libsystem_pthread.dylib 0x00007fff6732d3f0 start_wqthread + 0
Thread 5:: TaskSchedulerServiceThread
0 libsystem_kernel.dylib 0x00007fff6727b78e kevent + 10
1 com.github.Electron.framework 0x000000010e47f569 0x10c0ea000 + 37311849
2 com.github.Electron.framework 0x000000010e47d05d 0x10c0ea000 + 37302365
3 com.github.Electron.framework 0x000000010e472cfe 0x10c0ea000 + 37260542
4 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
5 com.github.Electron.framework 0x000000010e425cf7 0x10c0ea000 + 36945143
6 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 6:: TaskSchedulerForegroundWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421b62 0x10c0ea000 + 36928354
6 com.github.Electron.framework 0x000000010e421a74 0x10c0ea000 + 36928116
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 7:: TaskSchedulerForegroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421e2e 0x10c0ea000 + 36929070
6 com.github.Electron.framework 0x000000010e421a74 0x10c0ea000 + 36928116
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 8:: TaskSchedulerBackgroundWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421b62 0x10c0ea000 + 36928354
6 com.github.Electron.framework 0x000000010e4219e4 0x10c0ea000 + 36927972
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 9:: TaskSchedulerBackgroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421e2e 0x10c0ea000 + 36929070
6 com.github.Electron.framework 0x000000010e4219e4 0x10c0ea000 + 36927972
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 10:: Chrome_IOThread
0 libsystem_kernel.dylib 0x00007fff6727b78e kevent + 10
1 com.github.Electron.framework 0x000000010e47f569 0x10c0ea000 + 37311849
2 com.github.Electron.framework 0x000000010e47d05d 0x10c0ea000 + 37302365
3 com.github.Electron.framework 0x000000010e472cfe 0x10c0ea000 + 37260542
4 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
5 com.github.Electron.framework 0x000000010cc4c424 0x10c0ea000 + 11936804
6 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff6727b78e kevent + 10
1 com.github.Electron.framework 0x000000011171144f 0x10c0ea000 + 90338383
2 com.github.Electron.framework 0x0000000111701581 uv_run + 401
3 com.github.Electron.framework 0x000000011167f556 0x10c0ea000 + 89740630
4 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
5 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
6 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 12:
0 libsystem_kernel.dylib 0x00007fff6727886a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6733156e _pthread_cond_wait + 722
2 com.github.Electron.framework 0x000000011170c799 uv_cond_wait + 9
3 com.github.Electron.framework 0x000000011167f658 0x10c0ea000 + 89740888
4 com.github.Electron.framework 0x000000011167d3d8 0x10c0ea000 + 89732056
5 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
6 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
7 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff6727886a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6733156e _pthread_cond_wait + 722
2 com.github.Electron.framework 0x000000011170c799 uv_cond_wait + 9
3 com.github.Electron.framework 0x000000011167f658 0x10c0ea000 + 89740888
4 com.github.Electron.framework 0x000000011167d3d8 0x10c0ea000 + 89732056
5 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
6 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
7 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff6727886a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6733156e _pthread_cond_wait + 722
2 com.github.Electron.framework 0x000000011170c799 uv_cond_wait + 9
3 com.github.Electron.framework 0x000000011167f658 0x10c0ea000 + 89740888
4 com.github.Electron.framework 0x000000011167d3d8 0x10c0ea000 + 89732056
5 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
6 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
7 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff67275266 semaphore_wait_trap + 10
1 com.github.Electron.framework 0x000000011170cd00 uv_sem_wait + 16
2 com.github.Electron.framework 0x00000001116c7d12 0x10c0ea000 + 90037522
3 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 16:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3acc813e __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff3acc76ac __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff3acc6e0e CFRunLoopRunSpecific + 455
5 com.apple.Foundation 0x00007fff3cf1da9f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
6 com.github.Electron.framework 0x000000010e4796b1 0x10c0ea000 + 37287601
7 com.github.Electron.framework 0x000000010e4784df 0x10c0ea000 + 37283039
8 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
9 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
10 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
11 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
12 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
13 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 17:: DnsConfigService
0 libsystem_kernel.dylib 0x00007fff6727b78e kevent + 10
1 com.github.Electron.framework 0x000000010e47f569 0x10c0ea000 + 37311849
2 com.github.Electron.framework 0x000000010e47d05d 0x10c0ea000 + 37302365
3 com.github.Electron.framework 0x000000010e472d17 0x10c0ea000 + 37260567
4 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
5 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
6 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
7 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
8 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
9 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 18:: CrShutdownDetector
0 libsystem_kernel.dylib 0x00007fff67276ef2 read + 10
1 com.github.Electron.framework 0x000000010e2d532f 0x10c0ea000 + 35566383
2 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
3 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 19:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3acc813e __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff3acc76ac __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff3acc6e0e CFRunLoopRunSpecific + 455
5 com.apple.Foundation 0x00007fff3cf1da9f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
6 com.github.Electron.framework 0x000000010e4796b1 0x10c0ea000 + 37287601
7 com.github.Electron.framework 0x000000010e4784df 0x10c0ea000 + 37283039
8 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
9 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
10 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
11 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
12 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
13 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 20:: TaskSchedulerForegroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421e2e 0x10c0ea000 + 36929070
6 com.github.Electron.framework 0x000000010e421a74 0x10c0ea000 + 36928116
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 21:: TaskSchedulerForegroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421e2e 0x10c0ea000 + 36929070
6 com.github.Electron.framework 0x000000010e421a74 0x10c0ea000 + 36928116
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 22:: TaskSchedulerForegroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421b62 0x10c0ea000 + 36928354
6 com.github.Electron.framework 0x000000010e421a74 0x10c0ea000 + 36928116
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 23 Crashed:: TaskSchedulerBackgroundBlockingWorker
0 com.github.Electron.framework 0x000000010e434950 0x10c0ea000 + 37005648
1 com.github.Electron.framework 0x000000010e3b7953 0x10c0ea000 + 36493651
2 com.github.Electron.framework 0x000000010e429ffd 0x10c0ea000 + 36962301
3 com.github.Electron.framework 0x000000010e429b3c 0x10c0ea000 + 36961084
4 com.github.Electron.framework 0x000000010e46ac87 0x10c0ea000 + 37227655
5 com.github.Electron.framework 0x000000010e422461 0x10c0ea000 + 36930657
6 com.github.Electron.framework 0x000000010e421d04 0x10c0ea000 + 36928772
7 com.github.Electron.framework 0x000000010e4219e4 0x10c0ea000 + 36927972
8 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
9 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
10 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
11 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 24:: CompositorTileWorker1/45571
0 libsystem_kernel.dylib 0x00007fff6727886a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff6733156e _pthread_cond_wait + 722
2 com.github.Electron.framework 0x000000010e46a365 0x10c0ea000 + 37225317
3 com.github.Electron.framework 0x000000010f4e3808 0x10c0ea000 + 54499336
4 com.github.Electron.framework 0x000000010e435c92 0x10c0ea000 + 37010578
5 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
6 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
7 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
8 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 25:: AudioThread
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e3ef36f 0x10c0ea000 + 36721519
4 com.github.Electron.framework 0x000000010e3d333d 0x10c0ea000 + 36606781
5 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
6 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 26:
0 libsystem_kernel.dylib 0x00007fff6727c61a __select + 10
1 com.github.Electron.framework 0x000000010e361782 0x10c0ea000 + 36140930
2 com.github.Electron.framework 0x000000010e36122f 0x10c0ea000 + 36139567
3 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 27:: TaskSchedulerSingleThreadForegroundBlocking0
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e3ef36f 0x10c0ea000 + 36721519
4 com.github.Electron.framework 0x000000010e4217ea 0x10c0ea000 + 36927466
5 com.github.Electron.framework 0x000000010e421e2e 0x10c0ea000 + 36929070
6 com.github.Electron.framework 0x000000010e421ad4 0x10c0ea000 + 36928212
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 28:: TaskSchedulerSingleThreadSharedBackgroundBlocking1
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e3ef36f 0x10c0ea000 + 36721519
4 com.github.Electron.framework 0x000000010e4217ea 0x10c0ea000 + 36927466
5 com.github.Electron.framework 0x000000010e421b62 0x10c0ea000 + 36928354
6 com.github.Electron.framework 0x000000010e421a14 0x10c0ea000 + 36928020
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 29:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3acc813e __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff3acc76ac __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff3acc6e0e CFRunLoopRunSpecific + 455
5 com.apple.Foundation 0x00007fff3cf1da9f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
6 com.github.Electron.framework 0x000000010e4796b1 0x10c0ea000 + 37287601
7 com.github.Electron.framework 0x000000010e4784df 0x10c0ea000 + 37283039
8 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
9 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
10 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
11 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
12 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
13 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 30:: TaskSchedulerBackgroundBlockingWorker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e405ed1 0x10c0ea000 + 36814545
4 com.github.Electron.framework 0x000000010e4217f8 0x10c0ea000 + 36927480
5 com.github.Electron.framework 0x000000010e421b62 0x10c0ea000 + 36928354
6 com.github.Electron.framework 0x000000010e4219e4 0x10c0ea000 + 36927972
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 31:: CacheThread_BlockFile
0 libsystem_kernel.dylib 0x00007fff6727b78e kevent + 10
1 com.github.Electron.framework 0x000000010e47f569 0x10c0ea000 + 37311849
2 com.github.Electron.framework 0x000000010e47d05d 0x10c0ea000 + 37302365
3 com.github.Electron.framework 0x000000010e472cfe 0x10c0ea000 + 37260542
4 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
5 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
6 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
7 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
8 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
9 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 32:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3acc813e __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff3acc76ac __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff3acc6e0e CFRunLoopRunSpecific + 455
5 com.apple.AppKit 0x00007fff38355d1a _NSEventThread + 175
6 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
7 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
8 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 33:: Printing_Worker
0 libsystem_kernel.dylib 0x00007fff6727522a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6727576c mach_msg + 60
2 com.github.Electron.framework 0x000000010e405dc0 0x10c0ea000 + 36814272
3 com.github.Electron.framework 0x000000010e3ef36f 0x10c0ea000 + 36721519
4 com.github.Electron.framework 0x000000010e3d333d 0x10c0ea000 + 36606781
5 com.github.Electron.framework 0x000000010e3f12f8 0x10c0ea000 + 36729592
6 com.github.Electron.framework 0x000000010e4363ea 0x10c0ea000 + 37012458
7 com.github.Electron.framework 0x000000010e473067 0x10c0ea000 + 37261415
8 libsystem_pthread.dylib 0x00007fff6732e2eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff67331249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff6732d40d thread_start + 13
Thread 34:
0 libsystem_pthread.dylib 0x00007fff6732d3f0 start_wqthread + 0
Thread 23 crashed with X86 Thread State (64-bit):
rax: 0x00007fa7588d4000 rbx: 0x00007fa75a8d8c30 rcx: 0x0000000000000000 rdx: 0x0000000000000100
rdi: 0x00007fa700000202 rsi: 0x000070000ea16b48 rbp: 0x000070000ea169c0 rsp: 0x000070000ea16990
r8: 0x000070000ea169f0 r9: 0x0000000000000001 r10: 0x00007fa75af6eb20 r11: 0x00007fa75a852ea0
r12: 0x00007fa758418c38 r13: 0x000070000ea16b48 r14: 0x0000000000000000 r15: 0x00007fa75a8d8c30
rip: 0x000000010e434950 rfl: 0x0000000000010206 cr2: 0x00007fa70000020a
Logical CPU: 1
Error Code: 0x00000004
Trap Number: 14
Binary Images:
0x10c0bb000 - 0x10c0e3ff7 +com.github.Electron (5.0.5 - 5.0.5) <3788637B-0A53-3737-B3B6-C827ABF3E314> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/MacOS/Electron
0x10c0ea000 - 0x11229cf9f +com.github.Electron.framework (5.0.5) <F5A409A2-5B3D-3ED6-B4A3-4ABACB8F3605> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
0x1128ec000 - 0x112907fff +com.github.Squirrel (1.0 - 1) <E4398068-33D3-3A00-9DBE-5ACC9B022501> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/Frameworks/Squirrel.framework/Versions/A/Squirrel
0x11292f000 - 0x112992ff7 +org.reactivecocoa.ReactiveCocoa (1.0 - 1) <701B20DE-3ADD-3643-B52A-E05744C30DB3> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/Frameworks/ReactiveCocoa.framework/Versions/A/ReactiveCocoa
0x112a0b000 - 0x112a1ffff +org.mantle.Mantle (1.0 - ???) <31915DD6-48E6-3706-A076-C9D4CE17F4F6> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/Frameworks/Mantle.framework/Versions/A/Mantle
0x112a38000 - 0x112cb9fe7 +libffmpeg.dylib (0) <5AB84A10-1627-3C9C-8671-065B476B33F2> /usr/local/lib/node_modules/electron/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib
0x114635000 - 0x11469f6ef dyld (655.1.1) <F217F7F8-A795-3109-B77F-B1E2277F3E3B> /usr/lib/dyld
0x116671000 - 0x116674047 libobjc-trampolines.dylib (756.2) <E0ADAED0-0649-399B-856E-29BA398C6433> /usr/lib/libobjc-trampolines.dylib
0x1187e6000 - 0x118819ff3 com.apple.print.framework.Print.Private (14.4 - 589.12) <33EDB3ED-81BF-3213-98BE-F63B071C6A68> /System/Library/PrivateFrameworks/PrintingPrivate.framework/Versions/Current/Plugins/PrintCocoaUI.bundle/Contents/MacOS/PrintCocoaUI
0x11883a000 - 0x118876fff com.apple.print.PrintingCocoaPDEs (14.4 - 589.12) <475C69B8-AF26-3712-B29C-B613934B3FBE> /System/Library/PrivateFrameworks/PrintingPrivate.framework/Versions/A/Plugins/PrintingCocoaPDEs.bundle/Contents/MacOS/PrintingCocoaPDEs
0x7fff2f777000 - 0x7fff2facffff com.apple.RawCamera.bundle (8.14.0 - 1031.4.2) <7CEBABD9-0E85-3670-9836-40DD190C48A8> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x7fff327b6000 - 0x7fff328b3ff7 com.apple.driver.AppleIntelBDWGraphicsMTLDriver (12.8.38 - 12.0.8) <D7046DC2-E1AE-3050-95DA-5AAB34A80F74> /System/Library/Extensions/AppleIntelBDWGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelBDWGraphicsMTLDriver
0x7fff36d57000 - 0x7fff36f31ff7 com.apple.avfoundation (2.0 - 1546.25) <744B1F04-5F34-39F4-A594-34518CEA2421> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
0x7fff36f32000 - 0x7fff36ff7fff com.apple.audio.AVFAudio (1.0 - ???) <7F3AA3FD-9F0B-3714-8F05-7272CEC9E33B> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Frameworks/AVFAudio.framework/Versions/A/AVFAudio
0x7fff370ff000 - 0x7fff370fffff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff37100000 - 0x7fff37116ff7 libCGInterfaces.dylib (506.22) <A3CDEEC3-42B0-3C6E-9CCE-465C472609CD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
0x7fff37117000 - 0x7fff377b0fef com.apple.vImage (8.1 - ???) <F9C4B95C-7BE9-30A4-98D4-FD9996EE5E81> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff377b1000 - 0x7fff37a2aff3 libBLAS.dylib (1243.200.4) <F2B8340C-4147-3EE4-9BDF-1C259F9CB76E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff37a2b000 - 0x7fff37a9dffb libBNNS.dylib (38.250.1) <95A91B57-17B8-389F-B324-3AD42BBEA3E6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
0x7fff37a9e000 - 0x7fff37e47ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x7fff37e48000 - 0x7fff37e5dfeb libLinearAlgebra.dylib (1243.200.4) <BD6B8E28-C982-3002-868C-C96A18175030> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
0x7fff37e5e000 - 0x7fff37e63ff3 libQuadrature.dylib (3.200.2) <354D7970-0570-32E0-ABAE-222DAAF1F7A9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
0x7fff37e64000 - 0x7fff37ee0ff3 libSparse.dylib (79.200.5) <DCC01AE4-FC16-3C7B-9010-999411448164> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
0x7fff37ee1000 - 0x7fff37ef4fe3 libSparseBLAS.dylib (1243.200.4) <95B6FFFD-CDD5-3ABB-B862-6A86720DCD77> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
0x7fff37ef5000 - 0x7fff380dcff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x7fff380dd000 - 0x7fff38190ff7 libvMisc.dylib (671.250.4) <41FB4684-9DC8-3C19-8E2D-3BB7E6F74AAA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x7fff38191000 - 0x7fff38191fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff38192000 - 0x7fff381ecfff com.apple.Accounts (113 - 113) <A0BB170F-DD5A-3EDB-B8D0-BEEE1BAC0513> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
0x7fff381ef000 - 0x7fff38332fff com.apple.AddressBook.framework (11.0 - 1893) <AD9DE1B9-49D8-3328-A132-C06EA5FAA73F> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x7fff38333000 - 0x7fff390e8fff com.apple.AppKit (6.9 - 1671.40.119) <0A857684-99C7-30A9-8E23-D3015C6B24A3> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff3913a000 - 0x7fff3913afff com.apple.ApplicationServices (50.1 - 50.1) <E57E6BAC-3CA7-3EFB-9A6B-ACF662E07FAC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff3913b000 - 0x7fff391a6fff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <5B30E86D-B3AB-3346-A19F-F2CABF342465> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x7fff3923f000 - 0x7fff39356fff libFontParser.dylib (228.6.2.3) <BBB2EECE-7C24-3D43-A902-EB473A70EDED> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff39357000 - 0x7fff39399fff libFontRegistry.dylib (228.12.2.3) <DEA7AE34-2FA6-336E-BF00-00CA2BDC7584> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff393f3000 - 0x7fff39425fff libTrueTypeScaler.dylib (228.6.2.3) <8F2DA883-4A0E-389A-AB1D-C66FAA3B8E7C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
0x7fff3948a000 - 0x7fff3948eff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <6EDD928D-BC75-385E-AB04-3CB63EAEBF96> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
0x7fff39529000 - 0x7fff3957bff7 com.apple.HIServices (1.22 - 627.15) <1B4C3D08-1DBA-365B-9362-C6708D8844AA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x7fff3957c000 - 0x7fff3958bfff com.apple.LangAnalysis (1.7.0 - 1.7.0) <76B698A9-18B9-3089-9570-4FC3F754D56D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff3958c000 - 0x7fff395d5ff7 com.apple.print.framework.PrintCore (14.2 - 503.8) <885645E0-D760-35EC-B506-7FC2763390DF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x7fff395d6000 - 0x7fff3960fff7 com.apple.QD (3.12 - 407.2) <A414332F-72EC-393B-B2BC-7285268A19BD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x7fff39610000 - 0x7fff3961cfff com.apple.speech.synthesis.framework (8.1.2 - 8.1.2) <1F910DC7-410A-391B-A03D-17605E50B688> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff3961d000 - 0x7fff39894ff7 com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <1C76AD80-1106-312E-B2C0-126A8D62F192> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff39896000 - 0x7fff39896fff com.apple.audio.units.AudioUnit (1.14 - 1.14) <6AFA15D5-1886-3EBF-ADC9-90421375DB30> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff39bee000 - 0x7fff39f8ffff com.apple.CFNetwork (978.0.7 - 978.0.7) <EFB91439-6953-3CD4-8A14-3E7DC90DDF7E> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff39fa4000 - 0x7fff39fa4fff com.apple.Carbon (158 - 158) <080ECFD9-9C4B-3038-9F4B-BE111473E1DE> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff39fa5000 - 0x7fff39fa8ffb com.apple.CommonPanels (1.2.6 - 98) <D56205C5-F466-3B28-9FE3-5B5E1F1ECEF3> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x7fff39fa9000 - 0x7fff3a29ffff com.apple.HIToolbox (2.1.1 - 918.4) <CBD6613A-C5A5-3CF3-866A-B8A8C6FD64B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff3a2a0000 - 0x7fff3a2a3ff3 com.apple.help (1.3.8 - 66) <80B6EAF2-4745-3C04-AC10-4FC3EB08CB8D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x7fff3a2a4000 - 0x7fff3a2a9ff7 com.apple.ImageCapture (9.0 - 1534.2) <B02BE202-793D-3609-8E60-694A39D75CD0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x7fff3a2aa000 - 0x7fff3a33fff3 com.apple.ink.framework (10.9 - 225) <091165EE-D540-3978-9B0C-2FAB5CB185A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff3a340000 - 0x7fff3a358ff7 com.apple.openscripting (1.7 - 179.1) <ED25E087-6A14-32E3-9344-3907541ED9A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x7fff3a378000 - 0x7fff3a379ff7 com.apple.print.framework.Print (14.2 - 267.4) <3E310F68-2BC7-365B-B36C-AAC243C7FFC4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x7fff3a37a000 - 0x7fff3a37cff7 com.apple.securityhi (9.0 - 55006) <9A3E5426-CAC6-3B28-A3B7-C97A1B5CE9BC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x7fff3a37d000 - 0x7fff3a383ff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <E38A62C5-31EE-3BE7-83E5-CF126ECF4F51> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff3a4a5000 - 0x7fff3a4a5fff com.apple.Cocoa (6.11 - 23) <C487E1FC-D79C-32B4-950E-68F3060A125E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff3a4b3000 - 0x7fff3a57fff7 com.apple.ColorSync (4.13.0 - 3340.7) <3ABFA780-F46A-3F0A-8504-005ADDA0662E> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff3a580000 - 0x7fff3a668ff7 com.apple.contacts (1.0 - 2901) <AFBFDEB5-D426-3A81-858E-D14886546762> /System/Library/Frameworks/Contacts.framework/Versions/A/Contacts
0x7fff3a70b000 - 0x7fff3a791fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <7D8A5C9A-3F58-38C2-A1DC-20765150C742> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff3a7f5000 - 0x7fff3a81fffb com.apple.CoreBluetooth (1.0 - 1) <D0C72748-F75A-3C27-9620-C7973C4D365D> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
0x7fff3a820000 - 0x7fff3aba4fe3 com.apple.CoreData (120 - 866.5) <7A8DBE88-C7D4-39B4-87E6-508DA68BDAA8> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff3aba5000 - 0x7fff3ac8cff7 com.apple.CoreDisplay (101.3 - 108.11) <373AC375-0178-3721-8FFB-248D96E6AB05> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
0x7fff3ac8d000 - 0x7fff3b0d0fff com.apple.CoreFoundation (6.9 - 1570.16) <F3DFF269-6705-35AD-9F01-66D77DD1B518> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff3b0d2000 - 0x7fff3b761fe7 com.apple.CoreGraphics (2.0 - 1251.12) <58D98B52-5BEF-3345-B8DD-AAE476234FC1> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff3b763000 - 0x7fff3ba83fff com.apple.CoreImage (14.2.0 - 720.0.130) <D09743D4-3B21-367D-8C4A-3DB0F1C1E36D> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x7fff3ba84000 - 0x7fff3bafcfff com.apple.corelocation (2245.12.30) <6C27F2BF-3050-36EC-A628-152A313E5312> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation
0x7fff3bafd000 - 0x7fff3bb53ff7 com.apple.audio.midi.CoreMIDI (1.10 - 88) <E853491F-E03C-33E0-A8BE-BDF49CA5EC1E> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x7fff3bb56000 - 0x7fff3bd7ffff com.apple.CoreML (1.0 - 1) <D30944E3-D088-3E6F-80BB-D42EA81083F5> /System/Library/Frameworks/CoreML.framework/Versions/A/CoreML
0x7fff3bd80000 - 0x7fff3be81fff com.apple.CoreMedia (1.0 - 2286.48) <A521E22D-60AC-3048-8829-E430F6304B45> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff3be82000 - 0x7fff3beddff7 com.apple.CoreMediaIO (900.0 - 5025) <CA95EEF2-4A75-34FA-87D9-4A1A69555CFF> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
0x7fff3bede000 - 0x7fff3bedefff com.apple.CoreServices (944.3 - 944.3) <364A9C3B-6841-3E34-A02A-8227FB5C9030> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff3bedf000 - 0x7fff3bf5bff7 com.apple.AE (773 - 773) <3E32B3FF-0A2E-39F6-BBE0-F2E9607AB83A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x7fff3bf5c000 - 0x7fff3c233fff com.apple.CoreServices.CarbonCore (1178.32 - 1178.32) <B5B61DE0-93F8-3A9F-8AA6-ACAAD04B3547> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x7fff3c234000 - 0x7fff3c27cff7 com.apple.DictionaryServices (1.2 - 284.16.3) <3EE59BD1-FCDD-3DE2-A7D6-6C503564E1AC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff3c27d000 - 0x7fff3c285ffb com.apple.CoreServices.FSEvents (1239.200.12 - 1239.200.12) <727151AB-D38F-39B8-B7B3-F0039DBD45D0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
0x7fff3c286000 - 0x7fff3c438fff com.apple.LaunchServices (944.3 - 944.3) <7BB5AEC5-A509-3188-9884-619E0DF8EED6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff3c439000 - 0x7fff3c4d7ff7 com.apple.Metadata (10.7.0 - 1191.56) <8DD9AC75-7D3E-3607-BEA0-556E98C30765> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x7fff3c4d8000 - 0x7fff3c522ff7 com.apple.CoreServices.OSServices (944.3 - 944.3) <B631283D-9B71-3BF0-B0E7-65F8D444179F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x7fff3c523000 - 0x7fff3c58aff7 com.apple.SearchKit (1.4.0 - 1.4.0) <FB1A5F99-FB2F-3533-9658-EB0C82BA2705> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x7fff3c58b000 - 0x7fff3c5acff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <B8B5D959-4236-369D-847D-E696A8293420> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
0x7fff3c8b7000 - 0x7fff3ca19ff3 com.apple.CoreText (352.0 - 584.26.2.7) <C7E919A8-5840-39C9-A9E7-0E686F486109> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff3ca1a000 - 0x7fff3ca57ff3 com.apple.CoreVideo (1.8 - 0.0) <0376A7EC-8C71-3F26-9599-4CA7AB7924EA> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff3ca58000 - 0x7fff3cae6ffb com.apple.framework.CoreWLAN (13.0 - 1370.8) <68770CCD-9C7F-31AB-8BBB-0DE4577D5F61> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff3cc5d000 - 0x7fff3cc68ffb com.apple.DirectoryService.Framework (10.14 - 207.200.4) <ACE3DECB-5687-345C-8D25-8DB7FA7AB5D9> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x7fff3cc69000 - 0x7fff3cd17fff com.apple.DiscRecording (9.0.3 - 9030.4.5) <FE0C27DF-5E03-3C3C-A6C6-73010390E805> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x7fff3cd3d000 - 0x7fff3cd42ffb com.apple.DiskArbitration (2.7 - 2.7) <F30DF62A-0BE9-371D-8D86-96554FF45811> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff3cefe000 - 0x7fff3cf00ff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <EB563555-BF29-3217-92F7-625333EB5083> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback
0x7fff3cf01000 - 0x7fff3d2aeff3 com.apple.Foundation (6.9 - 1570.16) <84055403-9921-3EFC-B593-8F0600EBEE80> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff3d31d000 - 0x7fff3d34cffb com.apple.GSS (4.0 - 2.0) <F5E9FADD-D2DF-3A27-A08B-C74C9F7DB98D> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff3d34d000 - 0x7fff3d366ff3 com.apple.GameController (1.0 - 1) <C1D012D8-15C6-377F-9C14-D8DD8883F153> /System/Library/Frameworks/GameController.framework/Versions/A/GameController
0x7fff3d44c000 - 0x7fff3d554ff7 com.apple.Bluetooth (6.0.11 - 6.0.11f4) <D695F37C-27CE-3231-8136-49124F367418> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff3d5b6000 - 0x7fff3d645fff com.apple.framework.IOKit (2.0.2 - 1483.250.15) <1170EC49-1912-3657-9C71-991653959191> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff3d647000 - 0x7fff3d656ff3 com.apple.IOSurface (255.4.2 - 255.4.2) <9025E034-7D75-36E3-B71B-96E91FAE109B> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff3d657000 - 0x7fff3d6a9ff3 com.apple.ImageCaptureCore (1.0 - 1534.2) <59655185-CDD6-3F8F-A655-C274BDD1C9E9> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCore
0x7fff3d6aa000 - 0x7fff3d835fef com.apple.ImageIO.framework (3.3.0 - 1824.6) <81BA6C12-123A-3FD8-9E88-0698100471A6> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff3d836000 - 0x7fff3d83affb libGIF.dylib (1824.6) <4B7B283B-84C8-38D1-BED4-B507C3EF6E7E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff3d83b000 - 0x7fff3d917fef libJP2.dylib (1824.6) <E2161CB0-E1B7-351D-9FF3-4CF68A538976> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff3d918000 - 0x7fff3d93dfeb libJPEG.dylib (1824.6) <0968BAF1-5E5A-3AA0-A971-3B3FFC4A4B66> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff3dc00000 - 0x7fff3dc26feb libPng.dylib (1824.6) <661821A6-4BF5-31C6-AFDB-7874A446756C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff3dc27000 - 0x7fff3dc29ffb libRadiance.dylib (1824.6) <0154D539-DF89-3F75-A8F1-92EF147422AF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff3dc2a000 - 0x7fff3dc77fe7 libTIFF.dylib (1824.6) <D608EAA9-4159-347E-A449-0A8CAB85DC02> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff3df72000 - 0x7fff3edd5fff com.apple.JavaScriptCore (14607 - 14607.1.40.1.4) <D4D58ED1-1325-3FA0-AD7B-7C944D36D35B> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x7fff3eded000 - 0x7fff3ee06fff com.apple.Kerberos (3.0 - 1) <39F3F99E-036E-3406-80D9-8A845D820D4D> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff3ee07000 - 0x7fff3ee3cff3 com.apple.LDAPFramework (2.4.28 - 194.5) <A157D27C-132A-38B8-A6B6-382E19BBD9A6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7fff3ee89000 - 0x7fff3eea6ffb com.apple.CoreAuthentication.SharedUtils (1.0 - 425.250.11) <5FF0B1EB-8E07-3A48-B70F-64455C1C5CBB> /System/Library/Frameworks/LocalAuthentication.framework/Support/SharedUtils.framework/Versions/A/SharedUtils
0x7fff3eea7000 - 0x7fff3eebbfff com.apple.LocalAuthentication (1.0 - 425.250.11) <3080D7BB-CE7C-375D-8D7E-D5445AA58950> /System/Library/Frameworks/LocalAuthentication.framework/Versions/A/LocalAuthentication
0x7fff3f0bf000 - 0x7fff3f0c9fff com.apple.MediaAccessibility (1.0 - 114.4) <FD877F9B-6CAF-3BCD-8D74-5F25D61CB78C> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
0x7fff3f178000 - 0x7fff3f818fff com.apple.MediaToolbox (1.0 - 2286.48) <D6125E51-598A-3A1E-9C75-4BDC5AC03F55> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
0x7fff3f81a000 - 0x7fff3f8a9ff7 com.apple.Metal (161.7.1 - 161.7.1) <18BEB663-0D31-3255-9710-50BC5C3D2A0F> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
0x7fff3f8ab000 - 0x7fff3f8c4ff3 com.apple.MetalKit (1.0 - 113) <6EE8B7C8-A088-3CFF-A570-E0D5C0D5EFAC> /System/Library/Frameworks/MetalKit.framework/Versions/A/MetalKit
0x7fff3f8c5000 - 0x7fff3f8e4ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <BE0FF8B9-2DBA-3276-A293-C8B0F62BFFC4> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore
0x7fff3f8e5000 - 0x7fff3f961fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <7E94924C-1648-3AE2-A32E-FC0AFCA433C6> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage
0x7fff3f962000 - 0x7fff3f989fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E878F04A-43F8-3AA4-B9D8-0401F5F98653> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
0x7fff3f98a000 - 0x7fff3fab5ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <4866922C-9732-3FCE-9419-402E5DD22639> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
0x7fff3fab6000 - 0x7fff3fad0fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <80CB3AF2-4401-3B3C-8941-7DEB648DD001> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
0x7fff3fad1000 - 0x7fff3fad2ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <A589BBEA-93C6-325C-A695-6E7371B8477C> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
0x7fff408c9000 - 0x7fff408d5ff7 com.apple.NetFS (6.0 - 4.0) <7278E8E5-1583-3964-91DA-FB2127DFD63A> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff43373000 - 0x7fff433caff7 com.apple.opencl (2.15.3 - 2.15.3) <F558A6A7-3B33-320E-83C0-CF16220A150F> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff433cb000 - 0x7fff433e6ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <386A02AB-0BFA-3847-A56A-2E0EEC5E5D33> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff433e7000 - 0x7fff433f2ffb com.apple.OpenDirectory (10.14 - 207.200.4) <0BD19D17-7F00-3D56-8734-2EE52992B118> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff43d42000 - 0x7fff43d44fff libCVMSPluginSupport.dylib (17.5.4) <36EB7FAE-4E66-36BF-9B39-623B19486B3B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
0x7fff43d45000 - 0x7fff43d4aff3 libCoreFSCache.dylib (166.2) <1AD45004-2625-3351-8087-77878B95348F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0x7fff43d4b000 - 0x7fff43d4ffff libCoreVMClient.dylib (166.2) <E7FBDAEF-BC56-3662-8D59-71FF88D95F8C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff43d50000 - 0x7fff43d58ff7 libGFXShared.dylib (17.5.4) <E3B4FD28-FF4B-3174-AEB3-9EA12EF88100> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff43d59000 - 0x7fff43d64fff libGL.dylib (17.5.4) <F6D39828-B5D0-3F8D-8DE0-3683A17042E2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff43d65000 - 0x7fff43d9ffe7 libGLImage.dylib (17.5.4) <7EE3273C-41C2-387F-A4B7-793EFAA67769> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff43f13000 - 0x7fff43f51fff libGLU.dylib (17.5.4) <B56C2FEC-CB14-3B61-ADEB-FD4A92931F16> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff448ee000 - 0x7fff448fdffb com.apple.opengl (17.5.4 - 17.5.4) <34FA5E8C-0FAF-3708-836B-E8ACB67EF4F4> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff44c78000 - 0x7fff44dc1ff7 com.apple.QTKit (7.7.3 - 3039) <64E46C0B-C0B2-3255-9278-7FA90752B474> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff44dc2000 - 0x7fff45016fff com.apple.imageKit (3.0 - 1067) <42C1AB59-562B-3966-82A6-8380A6CD03C6> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
0x7fff45017000 - 0x7fff45103ffb com.apple.PDFKit (1.0 - 741.11) <6431D029-59E3-3C2A-90C0-FD1355316F09> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit
0x7fff45104000 - 0x7fff455d3ff7 com.apple.QuartzComposer (5.1 - 370) <1F431ABC-16D3-3C0C-A027-5B83D1EC160D> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
0x7fff455d4000 - 0x7fff455faff7 com.apple.quartzfilters (1.10.0 - 83.1) <0A29F81A-20DD-36A1-B61A-93B677220B84> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters
0x7fff455fb000 - 0x7fff456fcff7 com.apple.QuickLookUIFramework (5.0 - 775.5) <2AF16EB8-E39D-3144-A92B-932894734962> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI
0x7fff456fd000 - 0x7fff456fdfff com.apple.quartzframework (1.5 - 23) <30D153F2-A275-320E-B3CC-2A47FFEB5920> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x7fff456fe000 - 0x7fff45953fff com.apple.QuartzCore (1.11 - 697.24.4.2) <BB1034F0-B791-3AF1-B166-6532B2AB54FE> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff45954000 - 0x7fff459abfff com.apple.QuickLookFramework (5.0 - 775.5) <3B6CF250-5DB7-36A0-9E57-33734DD66148> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7fff45b72000 - 0x7fff45b89ff7 com.apple.SafariServices.framework (14607 - 14607.1.40.1.4) <1D4D4939-DC6A-367C-A019-02294E13BA48> /System/Library/Frameworks/SafariServices.framework/Versions/A/SafariServices
0x7fff4616e000 - 0x7fff46186fff com.apple.ScriptingBridge (1.4 - 78) <F6E6A167-84B7-35FC-8F29-458AAF274B09> /System/Library/Frameworks/ScriptingBridge.framework/Versions/A/ScriptingBridge
0x7fff46187000 - 0x7fff46485ff7 com.apple.security (7.0 - 58286.251.4) <2084C515-AD64-3A48-BE3E-811CAA5A0E41> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff46486000 - 0x7fff46512fff com.apple.securityfoundation (6.0 - 55185.251.1) <4A36D3BA-02B5-3C52-8B49-08EC290E1924> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff46513000 - 0x7fff46543ffb com.apple.securityinterface (10.0 - 55109.200.8) <89019DE6-FC90-3947-9298-8D2B06D7C413> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInterface
0x7fff46544000 - 0x7fff46548ff3 com.apple.xpc.ServiceManagement (1.0 - 1) <139D85D7-C356-36FA-B8F4-696FD37FD1EA> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
0x7fff46796000 - 0x7fff467acffb com.apple.StoreKit (1.0 - 1) <5F85D7AF-AD00-3179-8642-7562B83D4B61> /System/Library/Frameworks/StoreKit.framework/Versions/A/StoreKit
0x7fff468e0000 - 0x7fff4694dfff com.apple.SystemConfiguration (1.17 - 1.17) <90F4626B-F9F6-377C-AA62-B8C23E857244> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff46ba3000 - 0x7fff46effff7 com.apple.VideoToolbox (1.0 - 2286.48) <94A89B19-17C5-3085-8179-E832730B51C6> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff49d62000 - 0x7fff49e07fe7 com.apple.APFS (1.0 - 1) <BA5A03A1-09AF-3859-AA38-BD24C4225E23> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
0x7fff4a6a1000 - 0x7fff4a7ebff7 com.apple.AddressBook.core (1.0 - 1) <4E3E6B43-026C-387A-9F09-77FBCD3952AE> /System/Library/PrivateFrameworks/AddressBookCore.framework/Versions/A/AddressBookCore
0x7fff4a807000 - 0x7fff4a808ff7 com.apple.AggregateDictionary (1.0 - 1) <49B5FD7F-A50C-3D67-BFAB-1C25E60F685A> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
0x7fff4abbf000 - 0x7fff4ad02fff com.apple.AnnotationKit (1.0 - 232.3.30) <83E8D694-3564-389A-AADB-37AD6C91EC9B> /System/Library/PrivateFrameworks/AnnotationKit.framework/Versions/A/AnnotationKit
0x7fff4ae02000 - 0x7fff4ae2eff7 com.apple.framework.Apple80211 (13.0 - 1376.3) <9D32EF36-80E0-35DA-9270-2865C91F1020> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff4b106000 - 0x7fff4b115fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <5D6A617C-999A-3D51-8350-109D55E9428A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
0x7fff4b20f000 - 0x7fff4b21afff com.apple.AppleIDAuthSupport (1.0 - 1) <91975ABC-B2EB-3630-A81E-69A1B95E4D19> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport
0x7fff4b25b000 - 0x7fff4b2a4ff3 com.apple.AppleJPEG (1.0 - 1) <EED8C42F-AF5B-355F-BC86-66A6458513C7> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
0x7fff4b2a5000 - 0x7fff4b2b5fff com.apple.AppleLDAP (10.14 - 46.200.2) <6F990458-C78F-316D-B430-03EAA1E28461> /System/Library/PrivateFrameworks/AppleLDAP.framework/Versions/A/AppleLDAP
0x7fff4b4d5000 - 0x7fff4b4f2fff com.apple.aps.framework (4.0 - 4.0) <485BC6C9-30F5-39D8-859B-25073714AC8A> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService
0x7fff4b4f3000 - 0x7fff4b4f7ff7 com.apple.AppleSRP (5.0 - 1) <6E0F8E86-1EEB-33B4-9126-42AC5574873A> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
0x7fff4b4f8000 - 0x7fff4b51afff com.apple.applesauce (1.0 - ???) <48562D0B-1A1D-3D62-8BC2-61C55D0DCECE> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
0x7fff4b5da000 - 0x7fff4b5ddff7 com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <38206770-87AF-3969-A393-2741BF0DC958> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
0x7fff4b5de000 - 0x7fff4b62eff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <30C1F5C1-0742-3863-95F1-FCE51DF97E2D> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff4b679000 - 0x7fff4b68dffb com.apple.AssertionServices (1.0 - 1) <F64A3177-294E-320C-A0E1-25C4322B98E9> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
0x7fff4ba58000 - 0x7fff4bcf5ff7 com.apple.AuthKit (1.0 - 1) <5BC0D7C7-A46A-3B1A-BDC9-7E9150B5A876> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit
0x7fff4beb7000 - 0x7fff4bebffff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <7F48D9BD-17A8-3A76-8828-EC49245735EE> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
0x7fff4bec0000 - 0x7fff4bf55fff com.apple.backup.framework (1.10.4 - ???) <8247B1BE-DF97-31DC-BCC2-1A15797352D3> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff4bf56000 - 0x7fff4bfc3fff com.apple.BaseBoard (360.27 - 360.27) <215A242E-BD57-3A4B-BCA4-FCC9D674CE7B> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
0x7fff4bfcc000 - 0x7fff4bfd2fff com.apple.BezelServicesFW (317 - 317) <0C78843F-B503-372D-BA43-9A437E88D760> /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServices
0x7fff4c049000 - 0x7fff4c085ff3 com.apple.bom (14.0 - 197.6) <FF77262C-A363-3650-92E6-951DC13D7D2A> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x7fff4c734000 - 0x7fff4c760ffb com.apple.CalendarAgentLink (8.0 - 250) <177A3F0A-A52B-3B32-8032-038881079025> /System/Library/PrivateFrameworks/CalendarAgentLink.framework/Versions/A/CalendarAgentLink
0x7fff4ce21000 - 0x7fff4ce70ff7 com.apple.ChunkingLibrary (201 - 201) <08B75C80-CAA3-3128-BE6C-A1FA3A52A79B> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
0x7fff4cf86000 - 0x7fff4d00bff7 com.apple.CloudDocs (1.0 - 575.302) <46C7D508-D0C7-3728-B1C1-0FF3EA5CCFF3> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs
0x7fff4dc28000 - 0x7fff4dc31ffb com.apple.CommonAuth (4.0 - 2.0) <55CEF8E6-A659-3D68-BEE0-1236F36E494C> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff4dc45000 - 0x7fff4dc5affb com.apple.commonutilities (8.0 - 900) <2F945604-B4FA-3116-9AEE-0D216C283865> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
0x7fff4df02000 - 0x7fff4df64ff3 com.apple.AddressBook.ContactsFoundation (8.0 - ???) <93716128-0595-3CF6-8744-B5186D360F0E> /System/Library/PrivateFrameworks/ContactsFoundation.framework/Versions/A/ContactsFoundation
0x7fff4df65000 - 0x7fff4df88ff3 com.apple.contacts.ContactsPersistence (1.0 - ???) <B5F2F7C7-473F-3F0D-80E8-BBF3148047BF> /System/Library/PrivateFrameworks/ContactsPersistence.framework/Versions/A/ContactsPersistence
0x7fff4e0ca000 - 0x7fff4e4adfef com.apple.CoreAUC (274.0.0 - 274.0.0) <C78A44FB-53CD-324C-B363-9425B5269F7D> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
0x7fff4e4ae000 - 0x7fff4e4dcff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <C7A64576-B082-323A-AC02-E890C6DDF181> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
0x7fff4e4fc000 - 0x7fff4e51afff com.apple.CoreAnalytics.CoreAnalytics (1.0 - 1) <D0BF86C2-7D6F-3973-AC19-9969B6A4AC12> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
0x7fff4e572000 - 0x7fff4e5cdff3 com.apple.corebrightness (1.0 - 1) <BB3CA5C7-75AB-3B22-BB78-6F10935688AB> /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
0x7fff4e704000 - 0x7fff4e70dfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <E33CF2FB-50CF-3763-860C-CED9E5CF6B06> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
0x7fff4e907000 - 0x7fff4e918ff7 com.apple.CoreEmoji (1.0 - 69.19.9) <90ACD3F0-1542-3094-A1F6-FF2F508A8561> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
0x7fff4eac0000 - 0x7fff4ebaffff com.apple.CoreHandwriting (161 - 1.2) <7E01C62F-F8C2-3F21-B1E2-A048CF6FFC16> /System/Library/PrivateFrameworks/CoreHandwriting.framework/Versions/A/CoreHandwriting
0x7fff4ed81000 - 0x7fff4ed97ffb com.apple.CoreMediaAuthoring (2.2 - 958) <4C69C07C-73D1-3E5A-A8E1-3C5856A65D9A> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring
0x7fff4eec1000 - 0x7fff4ef27ff7 com.apple.CoreNLP (1.0 - 130.15.22) <5191A681-5DF3-359A-B401-C29109EA420A> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
0x7fff4f093000 - 0x7fff4f11ffff com.apple.CorePDF (4.0 - 414) <D87D2FD6-871F-3EC6-BB19-9719A37E3B27> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF
0x7fff4f1d4000 - 0x7fff4f1dcff7 com.apple.CorePhoneNumbers (1.0 - 1) <01CAC5E2-B6B1-3444-8939-595A9301399C> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers
0x7fff4f358000 - 0x7fff4f389ff3 com.apple.CoreServicesInternal (358 - 358) <7DD35528-033B-3B59-AAF2-5BFAF449D915> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
0x7fff4f74f000 - 0x7fff4f7d3fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <CBA82F08-26CC-3FB4-9539-B0B55B35C5E1> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x7fff4f862000 - 0x7fff4f98dff7 com.apple.coreui (2.1 - 499.10) <50A90628-5400-3EBC-A1FE-87D68BC59377> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff4f98e000 - 0x7fff4fb2affb com.apple.CoreUtils (5.7.6 - 576.49) <60FF6102-EEBB-302E-8DE4-6DCBB689ACC8> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils
0x7fff4fb7e000 - 0x7fff4fbe1ff7 com.apple.framework.CoreWiFi (13.0 - 1370.8) <F8634D22-1AD4-36B0-848C-BA60CC88BDAE> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
0x7fff4fbe2000 - 0x7fff4fbf3ff7 com.apple.CrashReporterSupport (10.13 - 938.25) <AB842AE0-8594-3530-ABB7-30E583F82FC5> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
0x7fff4fc82000 - 0x7fff4fc91fff com.apple.framework.DFRFoundation (1.0 - 211.1) <201CCA68-44E4-3E09-8604-7D8833AC803B> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
0x7fff4fc92000 - 0x7fff4fc96fff com.apple.DSExternalDisplay (3.1 - 380) <6AC4F805-7AAF-31D3-B614-C78B61907EE3> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
0x7fff4fd17000 - 0x7fff4fd8cff3 com.apple.datadetectorscore (7.0 - 590.24) <2A591F27-0FEE-3CE1-B6C3-7A3B56C9D18D> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff4fdd8000 - 0x7fff4fe15ff7 com.apple.DebugSymbols (190 - 190) <F2269F7B-5FCC-3187-8F13-A15F2C9D21E5> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x7fff4fe16000 - 0x7fff4ff51fff com.apple.desktopservices (1.13.1 - ???) <420CC09F-7C18-3644-A024-DA8997FECA02> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x7fff5015d000 - 0x7fff50223fff com.apple.DiskManagement (12.1 - 1555) <14459C59-D53A-3C24-94CC-D60CD1749FDB> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement
0x7fff50224000 - 0x7fff50228ffb com.apple.DisplayServicesFW (3.1 - 380) <B1F53D09-C299-31AA-962E-9A132ABB03B3> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices
0x7fff502cd000 - 0x7fff502d0ff3 com.apple.EFILogin (2.0 - 2) <B25F3D52-70FC-3F71-8B77-E23D7514D8FF> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
0x7fff50a06000 - 0x7fff50ce8ff7 com.apple.vision.EspressoFramework (1.0 - 120) <606AFD0D-D2DF-335C-915D-87A862C46765> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso
0x7fff50e8c000 - 0x7fff512a7fff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <D642D5E1-C7C5-3EBF-9D0A-397BDE2A5723> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
0x7fff512d8000 - 0x7fff5135dff7 com.apple.FileProvider (125.130 - 125.130) <30851CFB-6179-3BFB-A93E-EC9B0C97F50F> /System/Library/PrivateFrameworks/FileProvider.framework/Versions/A/FileProvider
0x7fff54b5b000 - 0x7fff54b5cfff libmetal_timestamp.dylib (902.3.2) <E4C0B5C2-AFAE-3DAD-8638-9D972E13F27C> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib
0x7fff561fc000 - 0x7fff56201fff com.apple.GPUWrangler (3.30.14 - 3.30.14) <5D15F5B8-9D7B-356D-A224-A86CF809BFBF> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
0x7fff5658e000 - 0x7fff565b2ff3 com.apple.GenerationalStorage (2.0 - 285.101) <E4F747EB-7D8B-39ED-B72E-C323C201B6E1> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
0x7fff565cb000 - 0x7fff56fc4fff com.apple.GeoServices (1.0 - 1364.24.8.24.47) <7A0FB79F-E311-3805-A8E2-C5E0176736DA> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices
0x7fff57006000 - 0x7fff57015fff com.apple.GraphVisualizer (1.0 - 5) <C261C18C-C66F-39BA-A640-727434ADBEB7> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
0x7fff57162000 - 0x7fff571d6ffb com.apple.Heimdal (4.0 - 2.0) <05B753FE-8F65-3764-8E18-F31902064BA1> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff571d7000 - 0x7fff57205fff com.apple.HelpData (2.3 - 184.4) <37EC79E3-5D56-3733-856C-5DB46CC9453B> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7fff584c0000 - 0x7fff584c7ffb com.apple.IOAccelerator (404.8 - 404.8) <FB11472D-74D7-31D4-8DF6-9A668BB08D4F> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x7fff584cb000 - 0x7fff584e3fff com.apple.IOPresentment (1.0 - 42.6) <B3365E07-6FC3-3AAA-884D-D6EE7ACDAE16> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
0x7fff5888b000 - 0x7fff588b8ff7 com.apple.IconServices (379 - 379) <189807AC-4BB1-3C37-B6EC-D4F0B645902D> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
0x7fff589e1000 - 0x7fff589e5ffb com.apple.InternationalSupport (1.0 - 10.15.6) <ADB2A56E-5E99-312A-B3B0-E96B519E46B1> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport
0x7fff58a4f000 - 0x7fff58a5cffb com.apple.IntlPreferences (2.0 - 227.17.1) <17AE2DAE-0295-3133-B51F-DEC8FEC2F0F8> /System/Library/PrivateFrameworks/IntlPreferences.framework/Versions/A/IntlPreferences
0x7fff58b4a000 - 0x7fff58b5cff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <731EEEC5-1613-3725-B33C-B38BBD55FA96> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle
0x7fff58b77000 - 0x7fff58c52ff7 com.apple.LanguageModeling (1.0 - 159.15.15) <229A8E92-CCB6-3BC7-BCD3-B2309FA744B3> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
0x7fff58c53000 - 0x7fff58c8fff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <30D3EEF3-31E5-3DE8-8158-40627C358AF6> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
0x7fff58c96000 - 0x7fff58c9bfff com.apple.LinguisticData (1.0 - 238.24.1) <E155D8DF-8AC1-34B2-B143-BBD3408C8D19> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
0x7fff594b8000 - 0x7fff594bbfff com.apple.Mangrove (1.0 - 25) <FF682E43-73CE-3E36-B4A9-8E69B546C7A4> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove
0x7fff59542000 - 0x7fff59568ff3 com.apple.MarkupUI (1.0 - 232.3.30) <BC364ADF-8725-37AE-B946-D8BB6260C044> /System/Library/PrivateFrameworks/MarkupUI.framework/Versions/A/MarkupUI
0x7fff595d0000 - 0x7fff59603ff7 com.apple.MediaKit (16 - 906) <D9B33C2A-706E-3A7C-90D1-D78EA4EFF871> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x7fff5998a000 - 0x7fff599b2ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.56) <550876F2-D905-3D65-8FA6-3366D857437B> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities
0x7fff599b3000 - 0x7fff59a3dfff com.apple.gpusw.MetalTools (1.0 - 1) <09394594-A80D-3D8B-99E8-E71693909FA1> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
0x7fff59a52000 - 0x7fff59a6bffb com.apple.MobileAssets (1.0 - 437.250.3) <95ACB386-7899-3661-BE5B-7E3133FE971B> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset
0x7fff59be9000 - 0x7fff59c03fff com.apple.MobileKeyBag (2.0 - 1.0) <A38DB402-7EB2-3D81-A9FA-4C95748FFC2D> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag
0x7fff59c15000 - 0x7fff59c8afff com.apple.Montreal (1.0 - 42.15.9) <84278E37-0BA4-32D2-BAA4-49D84831588D> /System/Library/PrivateFrameworks/Montreal.framework/Versions/A/Montreal
0x7fff59c8b000 - 0x7fff59cb5ffb com.apple.MultitouchSupport.framework (2440.7 - 2440.7) <FAE48832-BB56-35C9-B433-F0D03EF50FCD> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff59ef1000 - 0x7fff59efbfff com.apple.NetAuth (6.2 - 6.2) <216DF366-7A3E-39E7-896C-7CDFD2A9BD3D> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff5a75c000 - 0x7fff5a7adff3 com.apple.OTSVG (1.0 - ???) <AF7D1285-08EE-3EEB-B8B7-6C358768473D> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG
0x7fff5b76d000 - 0x7fff5b860fff com.apple.PencilKit (1.0 - 1) <EB69AD79-DB9B-30D8-9207-BDDBB34900D7> /System/Library/PrivateFrameworks/PencilKit.framework/Versions/A/PencilKit
0x7fff5b861000 - 0x7fff5b870ff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <DAF9D379-F0E9-3929-829E-7B2FAFC7DC64> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
0x7fff5ba97000 - 0x7fff5ba97fff com.apple.PhoneNumbers (1.0 - 1) <D7C25147-3D38-3DA4-988B-C5477EA685A0> /System/Library/PrivateFrameworks/PhoneNumbers.framework/Versions/A/PhoneNumbers
0x7fff5d29f000 - 0x7fff5d2b0ffb com.apple.PowerLog (1.0 - 1) <10082A63-C0F0-3A88-B47A-1DC14108B57E> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog
0x7fff5d508000 - 0x7fff5d517fff com.apple.printingprivate.framework.PrintingPrivate (14.0 - 180.3) <52B608D7-4347-39A3-A7C1-5F14C8467EE2> /System/Library/PrivateFrameworks/PrintingPrivate.framework/Versions/A/PrintingPrivate
0x7fff5d6ab000 - 0x7fff5d6ffff7 com.apple.ProtectedCloudStorage (1.0 - 1) <7EEE25C8-2680-32E1-9B4F-F76684E92BE1> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage
0x7fff5d700000 - 0x7fff5d71eff7 com.apple.ProtocolBuffer (1 - 263) <51266D17-7AB5-3741-BF76-FA7F3FE56D12> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
0x7fff5d89c000 - 0x7fff5d89fff3 com.apple.QuickLookNonBaseSystem (1.0 - 1) <8C160EB3-161F-3F35-9D10-C06403BC31F1> /System/Library/PrivateFrameworks/QuickLookNonBaseSystem.framework/Versions/A/QuickLookNonBaseSystem
0x7fff5d8a0000 - 0x7fff5d8b5ff3 com.apple.QuickLookThumbnailing (1.0 - 1) <2A637CF5-E50A-3016-88CB-F03F32662886> /System/Library/PrivateFrameworks/QuickLookThumbnailing.framework/Versions/A/QuickLookThumbnailing
0x7fff5d8b6000 - 0x7fff5d906fff com.apple.ROCKit (27.6 - 27.6) <A8116AFC-F78F-32BF-A66C-ED3B5E9FF1D9> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit
0x7fff5da35000 - 0x7fff5da40fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 1336.251.2) <937941A3-23E9-3DB4-B934-C8002EF1179D> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery
0x7fff5da53000 - 0x7fff5da75fff com.apple.RemoteViewServices (2.0 - 128) <E22D4E74-7B87-31ED-86D2-D63258D1B792> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
0x7fff5da76000 - 0x7fff5da89ff3 com.apple.xpc.RemoteXPC (1.0 - 1336.251.2) <45A2C9B1-787E-3BF8-AFB8-375822FC6AF4> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC
0x7fff5f274000 - 0x7fff5f38efff com.apple.Sharing (1288.25 - 1288.25) <E4C2CE6D-757D-322F-AA8D-52A0993E02D6> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
0x7fff5f38f000 - 0x7fff5f3aeffb com.apple.shortcut (2.16 - 101) <087A0F80-1818-3D93-A9D5-942F94C26D8E> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x7fff60136000 - 0x7fff603dffff com.apple.SkyLight (1.600.0 - 340.9) <A962D996-6561-3993-B470-EFD6EE4BFA9C> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
0x7fff60b81000 - 0x7fff60b8dfff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <08222836-F14B-3B9D-BCB9-3167505438E4> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
0x7fff60c3f000 - 0x7fff60ea2ff3 com.apple.spotlight.index (10.7.0 - 1191.56) <79DE4A4A-C589-3169-B75D-F0B2B01C2C72> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex
0x7fff6122c000 - 0x7fff61268ff3 com.apple.StreamingZip (1.0 - 1) <E25346D8-9C5E-3AD3-9F77-44F8A4449234> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip
0x7fff612de000 - 0x7fff61369fc7 com.apple.Symbolication (10.2 - 64490.38.1) <15A1DF22-3EE2-359A-8F94-B27F89F35ECE> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
0x7fff6136a000 - 0x7fff61372ffb com.apple.SymptomDiagnosticReporter (1.0 - 820.257.1) <F0DED0D7-EAEF-3607-A8D8-BCA60DAC1CBD> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter
0x7fff61840000 - 0x7fff6184bff7 com.apple.private.SystemPolicy (1.0 - 1) <7E43EFF3-41AC-3AF2-A2FD-1AE013FF32E6> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
0x7fff61850000 - 0x7fff6185cffb com.apple.TCC (1.0 - 1) <95D4B7DF-78F3-3948-AA63-6425AF2C00CD> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff61ac2000 - 0x7fff61b8aff3 com.apple.TextureIO (3.8.4 - 3.8.1) <29383676-6133-3EB4-8CAC-5A6F25FE2F4D> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
0x7fff61be7000 - 0x7fff61c02fff com.apple.ToneKit (1.0 - 1) <07E8BA17-0A78-3305-B247-728687222975> /System/Library/PrivateFrameworks/ToneKit.framework/Versions/A/ToneKit
0x7fff61c03000 - 0x7fff61c28ff7 com.apple.ToneLibrary (1.0 - 1) <722092E6-C0E6-3AD4-A870-5C4E1CF2B388> /System/Library/PrivateFrameworks/ToneLibrary.framework/Versions/A/ToneLibrary
0x7fff61c47000 - 0x7fff61dfdff7 com.apple.UIFoundation (1.0 - 551) <5359E30D-AF76-3013-8B50-0A93DB97BB8F> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7fff62a79000 - 0x7fff62b52fff com.apple.ViewBridge (401.1 - 401.1) <4DAA256D-F443-3484-AB8B-BFD939790E1D> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge
0x7fff63329000 - 0x7fff6332cfff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.46.2) <7763C799-CE25-302D-96D7-2A4DD9BEEE9A> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap
0x7fff6372d000 - 0x7fff6372fffb com.apple.loginsupport (1.0 - 1) <F9C63D6B-5191-3D95-B5C7-B998FA148AA6> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
0x7fff63730000 - 0x7fff63745fff com.apple.login (3.0 - 3.0) <D1B9E21E-87D9-341D-A23E-307908A1BEB6> /System/Library/PrivateFrameworks/login.framework/Versions/A/login
0x7fff6377c000 - 0x7fff637adffb com.apple.contacts.vCard (1.0 - ???) <4A802015-F485-3B44-8770-DB31714355A0> /System/Library/PrivateFrameworks/vCard.framework/Versions/A/vCard
0x7fff639f6000 - 0x7fff63a2afff libCRFSuite.dylib (41.15.4) <43D02A64-2A7B-3825-8097-A6747AF914EE> /usr/lib/libCRFSuite.dylib
0x7fff63a2d000 - 0x7fff63a37ff7 libChineseTokenizer.dylib (28.15.3) <BE41A678-907E-3031-B2BA-ECDB81282499> /usr/lib/libChineseTokenizer.dylib
0x7fff63a38000 - 0x7fff63ac1fff libCoreStorage.dylib (546.50.1) <1950AEDB-8782-39C9-9477-CB43ECB0EB38> /usr/lib/libCoreStorage.dylib
0x7fff63ac5000 - 0x7fff63ac6ffb libDiagnosticMessagesClient.dylib (107) <B5675E8C-2F34-3E0A-B7E8-6F2373589038> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff63afd000 - 0x7fff63d54ffb libFosl_dynamic.dylib (18.3.2) <C46C13F6-2799-39A0-BB32-126C2259194A> /usr/lib/libFosl_dynamic.dylib
0x7fff63d74000 - 0x7fff63d7bfff libMatch.1.dylib (31.200.1) <895AE4DA-69EF-30E8-82B3-1229B90C3E3D> /usr/lib/libMatch.1.dylib
0x7fff63da5000 - 0x7fff63dc3fff libMobileGestalt.dylib (645.250.13) <6B4E26AD-D712-360B-904C-877C24D89393> /usr/lib/libMobileGestalt.dylib
0x7fff63dc4000 - 0x7fff63dc4fff libOpenScriptingUtil.dylib (179.1) <5C6CFA80-CBCD-35EB-A69C-72C3B2E8FF50> /usr/lib/libOpenScriptingUtil.dylib
0x7fff63f04000 - 0x7fff63f05ffb libSystem.B.dylib (1252.250.1) <72841192-B0C9-36A0-8E55-ED651EADEF08> /usr/lib/libSystem.B.dylib
0x7fff63f81000 - 0x7fff63f82fff libThaiTokenizer.dylib (2.15.1) <3D80A800-D49A-305E-9DF0-E6FB11D4FD65> /usr/lib/libThaiTokenizer.dylib
0x7fff63f94000 - 0x7fff63faaffb libapple_nghttp2.dylib (1.24.1) <96F6DF29-D31C-3097-9C3E-63B1D62D756C> /usr/lib/libapple_nghttp2.dylib
0x7fff63fab000 - 0x7fff63fd4ffb libarchive.2.dylib (54.250.1) <D6370CDB-920D-37A3-A9C0-6C1FC95F2F99> /usr/lib/libarchive.2.dylib
0x7fff63fd5000 - 0x7fff64054fff libate.dylib (1.13.8) <D4150381-557F-3E9D-9119-ED4F2A8878A1> /usr/lib/libate.dylib
0x7fff64058000 - 0x7fff64058ff3 libauto.dylib (187) <4E260A46-13BB-3A8F-A037-D89748837B2A> /usr/lib/libauto.dylib
0x7fff64128000 - 0x7fff64138ffb libbsm.0.dylib (39.200.18) <CF0C09D6-FCED-3B48-A617-768A0B5B9DEB> /usr/lib/libbsm.0.dylib
0x7fff64139000 - 0x7fff64146fff libbz2.1.0.dylib (38.200.3) <62019AC3-20C9-3DDC-9C83-189C1F258073> /usr/lib/libbz2.1.0.dylib
0x7fff64147000 - 0x7fff6419aff7 libc++.1.dylib (400.9.4) <446DAE5E-4E97-3E4B-B2A3-AC0A74C0E453> /usr/lib/libc++.1.dylib
0x7fff6419b000 - 0x7fff641b0ff7 libc++abi.dylib (400.17) <A2D1FDAD-E10F-3E53-958F-CB6BC8485767> /usr/lib/libc++abi.dylib
0x7fff641b1000 - 0x7fff641b1ff3 libcharset.1.dylib (51.200.6) <0D3A5F4C-8800-33E3-AFE5-307E8BEE462C> /usr/lib/libcharset.1.dylib
0x7fff641b2000 - 0x7fff641c2ffb libcmph.dylib (6.15.1) <740A788E-FD92-36F3-B678-E7D510B1E2A1> /usr/lib/libcmph.dylib
0x7fff641c3000 - 0x7fff641dbffb libcompression.dylib (52.250.2) <9E125D43-CE4E-34F8-ACBA-C0835E5F8062> /usr/lib/libcompression.dylib
0x7fff64450000 - 0x7fff64466fff libcoretls.dylib (155.220.1) <FF7EA01E-9A26-36F9-A6FF-9665B501B536> /usr/lib/libcoretls.dylib
0x7fff64467000 - 0x7fff64468ff3 libcoretls_cfhelpers.dylib (155.220.1) <51572EB9-D154-348B-9934-3CA9444FAE5E> /usr/lib/libcoretls_cfhelpers.dylib
0x7fff64ac7000 - 0x7fff64ad2ff7 libcsfde.dylib (546.50.1) <D8EFD854-C2D1-3FF8-A910-A9E602A5BB79> /usr/lib/libcsfde.dylib
0x7fff64ada000 - 0x7fff64b30ff7 libcups.2.dylib (462.10) <83EF6851-07F6-35B4-AA80-690EF026C706> /usr/lib/libcups.2.dylib
0x7fff64c64000 - 0x7fff64c64fff libenergytrace.dylib (17.200.1) <F0A35E72-B772-359B-81AC-0C94B8A621CA> /usr/lib/libenergytrace.dylib
0x7fff64c65000 - 0x7fff64c7effb libexpat.1.dylib (16.1.1) <E614130E-8794-31EC-9434-837434962616> /usr/lib/libexpat.1.dylib
0x7fff64c96000 - 0x7fff64c9bff7 libgermantok.dylib (17.15.2) <A78E0BF5-0038-35C7-A8E7-05AEDF86D6D5> /usr/lib/libgermantok.dylib
0x7fff64c9c000 - 0x7fff64ca1ff7 libheimdal-asn1.dylib (520.250.1) <DE1C4650-FDFE-3A31-98AD-597B57C947E5> /usr/lib/libheimdal-asn1.dylib
0x7fff64ccc000 - 0x7fff64dbcfff libiconv.2.dylib (51.200.6) <E767B418-3531-3BB0-B58D-9ECB203407B7> /usr/lib/libiconv.2.dylib
0x7fff64dbd000 - 0x7fff6501dff3 libicucore.A.dylib (62123.0.1) <3936C798-1978-3C6C-9050-3BBD57CDA53E> /usr/lib/libicucore.A.dylib
0x7fff6506a000 - 0x7fff6506bfff liblangid.dylib (128.15.1) <1ED2EB78-3891-3DBA-8CB7-BA1A100CFC8F> /usr/lib/liblangid.dylib
0x7fff6506c000 - 0x7fff65084ff3 liblzma.5.dylib (10.200.3) <E6CA9433-904B-3804-82FF-B328E2047368> /usr/lib/liblzma.5.dylib
0x7fff6509c000 - 0x7fff65140ff7 libmecab.1.0.0.dylib (779.24.1) <0C57BF6E-A713-3AE8-8AD3-80F65D4CCC15> /usr/lib/libmecab.1.0.0.dylib
0x7fff65141000 - 0x7fff65345fff libmecabra.dylib (779.24.1) <A658B79D-4071-3EC1-9344-ADA438E43FB4> /usr/lib/libmecabra.dylib
0x7fff6551d000 - 0x7fff6586eff7 libnetwork.dylib (1229.250.15) <D8F52B1D-1AD9-3D33-8D59-2D631A3CBFEC> /usr/lib/libnetwork.dylib
0x7fff658fe000 - 0x7fff66083fdf libobjc.A.dylib (756.2) <4F86FC7C-496B-3E68-8A74-1EA2BA22FBCC> /usr/lib/libobjc.A.dylib
0x7fff66095000 - 0x7fff66099ffb libpam.2.dylib (22.200.1) <3AEB13DB-8DE2-3FD9-97D5-D9DB206E0693> /usr/lib/libpam.2.dylib
0x7fff6609c000 - 0x7fff660d1fff libpcap.A.dylib (79.250.1) <FA490ABF-6C15-336A-818F-0C14A8C090DB> /usr/lib/libpcap.A.dylib
0x7fff661ea000 - 0x7fff66202ffb libresolv.9.dylib (65.200.2) <DB6CA331-BB44-306D-8528-023EADE54BF7> /usr/lib/libresolv.9.dylib
0x7fff66204000 - 0x7fff6623fff3 libsandbox.1.dylib (851.250.12) <0A18B79B-4551-3D97-AC49-04E5373DC587> /usr/lib/libsandbox.1.dylib
0x7fff66240000 - 0x7fff66252ff7 libsasl2.2.dylib (211) <0B38826F-A082-38EF-ADE8-B23F98FBF44F> /usr/lib/libsasl2.2.dylib
0x7fff66253000 - 0x7fff66254ff7 libspindump.dylib (267.3) <47B91C83-6BE6-3B0B-8B42-83AE41160F3F> /usr/lib/libspindump.dylib
0x7fff66255000 - 0x7fff66432fe7 libsqlite3.dylib (274.22) <378D7B48-4661-3BA6-AC55-0B3A64F8C7E3> /usr/lib/libsqlite3.dylib
0x7fff666b2000 - 0x7fff666b5ff7 libutil.dylib (51.200.4) <336F9184-A739-3770-ACFA-4659DFEEACC4> /usr/lib/libutil.dylib
0x7fff666b6000 - 0x7fff666c3fff libxar.1.dylib (417.1) <D7AC80EE-D974-33E6-ACA7-87B398ACEDD7> /usr/lib/libxar.1.dylib
0x7fff666c8000 - 0x7fff667aaff3 libxml2.2.dylib (32.8) <064C2F49-C054-38F9-A6B2-032C4AC9738B> /usr/lib/libxml2.2.dylib
0x7fff667ab000 - 0x7fff667d3ff3 libxslt.1.dylib (16.1) <FB93A727-731D-313F-AF6B-4518FE830FFB> /usr/lib/libxslt.1.dylib
0x7fff667d4000 - 0x7fff667e6ff7 libz.1.dylib (70.200.4) <FDF169F3-F992-3E8E-B3F7-D4134FEBAE41> /usr/lib/libz.1.dylib
0x7fff66fc3000 - 0x7fff66fc7ff3 libcache.dylib (81) <9A8C27B0-49C9-337F-8BE2-37171ED2D8EE> /usr/lib/system/libcache.dylib
0x7fff66fc8000 - 0x7fff66fd2ff3 libcommonCrypto.dylib (60118.250.2) <17C4F395-9FF0-331F-8167-5E85AA3588E9> /usr/lib/system/libcommonCrypto.dylib
0x7fff66fd3000 - 0x7fff66fdaff7 libcompiler_rt.dylib (63.4) <8CB2B2B6-2C55-3733-9842-0E037AE3F46A> /usr/lib/system/libcompiler_rt.dylib
0x7fff66fdb000 - 0x7fff66fe4ff7 libcopyfile.dylib (146.250.1) <24905E41-9E2F-3DD1-A255-5A17F9FCDAD7> /usr/lib/system/libcopyfile.dylib
0x7fff66fe5000 - 0x7fff67069fc7 libcorecrypto.dylib (602.250.23) <3A6CBD41-AFFE-3E06-B1EC-3E95BC79BAC5> /usr/lib/system/libcorecrypto.dylib
0x7fff670f0000 - 0x7fff67129ff7 libdispatch.dylib (1008.250.7) <50235FCE-B399-3319-90DC-88F530D4FC5C> /usr/lib/system/libdispatch.dylib
0x7fff6712a000 - 0x7fff67156ff7 libdyld.dylib (655.1.1) <54C6B494-4A3D-3EEC-B083-636A76AAD649> /usr/lib/system/libdyld.dylib
0x7fff67157000 - 0x7fff67157ffb libkeymgr.dylib (30) <BEA04E04-FCF1-3A70-810F-08D0FF54CA36> /usr/lib/system/libkeymgr.dylib
0x7fff67158000 - 0x7fff67164ff3 libkxld.dylib (4903.251.3) <649F5829-6AA8-32EE-9A33-B1244378C319> /usr/lib/system/libkxld.dylib
0x7fff67165000 - 0x7fff67165ff7 liblaunch.dylib (1336.251.2) <30E6424E-4640-3DBA-9B64-D5F725263C6E> /usr/lib/system/liblaunch.dylib
0x7fff67166000 - 0x7fff6716bfff libmacho.dylib (927.0.2) <D8515A20-ED7B-3B13-9ADA-4BD7E19E38C4> /usr/lib/system/libmacho.dylib
0x7fff6716c000 - 0x7fff6716effb libquarantine.dylib (86.220.1) <8A9BF971-DB7D-311A-B131-6C5025E82F8F> /usr/lib/system/libquarantine.dylib
0x7fff6716f000 - 0x7fff67170ff7 libremovefile.dylib (45.200.2) <950036B7-B91E-3B5D-853C-8C551E5B6A32> /usr/lib/system/libremovefile.dylib
0x7fff67171000 - 0x7fff67188ff3 libsystem_asl.dylib (356.200.4) <16F632AD-FADA-3DE9-85E8-EBC7D619A1DA> /usr/lib/system/libsystem_asl.dylib
0x7fff67189000 - 0x7fff67189ff7 libsystem_blocks.dylib (73) <0CD6861B-EC5F-3345-9C24-B21EEB85E44F> /usr/lib/system/libsystem_blocks.dylib
0x7fff6718a000 - 0x7fff67211fff libsystem_c.dylib (1272.250.1) <F3AA9047-EEDD-3D80-8CC1-023FB312EC8B> /usr/lib/system/libsystem_c.dylib
0x7fff67212000 - 0x7fff67215ffb libsystem_configuration.dylib (963.250.1) <02C7A973-014A-31D7-B7D2-247D384CB0D2> /usr/lib/system/libsystem_configuration.dylib
0x7fff67216000 - 0x7fff67219ff7 libsystem_coreservices.dylib (66) <4CF1C89B-FA6C-3DF3-B1F8-79F549849534> /usr/lib/system/libsystem_coreservices.dylib
0x7fff6721a000 - 0x7fff67220fff libsystem_darwin.dylib (1272.250.1) <6983A268-20F4-3F98-A3F5-D63848933B02> /usr/lib/system/libsystem_darwin.dylib
0x7fff67221000 - 0x7fff67227ff7 libsystem_dnssd.dylib (878.250.4) <9FC5724C-DD03-3E14-A6E1-2DD009D79E0A> /usr/lib/system/libsystem_dnssd.dylib
0x7fff67228000 - 0x7fff67273ffb libsystem_info.dylib (517.200.9) <F617D3CF-5A4A-36D0-8CBB-4A7C7CDB67AF> /usr/lib/system/libsystem_info.dylib
0x7fff67274000 - 0x7fff6729cff7 libsystem_kernel.dylib (4903.251.3) <84EF0290-6CB5-36E5-A273-692A7E437B36> /usr/lib/system/libsystem_kernel.dylib
0x7fff6729d000 - 0x7fff672e8ff7 libsystem_m.dylib (3158.200.7) <33105665-CCC3-36D5-82C9-9B21730CB3DF> /usr/lib/system/libsystem_m.dylib
0x7fff672e9000 - 0x7fff6730dfff libsystem_malloc.dylib (166.251.2) <90DA09E3-1276-3FCF-8F5F-C9AA61AB9B6D> /usr/lib/system/libsystem_malloc.dylib
0x7fff6730e000 - 0x7fff67318ff7 libsystem_networkextension.dylib (767.250.2) <4575D797-B793-3D18-9E93-8696CF0B133B> /usr/lib/system/libsystem_networkextension.dylib
0x7fff67319000 - 0x7fff67320fff libsystem_notify.dylib (172.200.21) <679E9132-1A46-326E-9A11-D3FF9C86041C> /usr/lib/system/libsystem_notify.dylib
0x7fff67321000 - 0x7fff6732afef libsystem_platform.dylib (177.250.1) <3CC59141-5365-3848-94C3-D65E6FCA1E74> /usr/lib/system/libsystem_platform.dylib
0x7fff6732b000 - 0x7fff67335ff7 libsystem_pthread.dylib (330.250.2) <4344198A-A1A3-3C52-97B4-F168D56E9789> /usr/lib/system/libsystem_pthread.dylib
0x7fff67336000 - 0x7fff67339ff7 libsystem_sandbox.dylib (851.250.12) <66E91015-F62A-3365-BB81-AA88707E8F12> /usr/lib/system/libsystem_sandbox.dylib
0x7fff6733a000 - 0x7fff6733cff3 libsystem_secinit.dylib (30.220.1) <F054DCB0-68CE-35E7-8B8C-D648C42124EC> /usr/lib/system/libsystem_secinit.dylib
0x7fff6733d000 - 0x7fff67344ff3 libsystem_symptoms.dylib (820.257.1) <C8517F35-E9DA-3649-B07D-2B38349C6730> /usr/lib/system/libsystem_symptoms.dylib
0x7fff67345000 - 0x7fff6735afff libsystem_trace.dylib (906.250.5) <AE77ACC7-488F-3AE1-BB0C-1ACFC7E1CE77> /usr/lib/system/libsystem_trace.dylib
0x7fff6735c000 - 0x7fff67361ffb libunwind.dylib (35.4) <8F0BC197-B97C-3DDC-92B0-6A7D3CB72FD8> /usr/lib/system/libunwind.dylib
0x7fff67362000 - 0x7fff67391ff7 libxpc.dylib (1336.251.2) <49138829-09C8-355C-B558-97E070B84EC5> /usr/lib/system/libxpc.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 796398
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=556.7M resident=0K(0%) swapped_out_or_unallocated=556.7M(100%)
Writable regions: Total=303.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=303.3M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 384K 3
Activity Tracing 256K 1
CG backing stores 992K 2
CG image 140K 14
CoreAnimation 124K 9
CoreGraphics 8K 1
CoreImage 24K 2
CoreUI image data 2024K 20
CoreUI image file 352K 5
Dispatch continuations 8192K 1
Foundation 44K 3
IOKit 7940K 1
Image IO 64K 1
Kernel Alloc Once 8K 1
MALLOC 63.3M 45
MALLOC guard page 32K 8
Memory Tag 242 12K 1
Memory Tag 255 137.1M 44
PROTECTED_MEMORY 4K 1
STACK GUARD 56.1M 35
Stack 219.3M 35
VM_ALLOCATE 1292K 17
__DATA 42.9M 340
__FONT_DATA 4K 1
__LINKEDIT 224.1M 11
__TEXT 332.6M 343
__UNICODE 564K 1
mapped file 102.0M 36
shared memory 2792K 10
=========== ======= =======
TOTAL 1.2G 992
Model: MacBookPro12,1, BootROM 182.0.0.0.0, 2 processors, Intel Core i5, 2.7 GHz, 8 GB, SMC 2.28f7
Graphics: kHW_IntelIris6100Item, Intel Iris Graphics 6100, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54414C41522D4E5544
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54414C41522D4E5544
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.11f4, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB 3.0 Bus
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1
</details>
I would guess this is a regression from #18804 (#17400)?
|
https://github.com/electron/electron/issues/19539
|
https://github.com/electron/electron/pull/19601
|
40d9f828d4ce90244ccff35ef16885d915153a87
|
0bb227f8a43aaa5c0b3eafb3e051a07f6d82ca5f
| 2019-07-31T06:53:59Z |
c++
| 2019-08-05T13:19:01Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,522 |
["shell/browser/api/atom_api_app.cc"]
|
app.dock.bounce no longer has a default bounce type
|
Hi all,
I just upgraded to `6.0` and `TypeError: Insufficient number of arguments.`
|
https://github.com/electron/electron/issues/19522
|
https://github.com/electron/electron/pull/19523
|
d6605193a1e0355eb053cd15c55c7c20b5c4bb8c
|
51ce3e5a8349af924170eaab6d3996387a0a473e
| 2019-07-30T02:10:26Z |
c++
| 2019-07-31T15:20:45Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,481 |
["shell/browser/native_window_views_win.cc", "shell/browser/ui/views/root_view.cc", "shell/browser/ui/views/root_view.h"]
|
Frameless window does not enter fullscreen correctly from maximized
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0-beta.15
* **Operating System:**
* Windows 10 (1903)
* **Last Known Working Electron version:**
* 5.0.8
### Expected Behaviour
When a frameless window is maximized, and then enters full screen from that state, it should fill the entire screen with no border.
### Actual Behaviour
If a frameless window enters fullscreen from a maximized state, a ~10px white border appears all around the screen.
(Hard to show in a screenshot on a white page…)
### To Reproduce
Fiddle gist: https://gist.github.com/caesar/12c97746e9d8b0e9bd2ee7e4958c63ad
### Screenshots
It's hard to see the issue here because the border is white and so is the background of this page… but if you look carefully, the second time I the window enters fullscreen (when it does it from maximized), a white border appears.
|
https://github.com/electron/electron/issues/19481
|
https://github.com/electron/electron/pull/19883
|
080fdb3817318afbf627feda919a6753997a6d74
|
f6c523db13b5d015d3fdf241d3ee882847fa5979
| 2019-07-26T22:32:20Z |
c++
| 2019-08-26T01:03:57Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,475 |
["build/dump_syms.py"]
|
bug: breakpad symbols appear to be broken on Windows
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 5.0.7
* **Operating System:** All
* **Last Known Working Electron version:** 3.x.y
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
Breakpad symbols can be used to symbolicate crashes.
### Actual Behavior
Crash information on Windows is barely useful.
Here are first lines of symbolicated crashes on different platforms from [App Center](https://appcenter.ms).
#### Linux 🎉
_Electron 3_
```
skypeforlinux + 0x1bf0
```
_Electron 5.0.7_
```
skypeforlinux!(anonymous namespace)::AtlasOp::~AtlasOp() [GrCCPerFlushResources.cpp : 29 + 0x0]
```
#### Mac 👍 😞
_Electron 3_
```
Electron Framework!atom::AtomBindings::Crash()
```
_Electron 5.0.7_
```
Electron Framework!<name omitted> [atom_bindings.cc : 201 + 0x0]
```
#### Windows 😢
_Electron 3_
```
0 Skype.exe!base::FilePath::Append(base::BasicStringPiece<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> > >) [file_path.cc : 489 + 0x0]
```
_Electron 5.0.7_
```
0 Skype.exe + 0x7c20
```
### To Reproduce
Set up a crash reporter and run `process.crash()`.
### Additional Information
Probably related to #19157, /cc @nornagon.
|
https://github.com/electron/electron/issues/19475
|
https://github.com/electron/electron/pull/19483
|
0732da1b4aa913a3e372f4acce6a25bbfcaa7dd2
|
2983701c75a68eff490f309d44e4ad9eb8af4a1b
| 2019-07-26T12:01:22Z |
c++
| 2019-07-29T13:41:58Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,474 |
["patches/chromium/printing.patch", "shell/browser/api/atom_api_web_contents.cc"]
|
Silent printing not working in combination with deviceName (in v5.0.7 +)
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
* #17260 Not relevant: addresses the same issue, but for a version before the pull request that supposedly fixed silent printing. is already closed.
* #17077 Not relevant: addresses the same issue, but for an older version before pull request #19038 that should fix silent printing.
* #18123 Not relevant: doesn't address the same issue. Is already closed
* #17523 A list of issues related to printing.
### Issue Details
* **Electron Version:**
* 5.0.7 and 6.0.0-beta.15
* **Operating System:**
* MacOS Mojave v10.14.4
* **Last Known Working Electron version:**
* 3.1.11
### Expected Behaviors
According to the pull request #19038 which was merged in v.5.0.7, silent printing should work.
# | Code | Expected Behavior
------ | ----- | -------------------
1 | `webContents.print()` | Opens the print preview
2 | `webContents.print({ silent: true })` | Prints silently to default printer
3 | `webContents.print({ silent: true, printBackground: true })` | Prints silently with background to default printer
4 | `webContents.print({ silent: true, deviceName: 'Canon_MF633C_635C' })` | Prints silently to my Canon printer
5 | `webContents.print({ silent: true, deviceName: printBackground: true, deviceName: 'Canon_MF633C_635C' })` | Prints silently with background to my Canon printer
Original documentation of WebContents.print() can be found [here](https://electronjs.org/docs/api/web-contents#contentsprintoptions-callback).
### Actual Behaviors
# | Actual Behavior
------ | ---------------
1 | :white_check_mark: As expected
2 | :white_check_mark: As expected
3 | :white_check_mark: As expected
4 | :x: Nothing will happen, callback is never called
5 | :x: Nothing will happen, callback is never called
Unfortunately when providing a deviceName, nothing is send to the printer and the callback will never be called (see image of terminal logs below).
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->
1. Clone this fork: https://github.com/ibra038/electron-quick-start
2. Run `yarn install` and `yarn start`
3. Follow the steps on your screen
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Additional Information
For other developers that need to print silently to a predefined printer, the last known version I found to work is v3.1.11.
|
https://github.com/electron/electron/issues/19474
|
https://github.com/electron/electron/pull/19598
|
a8861e6a66127dcde5ef2db17ba280124b40dc0c
|
9c7a216814c3ec26dd7d9bbf2aedfbdb9373234b
| 2019-07-26T10:36:19Z |
c++
| 2019-08-07T14:47:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,455 |
["lib/browser/api/browser-window.js", "lib/browser/api/web-contents.js", "shell/browser/api/atom_api_event.cc", "shell/browser/api/event_emitter.cc", "shell/browser/api/event_emitter.h"]
|
browser-window-created and web-contents-created called with empty object as first parameter instead of event
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 6.0.0-beta.13
* **Operating System:** Windows 12
### Expected Behavior
The documentation for the App events `browser-window-created` and `web-contents-created` state that the first parameter is an `Event`. I therefore expect the first parameter to be an `Event`.
### Actual Behavior
The first parameter for both of these events is `undefined`. (The second parameter is a `BrowserWindow` and `WebContents`, respectively, as documented.)
|
https://github.com/electron/electron/issues/19455
|
https://github.com/electron/electron/pull/19465
|
33d1e87163ccc1cd934b8e587003365a96f90253
|
aaca9011aeca080743ec6c65fcd68373102f3e16
| 2019-07-25T14:53:58Z |
c++
| 2019-07-29T20:54:37Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,453 |
["shell/browser/native_window_views.cc", "spec-main/api-browser-window-spec.ts"]
|
BrowserWindow event always-on-top-changed called with negated bool parameter (isAlwaysOnTop)
|
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 6.0.0-beta.13
* **Operating System:** Windows 10
### Expected Behavior
When calling `browserWindow.setAlwaysOnTop(true)`, I expect the `always-on-top-changed` event to be called with the boolean `isAlwaysOnTop` parameter set to `true`, and vice versa.
### Actual Behavior
I experience the opposite of above: When calling `browserWindow.setAlwaysOnTop(true)`, my `always-on-top-changed` handler is called with `false`, and vice versa.
### To Reproduce
I don't have any JS code to share and I'm not a JS dev (I use F# and compile to JS with Fable). I think the issue should be easy to reproduce though.
|
https://github.com/electron/electron/issues/19453
|
https://github.com/electron/electron/pull/19463
|
4d23b9e03131512c388a3b126e7ddb82d0abbf81
|
504407c5df7c317e5647b3eb21d1cf3fa7b04309
| 2019-07-25T13:10:14Z |
c++
| 2019-07-26T22:53:31Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,425 |
["patches/node/.patches", "patches/node/fix_set_uptime_offset_in_correct_init_method.patch", "script/node-disabled-tests.json"]
|
process.uptime() returns unexpected result
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
v5.0.8
* **Operating System:**
Microsoft Windows 10 Pro (Version: 10.0.18362 Build 18362)
* **Last Known Working Electron version:**
unknown
### Expected Behavior
The same result node.js produces: the time the process is already running.
Output Node.js 12.7.0
```
node foo.js
2.1028718
4.1022395
6.1052112
8.1049451
```
### Actual Behavior
Electron returns some other numbers.
Output Electron 5.0.8
```
electron foo.js
585175.0756366
585177.0780253
585179.0767907
585181.0769859
```
### To Reproduce
foo.js
```
function uptime() {
console.log(process.uptime());
}
setTimeout(uptime, 2000);
setTimeout(uptime, 4000);
setTimeout(uptime, 6000);
setTimeout(uptime, 8000);
```
<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
### Additional Information
<!-- Add any other context about the problem here. -->
|
https://github.com/electron/electron/issues/19425
|
https://github.com/electron/electron/pull/19436
|
38c918ed5c56362106b8965fd51ca9c146a569f4
|
6e367dab9a7fbf0bff656cbade8b5031e33d1bf7
| 2019-07-24T11:37:03Z |
c++
| 2019-07-30T18:08:27Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,424 |
["shell/browser/api/atom_api_menu.cc"]
|
js garbage collector destroys active popup menus
|
Javascript's garbage collector destroys popup menus created by menu.popup from api Menu even when they are still active. It can lead to a crash when during destruction phase (when js object is already destroyed but c++ instance of class electron::api::Menu still lives) user makes any interaction with it, like changing focused element.
|
https://github.com/electron/electron/issues/19424
|
https://github.com/electron/electron/pull/19427
|
da2401ff399f1b23043f9c9529e8d2c541b44821
|
50cc54e50b58f7b2a39119be4a92c2d300f28ab8
| 2019-07-24T11:19:31Z |
c++
| 2019-08-06T21:55:00Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,423 |
["shell/browser/native_window_views_win.cc"]
|
Electron 6, maximize/restore not working correctly
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0-beta.15
* **Operating System:**
* Windows 10 64bit
* **Last Known Working Electron version:**
* 5.0.8
### Expected Behavior
The window restores its size to what it used to be
### Actual Behavior
The window is shown in the smallest size
### To Reproduce
1) Maximize Window
2) Minimize Window
3) Restore Window (click on the icon in the taskbar)
4) Unmaximize Window
### Screenshots
|
https://github.com/electron/electron/issues/19423
|
https://github.com/electron/electron/pull/19928
|
832c926712802913d7f48f84015d394d62281338
|
27ce6a9cd3445ce7c405fb3abebb472e7bc2bd0f
| 2019-07-24T09:24:27Z |
c++
| 2019-08-28T00:34:34Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,411 |
["shell/browser/api/atom_api_menu_mac.h", "shell/browser/api/atom_api_menu_mac.mm"]
|
closePopup() doesn't close the menu if called immediately after popup()
|
e.g.
```js
// in the main process
const w = new BrowserWindow({ show: false })
const menu = Menu.buildFromTemplate([
{ label: '1' },
{ label: '2' },
{ label: '3' }
])
menu.popup()
menu.closePopup()
```
It works if you call `closePopup()` in a `setTimeout` callback, though.
Expected behaviour:
menu appears and then disappears.
Actual behaviour:
menu appears and never goes away.
See [fiddle](https://gist.github.com/b76d0930011603e320f06f6ca0788317).
Happens on Electron 4, 5 and 6.
|
https://github.com/electron/electron/issues/19411
|
https://github.com/electron/electron/pull/20114
|
8a0a41b9efb7cba0ceed86505ff8d7d33cdbd75e
|
20e3c519dd27f3879d1ec69cb34aac33460eafe4
| 2019-07-23T23:35:27Z |
c++
| 2019-09-05T20:37:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,388 |
["shell/app/manifests.cc", "shell/app/manifests.h"]
|
crlf instead of lf in shell/app/manifests.cc/h
|
These two files:
shell/app/manifests.cc
shell/app/manifests.h
are commited with crlf and it makes some git operations (like cherry-pick/rebasing) impossible in some scenarios.
|
https://github.com/electron/electron/issues/19388
|
https://github.com/electron/electron/pull/19382
|
38507974d61c9f1e371d106d4b977363814cd9f2
|
2e3d757f4670b97383c6b3adb7699d9c8364754c
| 2019-07-23T15:38:22Z |
c++
| 2019-07-23T18:17:34Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,368 |
["lib/renderer/init.ts"]
|
Sending IPC messages to renderers interferes with node http module on windows
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0-beta.15
* **Operating System:**
* Windows 10 1903
* **Last Known Working Electron version:**
* 5.0.7
### Expected Behavior
Node's built-in should work all the time the app starts.
### Actual Behavior
I noticed when using NeDB in my Electron app in renderer process after the update to 6.0.0-beta.15, the databases just don't load (they load properly very rare). But when reloading my renderer process using `Ctrl + R` everything works fine. Also it's worth to mention that requests using `http` or `https` modules behave in the same way, they just sometimes don't work. The problem doesn't occur in Electron 5.0.7. The problem seems to be very random and for me it's hard to describe what causes it.
### To Reproduce
The best way to reproduce this is to build my [project](https://github.com/wexond/wexond). All instructions are in the README. Then try to add some bookmarks, close the app and restart it and see if they appear under the address bar. Also as I mentioned before, sometimes web requests doesn't work so you may not see the weather card. Then try to reload using `Ctrl + R` and you will see that everything works correctly.
|
https://github.com/electron/electron/issues/19368
|
https://github.com/electron/electron/pull/19727
|
28466a39d81e8adbade67ff150b7037be4993db2
|
49fe2604b38a52ff59ea7d3c142485db42898ba3
| 2019-07-22T17:49:04Z |
c++
| 2019-08-13T21:03:25Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,348 |
["shell/common/native_mate_converters/message_box_converter.cc"]
|
MessageBox `type` property not working on Windows
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** v7 nightly 20190615
* **Operating System:** Windows 10 (1809)
* **Last Known Working Electron version:** v7 nightly 20190613
### Expected Behavior
Icon is shown in message box according to the `type` property.
### Actual Behavior
Icon is not shown.
### To Reproduce
```
const { app, dialog } = require("electron")
app.on("ready", () => {
dialog.showMessageBox({
title: "Also, something with windows looks broken.",
type: "info"
})
})
```
<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
_before_
_after_
### Additional Information
I'm pretty sure this issue was introduced by https://github.com/electron/electron/pull/18732. Any ideas @codebytere? Probs the `icon` property is broken as well.
|
https://github.com/electron/electron/issues/19348
|
https://github.com/electron/electron/pull/19349
|
526f9d442d0786f854d7fc04a088cde18d76e46a
|
0490189531dab039cbcd33beba1f00dbcf215da3
| 2019-07-19T22:34:04Z |
c++
| 2019-07-22T15:19:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,321 |
["docs/api/menu-item.md", "lib/browser/api/menu-item-roles.js", "lib/browser/devtools.ts", "spec-main/api-menu-item-spec.ts", "spec/ts-smoke/electron/main.ts"]
|
typings for MenuItemConstructorOptions.roles are missing possible values
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
5.0.7
* **Operating System:**
macOS
### Expected Behavior
No typescript error when using for example `recentDocuments`-role for MenuItem
### Actual Behavior
Typescript error when using for example `recentDocuments`-role for MenuItem
### To Reproduce
Try to use `recentDocuments`-role on a MenuItem
### Additional Information
In the [menu-item.md](https://github.com/electron/electron/blob/master/docs/api/menu-item.md#roles) there are the possible roles only for macOS missing. This results in the following typescript declaration line: `role?: ('undo' | 'redo' | 'cut' | 'copy' | 'paste' | 'pasteandmatchstyle' | 'delete' | 'selectall' | 'reload' | 'forcereload' | 'toggledevtools' | 'resetzoom' | 'zoomin' | 'zoomout' | 'togglefullscreen' | 'window' | 'minimize' | 'close' | 'help' | 'about' | 'services' | 'hide' | 'hideothers' | 'unhide' | 'quit' | 'startspeaking' | 'stopspeaking' | 'close' | 'minimize' | 'zoom' | 'front' | 'appMenu' | 'fileMenu' | 'editMenu' | 'viewMenu' | 'windowMenu');`
I can still use the role I write `role: 'recentDocuments' as any`. I don't think this is how it should be.
|
https://github.com/electron/electron/issues/19321
|
https://github.com/electron/electron/pull/19329
|
bf66fe51f640439ec37faeebf41c8d43d58e8986
|
a5f87cee6b79e2ed38fbfe7b8af26a9de0649658
| 2019-07-18T08:53:54Z |
c++
| 2019-07-31T21:13:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,306 |
["shell/browser/native_window_mac.mm"]
|
Setting maximizable to false still shows the maximize icon on the frame
|
Here is my sample code to create the window:
```
let aboutWindow = new BrowserWindow({
width: 300,
height: 300,
backgroundColor: '#222',
show: true,
maximizable: false,
minimizable: false,
alwaysOnTop: true,
title: 'About'
})
```
And here is the screenshot of the output window on Mac(Mojave 10.14.4). Have't tested on other platform yet.
<img width="297" alt="Screen Shot 2019-07-17 at 9 36 57 PM" src="https://user-images.githubusercontent.com/6407135/61392526-a79f0980-a8dc-11e9-87f3-c722d41b32bc.png">
Electron version: 4.2.0
As you can see the maximize icon is still there on the frame even after setting maximizable to false while creating the window. I can click that icon and the window goes full screen.
|
https://github.com/electron/electron/issues/19306
|
https://github.com/electron/electron/pull/19314
|
e389fa75eace59e6e05d3b2275dbe4dd54dda594
|
42d4c579c39440247dd60e316b8b1fdd17fca594
| 2019-07-17T16:25:12Z |
c++
| 2019-07-19T23:17:59Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,256 |
["docs/api/web-contents.md", "shell/renderer/api/atom_api_web_frame.cc"]
|
`webContents.insertCSS` cssOrigin option
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->
Hi, I'm trying to integrate uBlock Origin extension into my app, using my own package [electron-extensions](https://github.com/sentialx/electron-extensions). But I can see uBlock Origin uses `chrome.tabs.insertCSS` with `cssOrigin` set to `user`. The property is important to block elements with `display: block !important`.
### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->
In `webContents.insertCSS` there should be a `details` object with at least `cssOrigin` property as it's described [here](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/insertCSS).
### Alternatives Considered
Unfortunately there are no alternatives. If there were any, I wouldn't create this issue.
|
https://github.com/electron/electron/issues/19256
|
https://github.com/electron/electron/pull/19268
|
e510816cf6bb4bac554041186533d170507488d9
|
3ee95cf0e86641758e536d7111105c3be3969f8e
| 2019-07-15T15:19:26Z |
c++
| 2019-07-17T21:34:05Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,201 |
["docs/development/testing.md"]
|
tests: Meiryo is not installed by default on Windows 10
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 --> 6.0.0-beta.12
* **Operating System:**
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 --> Windows 10 (1903).
* **Last Known Working Electron version:**
* <!-- (if applicable) e.g. 3.1.0 -->n/a
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
All font fallback tests pass.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
Font fall back tests fail with this in the log:
not ok 1191 font fallback should fall back to Japanese font for sans-serif Japanese script",
AssertionError: expected 'Yu Gothic' to equal 'Meiryo'",
at Context.<anonymous> (C:\\ci\\electron\\spec\\chromium-spec.js:1555:36)",
The Meiryo font does not appear to be installed on any of the Windows 10 machine that I have access to, and [Microsoft's typography page indicates that it's no longer shipped.](https://docs.microsoft.com/en-us/typography/font-list/meiryo)
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
Run the tests with `-g "font fallback"` or similar on a Windows 10 system.
<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
n/a
### Additional Information
<!-- Add any other context about the problem here. -->
n/a
|
https://github.com/electron/electron/issues/19201
|
https://github.com/electron/electron/pull/19308
|
d82e7af9be2625e4b19f126a6a8eefd0c5dbf550
|
9711fc895ed5991c795a9ce176dd8bf0748ae1e5
| 2019-07-10T17:44:37Z |
c++
| 2019-07-18T17:51:34Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,185 |
["docs/api/browser-window.md", "docs/styleguide.md"]
|
docs parser not generating types for BrowserWindow properties
|
e.g. `BrowserWindow.minimizable` is not present in `electron.d.ts`. Unsure if this is a docs parser issue or a type generator issue. cc @codebytere @MarshallOfSound
> [...] error TS2551: Property 'minimizable' does not exist on type 'BrowserWindow'. Did you mean 'isMinimizable'?
|
https://github.com/electron/electron/issues/19185
|
https://github.com/electron/electron/pull/19196
|
f6a29707b64bc2f7364f89096d187246bfc53765
|
50f49770483d1579ef47e63eca58498072681f84
| 2019-07-10T00:24:38Z |
c++
| 2019-07-15T17:15:32Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,161 |
["docs/api/web-frame.md", "shell/renderer/api/electron_api_web_frame.cc", "spec/api-web-frame-spec.js"]
|
promisifying WebFrame.executeJavaScript(InIsolatedWorld) is a breaking change without a workaround
|
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** v6.0.0-beta.12 x86
* **Operating System:** win7 x64 sp1
* **Last Known Working Electron version:** v5.0.6
The webFrame execute APIs have always been synchronous (which makes perfect sense, since this is in-process js evaluation), and under the hood they still are, despite now (#17312) returning promises. The callback used to deliver the result synchronously before the method returned.
There is nothing gained and only loss of flexibility when you wrap an actually sync api in a promise. It's trivial for the user to go from sync to promise (`Promise.(resolve|reject)`) but going from promise to sync is impossible.
So this change (for webFrame) is:
1. not an improvement
2. a breaking change for 6.0 (I have code that depends on the synchronous nature of these, which now can't even be fixed without having to become async)
### Expected Behavior
existing execute methods should remain sync, they could also be improved by returning the result, in addition to invoking the sync callback (which could be deprecated for later removal)
### Actual Behavior
no more sync callback, async promise instead
### To Reproduce
1. launch the following app in 5.0.6
**`index.js`**
```js
'use strict';
const {app, BrowserWindow} = require('electron'),
path = require('path');
let win;
app.on('ready', () => {
win = new BrowserWindow({
width: 1440,
height: 900,
useContentSize: true,
webPreferences: {
nodeIntegration: false,
contextIsolation: true,
preload: path.join(__dirname, 'preload.js'),
},
});
win.loadURL('about:blank');
win.webContents.openDevTools({mode: 'right'});
});
```
**`preload.js`**
```js
'use strict';
const {webFrame} = require('electron');
window.evalMainWorldSync = function(code) {
let result;
webFrame.executeJavaScript(code, false, res => result = res);
return result;
};
```
2. In the devtools console for the main world, enter: `foo = 1`
3. Switch console context to the Electron Isolated Context
4. eval `evalMainWorldSync('foo')`
5. it prints `1`
6. repeat 1-5 with electron 6.0.0-beta.12
7. it prints `undefined`
|
https://github.com/electron/electron/issues/19161
|
https://github.com/electron/electron/pull/21423
|
748a917ffdc238782ab427b442f785b575ddc16a
|
84126a4f23e0ce0c4596ec9a66c60e54e46017a0
| 2019-07-08T22:50:41Z |
c++
| 2020-03-03T00:11:40Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,160 |
["shell/browser/browser_mac.mm"]
|
crash in 'correctly sets and unsets the LoginItem'
|
cc @codebytere
```
4 ??? 0x00007f98dd127038 0x0 + 140294520729656
5 SharedFileList 0x00007fff36838f62 -[SFLLoginItemList _fetchItems] + 364
6 SharedFileList 0x00007fff36837942 __49-[SFLLoginItemList handleListChangeNotification:]_block_invoke + 103
```
https://circleci.com/gh/electron/electron/255344
|
https://github.com/electron/electron/issues/19160
|
https://github.com/electron/electron/pull/19179
|
50f49770483d1579ef47e63eca58498072681f84
|
4439249617f40a13d9283b729f050b29d8bbe40f
| 2019-07-08T21:18:32Z |
c++
| 2019-07-15T21:36:23Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,131 |
["shell/browser/api/atom_api_browser_window.cc"]
|
BrowserWindow.on('swipe') broken since Electron 3
|
### Issue Details
* **Electron Version:**
* 3.0.x, 4.0.x, 5.0.x, 6.0.x
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* 2.0.x
### Expected Behavior
`BrowserWindow.on('swipe')` fires when doing a 3-finger swipe gesture.
### Actual Behavior
`BrowserWindow.on('swipe')` does not fire.
|
https://github.com/electron/electron/issues/19131
|
https://github.com/electron/electron/pull/19319
|
42d4c579c39440247dd60e316b8b1fdd17fca594
|
1f2f1fb82d4f3c6c0564961e43a52219fb54284e
| 2019-07-06T07:06:54Z |
c++
| 2019-07-19T23:21:07Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,124 |
["shell/browser/ui/cocoa/atom_ns_window_delegate.mm", "spec/api-browser-window-spec.js"]
|
Can’t input using macOS “Emoji & Symbols” popover
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0-beta.12
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* 6.0.0-beta.11
### Expected Behavior
Selecting a character from the *Emoji & Symbols* popover should enter it to the focused input
### Actual Behavior
The popover closes and no character is input
### To Reproduce
1. `$ git clone https://github.com/javan/electron-quick-start.git -b emoji-and-symbols-bug`
1. `$ npm install`
1. `$ npm start || electron .`
1. Click the *Edit* → *Emoji & Symbols* menu or press <kbd>⌃</kbd><kbd>⌘</kbd><kbd>Space</kbd> to open the popover
1. Select any character from the popover
### Screenshots
<details><summary>v6.0.0-beta.12 👎</summary>
</details>
<details><summary>v6.0.0-beta.11 👍</summary>
</details>
### Additional Information
https://github.com/electron/electron/pull/18995 may be the culprit since it was introduce in beta.12 (cc: @erickzhao @codebytere)
|
https://github.com/electron/electron/issues/19124
|
https://github.com/electron/electron/pull/19213
|
35294891ae0dfc298643afea46b0374c8e4ce46c
|
9a42ddd2b847280fb5c6a32bef73bc55c658d8f2
| 2019-07-05T16:38:56Z |
c++
| 2019-07-12T08:46:35Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,122 |
["patches/chromium/printing.patch", "shell/browser/api/atom_api_web_contents.cc"]
|
webContents.print() doesn't work under Windows when 'deviceName' is provided
|
* Electron Version 6.0.0-beta.12
* Operating System Windows 10 64 bit
Expected Behavior
webContents.print() should send print a job to the specified printer
Actual behavior
Nothing happens. Callback gets called much latter, for example on program exit.
To Reproduce
let print_options = {
silent: true,
printBackground: true,
deviceName: barcode_device_name
}
print_window.webContents.print(print_options, (data) => {
console.log(`print result: ${data}`)
})
Related to #17260
|
https://github.com/electron/electron/issues/19122
|
https://github.com/electron/electron/pull/19598
|
a8861e6a66127dcde5ef2db17ba280124b40dc0c
|
9c7a216814c3ec26dd7d9bbf2aedfbdb9373234b
| 2019-07-05T06:04:13Z |
c++
| 2019-08-07T14:47:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,120 |
["filenames.gni", "patches/node/.patches", "patches/node/chore_re-add_compileandcall_this_should_be_added_as_a_helper_in.patch", "shell/common/api/atom_api_asar.cc", "shell/common/node_util.cc", "shell/common/node_util.h", "shell/renderer/atom_renderer_client.cc", "shell/renderer/atom_sandboxed_renderer_client.cc"]
|
Move CompileAndCall out of a node patch and into an electron helper
|
Post https://github.com/electron/electron/pull/18924 we shouldn't be patching `CompileAndCall` into our node fork, instead that method can quite easily live in our code as a helper.
|
https://github.com/electron/electron/issues/19120
|
https://github.com/electron/electron/pull/20675
|
5abce7ec081579b0334bc1c0b43d8618c861d0e5
|
db4d01c5172c1904bdfd472050b0e86283026c9d
| 2019-07-04T23:07:54Z |
c++
| 2019-10-23T16:26:32Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,108 |
["patches/chromium/printing.patch", "shell/browser/api/atom_api_web_contents.cc"]
|
Electron crashed after print
|
Version: v5.0.5, v5.0.6
JavaScript code: `document.querySelector('iframe').contentWindow.print()`
|
https://github.com/electron/electron/issues/19108
|
https://github.com/electron/electron/pull/19598
|
a8861e6a66127dcde5ef2db17ba280124b40dc0c
|
9c7a216814c3ec26dd7d9bbf2aedfbdb9373234b
| 2019-07-04T07:56:28Z |
c++
| 2019-08-07T14:47:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,097 |
["docs/api/system-preferences.md", "shell/browser/api/atom_api_system_preferences.h", "shell/browser/api/atom_api_system_preferences_mac.mm"]
|
systemPreferences.subscribeNotification should pass notification object to the callback
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
Today, it's not possible to receive contextual data from notifications originating from sandboxed macOS apps.
This is because Electron's `systemPreferences.subscribeNotification` accepts a callback that receives the `event` and `userInfo` properties from the macOS notification but **not** the `object` property. This is problematic because sandboxed apps cannot use the `userInfo` property, and can only transmit contextual data via the `object` of a notification. [Apple's docs](https://developer.apple.com/documentation/foundation/nsdistributednotificationcenter/1418360-postnotificationname?language=objc) clearly note this restriction.
As such, Electron cannot read contextual data sent from notifications that originate from sandboxed apps. So, for example, a Finder extension can notify an Electron app that *some* file has been right-clicked, but **cannot** indicate *which file* has been right-clicked.
### Proposed Solution
I'm proposing a change similar to #5582, which enhanced `systemPreferences.subscribeNotification` to pass the `userInfo` from the macOS notification to the callback. Here, we need to further enhance `systemPreferences.subscribeNotification` to also pass the `object` from the macOS notification.
To preserve backwards-compatibility, the callback should accept the new `object` argument as its third parameter. As such, the new version of the documentation [here](https://electronjs.org/docs/api/system-preferences#systempreferencessubscribenotificationevent-callback-macos) would read:
```diff
systemPreferences.subscribeNotification(event, callback) [macOS]
* event String
* callback Function
* event String
* userInfo Object
+ * object String
Returns Number - The ID of this subscription
Subscribes to native notifications of macOS, callback will be called with `callback(event, userInfo)` when the corresponding event happens. The `userInfo` is an Object that contains the user information dictionary sent along with the notification.
+The `object` is a String that contains additional data sent along with the notification.
```
### Alternatives Considered
I think the only reasonable alternative is to update the documentation [here](https://electronjs.org/docs/api/system-preferences#systempreferencessubscribenotificationevent-callback-macos) to note that sandbox apps cannot send any contextual data to Electron apps.
### Additional Information
There is a precedent for this kind of change in Electron. See #5543 which was fixed under #5582.
For macOS developers running into this issue, a possible workaround is to have your sandboxed app communicate with a non-sandboxed app and then relay notifications on to your Electron app. The sandbox to non-sandbox communication must use `object` to hold contextual data, and the non-sandbox to Electron communication must use `userInfo` to hold contextual data. (However, AFAIK, using a non-sandboxed app prevents publishing your app in the Mac App Store).
|
https://github.com/electron/electron/issues/19097
|
https://github.com/electron/electron/pull/19110
|
6d34314457fc92f76e57a5fa1f8e99dfb4d50aaf
|
79114ff40a7795f5d0229c85eb33db34a8c0e584
| 2019-07-03T16:29:40Z |
c++
| 2019-07-11T17:06:31Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,086 |
["spec/webview-spec.ts"]
|
re-enable test: <webview> tag DOM events emits resize events
|
disabled during a chromium roll here: https://github.com/electron/electron/pull/18648/commits/87902ad19cec639c1ef6dd6c7b8ab1803d77721d
|
https://github.com/electron/electron/issues/19086
|
https://github.com/electron/electron/pull/36026
|
e660fdf7760d9011c538f2a8e9b15b9710065dbc
|
76880be6d2cc466a44cf437bf34bf32f94a9f6ad
| 2019-07-02T20:55:54Z |
c++
| 2022-10-17T05:57:44Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,074 |
["lib/common/asar.js", "spec/asar-spec.js"]
|
Electron does not support withFileTypes in readdir inside asar
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->
Electrons patching of asar does not support withFileTypes (or encoding for that matter) options on readdir and readdirSync
### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->
[as you can see here](https://github.com/electron/electron/blob/cec61d010b7f421870d07f00d2aae25bb3b05b61/lib/common/asar.js#L605), electrons wrapping of readdir & readdir sync do not support the withFileTypes option, this option is majorly useful when reading over directories in node and requires a lot of unnecessary code work around this.
The Node that has the info neccessary for withTypes data is already being grabbed [here](https://github.com/electron/electron/blob/34c4c8d5088fa183f56baea28809de6f2a427e02/shell/common/asar/archive.cc#L245)
Im not versed enough in c++ to make a PR, but someone should be able to use that to get the info neccessary
|
https://github.com/electron/electron/issues/19074
|
https://github.com/electron/electron/pull/24062
|
a7599a0838d460609b19da84a0e867963345e9cc
|
66744ecb4d7ba5d9973d6b459b9cb0d2bf9af8b3
| 2019-07-02T05:29:40Z |
c++
| 2020-06-12T15:32:59Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,070 |
["lib/renderer/chrome-api.ts"]
|
chrome.runtime's port.postMessage incorrectly send UintArray
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 5.0.6
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 -->
* **Operating System:** mac OS 10.14.5
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 -->
* **Last Known Working Electron version:** Unknown
* <!-- (if applicable) e.g. 3.1.0 -->
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
`port.postMessage` correctly send UintArray
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
`port.postMessage` incorrectly appends unexpected number of `0` in buffer
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
- clone https://github.com/kwonoj/electron-crx-uintarray
- `npm install && npm start`
- navigate `localhost:8315` on chrome browser, open `chrome-extension://boo/_generated_background_page.html` to observe console message from devtools
<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
**from Electron@5**
**from chrome browser**
### Additional Information
https://github.com/bvaughn/react-devtools-experimental/issues/344 is caused by this, since every `postMessage` to UnitArray appends `0` to its buffer, operations relying on `0` as default value (unsupported) raises exception on devtools.
As attached above, this only happens in Electron (4 / 5 both so far tried) but not occurring on Chrome.
|
https://github.com/electron/electron/issues/19070
|
https://github.com/electron/electron/pull/19104
|
d0ece2bc93e30c829d5c0a000819af92600b5f91
|
6d5e49478269d38cb494edfb5df51541e19adaf5
| 2019-07-01T22:43:13Z |
c++
| 2019-07-15T10:05:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,056 |
["docs/api/web-contents.md", "docs/api/webview-tag.md", "lib/browser/api/web-contents.js", "shell/browser/api/electron_api_web_contents.cc", "spec-main/api-web-contents-spec.ts"]
|
Add an option to choose the paper format (size) on webContents.print()
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->
They is no way to choose the paper format (A4, A3, Letter, ...) when printing with `webContents.print()`.
### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->
Add something like the `pageSize` option which is available in [`webContents.printToPDF()`](https://electronjs.org/docs/api/web-contents#contentsprinttopdfoptions-callback).
|
https://github.com/electron/electron/issues/19056
|
https://github.com/electron/electron/pull/22014
|
385388dd6b9952029a5af2f7a4a371a3a7b9ff4d
|
928175bdfebbc5532966b16c9ae88a443dded4af
| 2019-07-01T07:47:57Z |
c++
| 2020-02-05T04:25:02Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,050 |
["docs/api/dialog.md"]
|
Please update the readme example to something that has the expected behavior on every os.
|
The first line in the Readme is a sample usage. One that only works as expected in OS X. One needs to go down a couple of paragraphs to realize that it's not supposed to work on their system, which in my case is on Archlinux. Please have some empathy for most of the population of the world who happen to not use a macbook like you guys. If you don't, at least move the warning up there so people can see it while trying out the example!
|
https://github.com/electron/electron/issues/19050
|
https://github.com/electron/electron/pull/19055
|
21d04ed3f42daf0c46281d91aa0b270da8045950
|
4e2990d3aac52c7b6da65eb5122956d12d70007f
| 2019-06-30T07:12:49Z |
c++
| 2019-07-01T23:53:07Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,020 |
["filenames.gni", "package.json", "spec-main/api-app-spec.ts", "yarn.lock"]
|
@types/node outdated
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 5.0.6
[docs](https://electronjs.org/releases/stable?version=5&page=2#5.0.0) say that Electron 5.x uses Node 12.0.0.
[package.json](https://github.com/electron/electron/blob/master/package.json#L15) uses @types/node 10.12.
|
https://github.com/electron/electron/issues/19020
|
https://github.com/electron/electron/pull/19025
|
5a3073128c47ce8a17db608e58093836cab24531
|
5154b954470e87842e3ff6f9c6785e2371059d60
| 2019-06-27T23:22:17Z |
c++
| 2019-07-01T18:25:45Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 19,008 |
["patches/chromium/printing.patch", "shell/browser/api/atom_api_web_contents.cc"]
|
Wrong behavior after canceling the printer dialog box
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 5.0.6
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* 4.2.5
### Expected Behavior
When I click on a **button** who uses the `print()` method
The print dialog opens
Then I click on "Cancel" button
I must be able to go to another page by clicking on a link
### Actual Behavior
When I click on a **button** who uses the `print()` method
The print dialog opens
Then I click on "Cancel" button
I can not click on another link, I have to quit the application and open it again
### To Reproduce
You can download the PIA 2.1.0 version at this URL https://github.com/LINCnil/pia-app/releases/tag/2.1.0 then:
* Create a new PIA
* Click on the **Preview** icon
* Click on the **Printer** icon (Wait for the printer dialog box)
* Click on the **Cancel** button
* Try to go on another page of the application
|
https://github.com/electron/electron/issues/19008
|
https://github.com/electron/electron/pull/21026
|
fe2ca6e6e7d7750f8775be25ce0b7efc538dbf62
|
6c2af8b421395cfc3a20e045218d7a1c739f08d5
| 2019-06-27T12:10:13Z |
c++
| 2019-11-08T18:01:50Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,980 |
["docs/api/web-contents.md", "patches/chromium/printing.patch"]
|
Better callback value for webContents.print()
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:** 5.0.5
* **Operating System:** macOS Mojave 10.14.5 / Windows too ?
* **Last Known Working Electron version:** not known
### Expected Behavior
When using `webContents.print()`, if the user click the **cancel button** on the print dialog (or on the **"PDF" button**) this should: return a callback value of "false" (error) or "true" (success), but with more details that only "true" or "false". Something like an error/success message that tell that the cancel button has been clicked..
This could be:
- `success` when the document is sent to the printer
- `cancelled` when the cancel button is clicked
- `pdf` / `other-action`? when the PDF button is clicked
- `failed` when an error occurs
### Actual Behavior
In my application, I only want to display a success notification to the user when the print process is successfully launched and an error message when they is an error. For now, false-positive notifications are display when :
- the cancel button is clicked on the print dialog (return is `false`), we do not know if it is an `error` or a `cancel` event and when an error occurs (return is `false` too), we do not know if it is an `error` or a `cancel` event.
- the "PDF" button (only on macOS?) is clicked (return is `true`) and we would know if this is a print `success` or something else to display a "successfully print" notification to the user.
Not tested, but Windows should have the same problem !
---
Perhaps linked with #15568 but more specific ?
@codebytere perhaps something that is linked with #17400
|
https://github.com/electron/electron/issues/18980
|
https://github.com/electron/electron/pull/19000
|
5154b954470e87842e3ff6f9c6785e2371059d60
|
21d04ed3f42daf0c46281d91aa0b270da8045950
| 2019-06-25T20:24:47Z |
c++
| 2019-07-01T21:03:19Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,938 |
["lib/common/init.ts", "spec/node-spec.js"]
|
timers Module Doesn't Work in Renderer
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 6.0.0-beta.8
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* N/A
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
Timeouts and intervals created with the `timers` module should work.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
Timers never fire.
### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
Reproduce repo: https://github.com/dsanders11/electron-quick-start/tree/timers-module-in-renderer
### Additional Information
<!-- Add any other context about the problem here. -->
Can be 'fixed' by calling `process.nextTick(() => {})` immediately after `timers.setTimeout` to trigger the UV event loop.
Root cause is the `wrapWithActivateUvLoop` wrapper which fixes this issue is not applied to the `timers` module itself, so any direct requires of the module will not use the wrapped version.
https://github.com/electron/electron/blob/792f6b246cbc385fd5db8b6ed4ad017c75d1643f/lib/common/init.ts#L16-L23
|
https://github.com/electron/electron/issues/18938
|
https://github.com/electron/electron/pull/18948
|
fb01c94511c42a72440e0503d1cb5499229fc7c0
|
764be844ec3aa649f47a798cd3b02fe8d36eeb4e
| 2019-06-22T10:48:17Z |
c++
| 2019-06-24T17:18:29Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,913 |
["shell/browser/api/atom_api_system_preferences_mac.mm"]
|
systemPreferences.isDarkMode doesn't return a value on macOS 10.15 Catalina
|
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 5.0.4
* **Operating System:**
* MacOS 10.15 Catalina (Developer Beta 2, 19A487l)
* **Last Known Working Electron version:**
* n/a
### Expected Behavior
When using the auto mode in macOS Catalina, the `systemPreferences.isDarkMode()` should reflect it based on the current mode set during that time of day. For instance, if Auto Mode is turned on and it's 2:00 PM, it should return that dark mode is false.
### Actual Behavior
This value doesn't return any value, meaning that the window retains its current state and thus doesn't comply with the rest of the system.
### To Reproduce
Noticed in https://github.com/hyperspacedev/hyperspace when running the desktop version. The code that makes it happen:
```js
// Watch for a change in macOS's dark mode and reload the window to apply changes
systemPreferences.subscribeNotification('AppleInterfaceThemeChangedNotification', () => {
if (mainWindow != null) {
mainWindow.setVibrancy(systemPreferences.isDarkMode()? "ultra-dark": "light");
mainWindow.webContents.reload();
}
})
```
```sh
$ git clone https://github.com/hyperspacedev/hyperspace -b beta6
$ npm install
$ npm start || npm run electrify
```
In System Preferences, change the Appearance mode from its current setting to Dark Mode. Wait for the change to take effect on the window, then change it to Auto Mode.
### Screenshots
<img width="1440" alt="image" src="https://user-images.githubusercontent.com/13445064/59887306-d8992680-9390-11e9-9f99-1774177267c3.png">
> Because `isDarkMode` doesn't return a boolean value, it remains in dark mode even though this isn't supposed to be the case in Auto Mode.
|
https://github.com/electron/electron/issues/18913
|
https://github.com/electron/electron/pull/18949
|
1cd7c21f389dca019d3a95ca1a5848b9e04b93d8
|
5686a0713e0444508f4c5142dd4399e3f1e2e206
| 2019-06-20T23:26:08Z |
c++
| 2019-06-24T17:17:38Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,901 |
["lib/renderer/init.ts", "lib/sandboxed_renderer/init.js"]
|
Show stack trace of errors with preload scripts using console.trace()
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
Per this question I asked on [Stack Overflow](https://stackoverflow.com/questions/56674450/retrieve-more-detailed-errors-from-electron-preload-script?noredirect=1#comment99926907_56674450), there is no way to inspect the stack trace / source of errors that occur when running preload scripts.
### Proposed Solution
Log these errors with [`console.trace`](https://developer.mozilla.org/en-US/docs/Web/API/Console/trace) along with `console.error`.
### Alternatives Considered
The other option is to re-throw the caught errors, however this would change functionality in an unexpected manner.
### Additional Information
Relevant code: https://github.com/electron/electron/blob/master/lib/renderer/init.ts#L199-L200
|
https://github.com/electron/electron/issues/18901
|
https://github.com/electron/electron/pull/18905
|
e6e94fc59de85c2333143ee7deaa09504c89de8d
|
079a173a72b8fda85f58772f3a13a287694ff90b
| 2019-06-20T13:08:40Z |
c++
| 2019-07-15T04:54:33Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,829 |
["filenames.gni", "shell/browser/api/electron_api_web_contents.cc", "shell/common/language_util.h", "shell/common/language_util_linux.cc", "shell/common/language_util_mac.mm", "shell/common/language_util_win.cc", "spec-main/chromium-spec.ts"]
|
Choosing appropriate fallback font list by system locale (especially on Windows)
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->
Under a Windows machine using English as a display language, Japanese kanji texts are rendered with Chinese font `SimSum`. This behavior matches with Chrome's one if the machine doesn't list Japanese as an alternative preferred locale, and HTML content language is set to `en-US`.
But if the machine lists Japanese as an alternative, Electron should render the text with Japanese fonts.
AFAIK, Chrome renders kanji texts (Han script) with Japanese fonts when the accept-language configuration includes Japanese, as reading Chromium (blink)'s [font_fallback_win.cc](https://cs.chromium.org/chromium/src/third_party/blink/renderer/platform/fonts/win/font_fallback_win.cc). This behavior is done by considering the system locales including secondary/alternative locales. Because of this, I don't encounter the same problem in Chrome.
Looks like Electron currently honors only primary system locale and content locale (HTML `lang`), but not secondary/alternative locales. Thus I think Electron's current behavior is not following Chrome's one.
As I'm not familiar with the Electron codebase, I'm still not sure why the current implementation doesn't make this problem on Mac. I'm listing Japanese as an alternative locale both on my Mac and Windows machine, but this problem happens only on Windows; as looking into font related codes in Chromium, I guess macOS' CoreText is doing good for choosing a font.
Related to #15486 #18197.
In real life, for Slack workspace/Discord servers where its primary language is Japanese, this problem forces people using English as a primary system language to read Japanese with an unmatched font, which is rendered ugly as a Japanese text. I don't think letting app developers using Electron to implement font configuration is happy, just for this problem. Electron should provide a good default to devs.
### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->
Get _all_ preferred locales from OS and set them to Chromium engine. I'm guessing https://github.com/electron/electron/pull/15532 fixes this problem.
### Additional Information
<!-- Add any other context about the problem here. -->
#### Japanese text shown on Slack app (Windows)
If I manually change `<html>` lang to `ja-JP`, kanji text starts rendered with Japanese font, Meiryo.
#### Windows Language Preference
#### Mac Language Preference
|
https://github.com/electron/electron/issues/18829
|
https://github.com/electron/electron/pull/23247
|
45d1ebe961ff21bc0640dfc44010a2f240b32acb
|
f176d2494f408162c0e53d925ddf7ff1eee08140
| 2019-06-16T13:51:09Z |
c++
| 2020-05-04T17:49:29Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,817 |
["DEPS"]
|
http2 code in Electron 5/6 suffers from a known memory leak
|
### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
### Problem Description
The current version of node (12.0.0) that is embedded in Electron suffers from a memory leak in the http2 code that makes it impossible to use grpc without fatal memory overflow errors.
See https://github.com/nodejs/node/issues/27416
The issues has been resolved in https://github.com/nodejs/node/pull/27914 and the fix is included in [node v12.4.0](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.4.0)
### Proposed Solution
Update node to 12.4.0
### Alternatives Considered
Without this upgrade, the only way to use grpc is to downgrade Electron to v4.
|
https://github.com/electron/electron/issues/18817
|
https://github.com/electron/electron/pull/18868
|
98bc0ae7eea791e2b9425b4909804c4f5dd407fc
|
ae49aa4a0318393330ba831bb425762a4405ba19
| 2019-06-15T11:31:30Z |
c++
| 2019-06-19T17:47:23Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,808 |
["shell/browser/api/event_emitter.cc", "shell/browser/ui/cocoa/atom_menu_controller.mm", "spec/api-menu-spec.js"]
|
bug: triggeredByAccelerator logic should not be tied to modifier key logic
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* v7.0.0-nightly.20190614
* **Operating System:**
* macOS 10.14.5
* **Last Known Working Electron version:**
* none
### Expected Behavior
* Using an accelerator without a modifier to activate a menu item (e.g. pressing key 'B') should result in `triggeredByAccelerator: true`.
* Clicking on a menu item with a menu item (e.g. Shift+Click) should result in `triggeredByAccelerator:false`.
### Actual Behavior
* Using an accelerator without a modifier to activate a menu item (e.g. pressing key 'B') results in `triggeredByAccelerator: false`.
* Clicking on a menu item while holding down a modifier key (e.g. Shift+Click) results in `triggeredByAccelerator:true`.
### To Reproduce
Electron Fiddle gist: https://gist.github.com/19163d031cf3e35bb7b163bd2c39305c
```
{
label: "Blade",
id: "blade",
accelerator: "B",
click(a, b, e) {
console.log(e);
}
}
```
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
### Additional Information
<!-- Add any other context about the problem here. -->
The property is currently derived from some event modifier flags (on Mac: `NSEvent.modifierFlags`). When using an accelerator with a modifier key, these flags are set and the property works as expected.
See:
```cpp
v8::Local<v8::Object> CreateEventFromFlags(v8::Isolate* isolate, int flags) {
mate::Dictionary obj = mate::Dictionary::CreateEmpty(isolate);
obj.Set("shiftKey", static_cast<bool>(flags & ui::EF_SHIFT_DOWN));
obj.Set("ctrlKey", static_cast<bool>(flags & ui::EF_CONTROL_DOWN));
obj.Set("altKey", static_cast<bool>(flags & ui::EF_ALT_DOWN));
obj.Set("metaKey", static_cast<bool>(flags & ui::EF_COMMAND_DOWN));
obj.Set("triggeredByAccelerator", static_cast<bool>(flags));
return obj.GetHandle();
}
```
https://github.com/electron/electron/blob/master/atom/browser/api/event_emitter.cc#L85
However, either triggering an accelerator without a modifier key (or clicking an accelerator with a modifier key) will give an invalid result. The `triggeredByAccelerator` logic should be decoupled from the modifier flags.
A better approach covering the edge case of not using a modifier is to use `NSEvent.type` to distinguish between a click or a keydown. Fix should go [here](https://github.com/electron/electron/blob/6f91af93433df4e9c0e7fb592e5b2dcb0b1c7888/atom/browser/ui/cocoa/atom_menu_controller.mm#L307).
cc @codebytere @erickzhao
|
https://github.com/electron/electron/issues/18808
|
https://github.com/electron/electron/pull/18865
|
6eed4a98ceb48cb048777d9515586f76aa276476
|
e03a40026a238eec5b2e5b8bc144a7596a4c1ba1
| 2019-06-14T22:43:28Z |
c++
| 2019-06-28T21:38:17Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,805 |
["docs/api/app.md", "shell/browser/api/atom_api_app.cc", "shell/browser/ui/cocoa/atom_bundle_mover.h", "shell/browser/ui/cocoa/atom_bundle_mover.mm"]
|
`app.moveToApplicationsFolder` fails if an homonymous app is already present and active
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 --> 5.0.3
* **Operating System:**
* <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 --> macOS 10.14
* **Last Known Working Electron version:**
* <!-- (if applicable) e.g. 3.1.0 --> n/a
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
`app.moveToApplicationsFolder` should throw when it fails, as the docs say.
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
It doesn't throw, in fact it even returns `true`.
### To Reproduce
- Have Foo v1 located in `/Applications/Foo.app`
- Open it
- Have Foo v2, still named `Foo.app`, located somewhere else
- Open it
- Use `app.moveToApplicationsFolder`.
- Instead of moving the app the currently open Foo v1 window will be focused, and `app.moveToApplicationsFolder` returns `true` instead of throwing.
|
https://github.com/electron/electron/issues/18805
|
https://github.com/electron/electron/pull/18916
|
0db6789210bcf30fee8536cfca5187a9ec56268b
|
f6a29707b64bc2f7364f89096d187246bfc53765
| 2019-06-14T20:10:06Z |
c++
| 2019-07-15T16:34:20Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,755 |
["atom/browser/api/atom_api_session.cc", "atom/browser/atom_permission_manager.cc", "atom/browser/atom_permission_manager.h", "docs/api/session.md"]
|
session.setPermissionRequestHandler for iframes has incorrect content URL
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* Tested with v4.1.4 and above
* **Operating System:**
* macOS 10.14.4
* **Last Known Working Electron version:**
* n/a
The **webContents getURL() does not return the contents URL for an iframe when a device permissions request is emitted**. Compared to a webview when a device permissions request is handled the webContent passed on the event has the correct URL for the content in the webview. In the case of iframes the URL given is the parent windows and not the url for the content of the iframe.
RUN THE ATTACHED ELECTRON FIDDLE
### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
The url printed in the console should be the same for each call and match the content url of both the iframe and webview.
Both getURL calls should have a value of: https://statics.teams.microsoft.com/evergreen-assets/tabs/v0.4/devicePermissionTab.html
### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
The url printed in the console for the iframe is incorrect. Its giving us the url of the parent window and not the contents window: file:///var/folders/1m/mvzrl4cn4c7cqw47g8xk1m3h0000gn/T/tmp-10161DTmlueZz9SLn/index.html
### To Reproduce
* Run the attached test Electron fiddle app.
* In the first window (iframe) click on the button under "notifications" to which will emit a device permissions request on the content.
* In the second window (webview) click the same button under "notifications".
* Look at the console output
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->
<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->
### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
### Additional Information
<!-- Add any other context about the problem here. -->
[iframedeviceperms.zip](https://github.com/electron/electron/files/3283118/iframedeviceperms.zip)
|
https://github.com/electron/electron/issues/18755
|
https://github.com/electron/electron/pull/18757
|
7c76d0e34a8b7d81379529ca65867e9deb591f39
|
ac02ab9fdea0778d3e5fb4888f7c6a4a6420466a
| 2019-06-12T21:06:16Z |
c++
| 2019-06-13T18:11:43Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,745 |
["shell/browser/ui/views/menu_bar.cc"]
|
Undo/Redo/Cut/Copy/Paste & more Not work using Menubar in Windows
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
* 5.0.3
* **Operating System:**
* Windows 10 (1809)
* **Last Known Working Electron version:**
* 4.2.4
### Expected Behavior
Selecting Undo/Redo/Cut/Copy/Paste/ZoomIn/ZoomOut/ResetZoom from menu bar with mouse performs those various functions.
### Actual Behavior
Selecting these options from the menubar using the mouse seems to have no effect.
Using keyboard shortcuts does work ok.
Both mouse & keyboard works ok for all functions in MacOS 10.14.5.
### To Reproduce
https://github.com/electron/fiddle/releases/tag/v0.8.1
Download and run, then try Edit and View menus.
This uses 5.0.1
I have same problem in my own app using 5.0.3. Problem eliminated by downgrading to 4.2.4.
### Additional Information
My app uses standard MenuItem roles:
```
{ role: 'resetzoom' },
{ role: 'zoomin' },
{ role: 'zoomout' },
```
Electron Fiddle does the same:
https://github.com/electron/fiddle/blob/88ce4a76e97c4c93821306b59b3de9a147378058/src/main/menu.ts
```
item.submenu.push({ type: 'separator' }, { role: 'resetzoom' }, { role: 'zoomin' }, { role: 'zoomout' }); // Add zooming actions
```
|
https://github.com/electron/electron/issues/18745
|
https://github.com/electron/electron/pull/19657
|
57507ca37c7584de79e64732b06005e4362df811
|
1749af9707e7d1aab662ce3ef265b3fcc6f7f20b
| 2019-06-12T15:09:41Z |
c++
| 2019-08-09T21:10:11Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,734 |
["docs/api/browser-view.md", "shell/browser/api/atom_api_browser_view.cc", "shell/browser/api/atom_api_browser_view.h", "shell/browser/native_browser_view.h", "shell/browser/native_browser_view_mac.h", "shell/browser/native_browser_view_mac.mm", "shell/browser/native_browser_view_views.cc", "shell/browser/native_browser_view_views.h", "spec-main/api-browser-view-spec.ts"]
|
Add getBounds for BrowserView like BrowserWindow
|
<!-- As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->
### Feature Request
The only current way to get the parameters set by ``setBounds`` of a ``BrowserView`` seems to be to store it as a global variable at creation, and to reference that variable. Ideally, there should be a way to get this information from the created ``BrowserView`` directly with ``getBounds``, like the ``BrowserWindow``. This is particularly important if the bounds of the ``BrowserView`` has been changed by ``setAutoResize`` after creation, because the bounds no longer match a stored global variable.
|
https://github.com/electron/electron/issues/18734
|
https://github.com/electron/electron/pull/19370
|
c06007175fedd0e34279f54be7fa1d9f5a2c1249
|
42a483ad2734e97b214aa29cdadc541525daac53
| 2019-06-11T18:20:54Z |
c++
| 2019-07-30T02:43:05Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,708 |
["atom/browser/api/atom_api_in_app_purchase.cc", "atom/browser/mac/in_app_purchase_product.h", "atom/browser/mac/in_app_purchase_product.mm", "docs/api/structures/product.md"]
|
in-app-purchase / product - Miss match between documentation/types to result
|
`Product` of (`InAppPurchase`) - Miss match between documentation/types to result of the key `downloadable`.
### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
### Issue Details
* **Electron Version:**
`v5.0.3`
* **Operating System:**
macOS 10.14.15
* **Last Known Working Electron version:**
N/A
### Expected Behavior
The `Product` structure of returned data from `inAppPurchase.getProducts()` should contain `downloadable` key as in the [docs / TS type definitions](https://github.com/electron/electron/blob/master/docs/api/structures/product.md)
### Actual Behavior
The `Product` contains `isDownloadable` key (which isn't documented).
### To Reproduce
### Screenshots
### Additional Information
I think the issue related to [this line](https://github.com/electron/electron/blob/3e5a98b5f43fe70961eb6452dc8837453c6de1a0/atom/browser/api/atom_api_in_app_purchase.cc#L64)
|
https://github.com/electron/electron/issues/18708
|
https://github.com/electron/electron/pull/18720
|
5317211b0b3ccb3d13f80e2c812569f4d35ec33d
|
292a240e1b166dea3f4bff6c523fde86430b77e7
| 2019-06-10T08:57:10Z |
c++
| 2019-06-12T17:54:14Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 18,701 |
["shell/browser/api/atom_api_notification.cc"]
|
Notification close() causes app crash at exit
|
* **Electron Version:**
* 5.0.x
* **Operating System:**
* macOS 10.14.5
### Expected Behavior
Electron does not crash at exit.
### Actual Behavior
The notifications are sent well, i use the close() function to avoid persistence in Notification Center.
By doing this every time I quit the application I have a message that warns me that the application did not stop properly.
### To Reproduce
```javascript
const notif = new Notification({title: title, body: body, silent: true})
notif.on('click', () => appEvent.emit('show-window'))
notif.show()
setTimeout(() => notif.close(), 10000)
```
After sending notification(s), close application (app.quit()) and the error will appear.
To no longer have the error after quitting app, i do not use the function close () but my application generates a lot of notifications and I would have preferred to handle that.
|
https://github.com/electron/electron/issues/18701
|
https://github.com/electron/electron/pull/21709
|
bd923838c108c0ea693f3a158a5d1ca09cd317b3
|
f5e202a89871ff50a95e3113cf246e226257fac0
| 2019-06-09T12:58:49Z |
c++
| 2020-01-09T17:42:20Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.