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
| 5,269 |
["atom/browser/api/atom_api_desktop_capturer.cc", "spec/api-desktop-capturer-spec.js"]
|
Two subsequent calls to desktopCapturer.getSources() with different types - only first called back
|
- Electron version: 0.37.6
- Operating system: Ubuntu 14.04
When calling `desktopCapturer.getSources()` with different types one after another, only callback for the first call is executed.
```
desktopCapturer.getSources({ types: ['window'] }, callback1)
desktopCapturer.getSources({ types: ['screen'] }, callback2)
```
Here only `callback1` will be called.
Here is a spec which fails on master branch:
```
it('should respond to two subsequent calls with different options', function (done) {
var callCount = 0
var callback = function (error, sources) {
callCount++
assert.notEqual(sources.length, 0)
if (callCount === 2) done()
}
desktopCapturer.getSources({ types: ['window'] }, callback)
desktopCapturer.getSources({ types: ['screen'] }, callback)
})
```
I did some investigation - [`desktopCapturer.startHandling`](https://github.com/electron/electron/blob/master/lib/browser/desktop-capturer.js#L75) is called for a second time, but [`desktopCapturer.emit`](https://github.com/electron/electron/blob/master/lib/browser/desktop-capturer.js#L36) is only called once. Seems like an issue with media listeners, but I wasn't able to get deep into c++ code. Thanks!
|
https://github.com/electron/electron/issues/5269
|
https://github.com/electron/electron/pull/5320
|
68192785e7d813c9103196146957086e82132f76
|
850bc2d44319289d04ec64dde542dc00b5ff64bc
| 2016-04-23T19:13:40Z |
c++
| 2016-04-28T11:14:58Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,267 |
["atom/browser/native_window_views.cc", "atom/browser/ui/views/win_frame_view.cc", "atom/browser/ui/win/atom_desktop_window_tree_host_win.cc", "atom/browser/ui/win/atom_desktop_window_tree_host_win.h", "electron.gyp"]
|
Strange overflowing window when maximizing a frameless window
|
- Electron version: `0.37.4`
- Operating system: Windows
When I maximize my [frameless](https://github.com/electron/electron/blob/master/docs/api/frameless-window.md) electron window a small part of the window in an unmaximized state is visible on a secondary monitor.
**Screenshot**
You can visibly see the "line between the monitors" and you can see some really strange overhanging content that is over that line.
**Steps to reproduce**
1. Open an electron app
2. Maximize the app on your secondary display
3. Look closely for the overflow onto your primary display
This might take a few times to trigger, it appears to do it about 70% of the time :confused:
|
https://github.com/electron/electron/issues/5267
|
https://github.com/electron/electron/pull/9167
|
7f4bd79b01d795e4cfbcabd46784e61dbaa4532b
|
0c1d60381df21f9c1f06a641eaf97ca4d3dec65e
| 2016-04-23T15:27:37Z |
c++
| 2017-04-13T10:08:39Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,246 |
["atom/browser/common_web_contents_delegate_mac.mm", "atom/browser/native_window_mac.mm", "vendor/brightray"]
|
Move Focus to Next Window not working anymore
|
- Electron version: 0.37.6
- Operating system: Mac OS X 10.11
A user reported that with VS Code running with Electron 0.37.6 would no longer allow him to "Move Focus to Next Window". It seems you can assign a keybinding for this globally in settings (in this case he tried with Cmd+F1).
I verified that the same keybinding works just fine with our VS Code on Electron 0.35.6.
When I look through the release notes, I see an entry in v0.36.8 that might be suspicious?
> Fix Command + ~ not switching windows sometimes.
|
https://github.com/electron/electron/issues/5246
|
https://github.com/electron/electron/pull/6068
|
31d619f7482c662b43e7c15fa9ba118441df7bb8
|
6f4899bd946d017cd0eec3682ab8bfd8df8fb8c6
| 2016-04-21T21:36:55Z |
c++
| 2016-06-19T11:22:02Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,230 |
["atom/browser/common_web_contents_delegate.cc", "atom/browser/common_web_contents_delegate.h"]
|
Search through files not working in devtools after adding folder in workspace
|
- Electron version: 0.36.12, 0.37.6
- Operating system: Kubuntu 15.10
Try Ctrl+Shift+F, find progress freeze always.
|
https://github.com/electron/electron/issues/5230
|
https://github.com/electron/electron/pull/5431
|
e6f4dd0f85d01102ec9fed3daa97a82344b9de6f
|
8f4b6afa646e1f0933c8efaa1cd799278aa35eb2
| 2016-04-20T20:38:31Z |
c++
| 2016-05-07T01:55:12Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,228 |
["atom/browser/api/atom_api_session.cc", "atom/browser/api/save_page_handler.cc", "atom/browser/api/save_page_handler.h", "atom/browser/atom_download_manager_delegate.cc"]
|
Downloading a file emits a `did-fail-load` event
|
- Electron version: 0.36.9
- Operating system: Mac OSX 10.11.14
When I click on a link that triggers a file download, it emits a `did-fail-load` event with an error code `-3`. The download works and is saved as expected though.
As a side note, I was calling `loadURL` in the `did-fail-load` handler which caused Electron to crash. I can provide the full dump for that if you'd like.
Let me know if you'd like any more details.
|
https://github.com/electron/electron/issues/5228
|
https://github.com/electron/electron/pull/5315
|
77573281b5fc301de5ce3536e85614c3344f7947
|
122652a3683d457b2721f2c48381b58a65500d43
| 2016-04-20T17:18:22Z |
c++
| 2016-04-28T07:08:22Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,215 |
["lib/browser/rpc-server.js", "lib/renderer/api/remote.js"]
|
Error: Cannot read property 'name' of undefined at valueToMeta (.../node_modules/electron-prebuilt/dist/resources/electron.asar/browser/rpc-server.js:76:41)
|
- Electron version: 0.37.6 (0.33 exhibited as well)
- Operating system: "Ubuntu 12.04 LTS"
We use Electron on Linux to run some tests, and we just began seeing this error:
```
00:21:39.567 [14629:0419/140939:INFO:CONSOLE(37)] "Error: Cannot read property 'name' of undefined
00:21:39.567 TypeError: Cannot read property 'name' of undefined
00:21:39.567 at valueToMeta (/home/vagrant/workspace/Evergreen_Test_Runner/ynab_web/node_modules/electron-prebuilt/dist/resources/electron.asar/browser/rpc-server.js:76:41)
00:21:39.568 at EventEmitter.<anonymous> (/home/vagrant/workspace/Evergreen_Test_Runner/ynab_web/node_modules/electron-prebuilt/dist/resources/electron.asar/browser/rpc-server.js:337:25)
00:21:39.568 at emitThree (events.js:110:13)
00:21:39.568 at EventEmitter.emit (events.js:188:7)
00:21:39.568 at EventEmitter.<anonymous> (/home/vagrant/workspace/Evergreen_Test_Runner/ynab_web/node_modules/electron-prebuilt/dist/resources/electron.asar/browser/api/web-contents.js:139:25)
00:21:39.569 at emitTwo (events.js:100:13)
00:21:39.569 at EventEmitter.emit (events.js:185:7)
00:21:39.569 at metaToValue (/home/vagrant/workspace/Evergreen_Test_Runner/ynab_web/node_modules/electron-prebuilt/dist/resources/electron.asar/renderer/api/remote.js:176:13)
00:21:39.569 at undefined.descriptor.get [as _externalStream] (/home/vagrant/workspace/Evergreen_Test_Runner/ynab_web/node_modules/electron-prebuilt/dist/resources/electron.asar/renderer/api/remote.js:125:16)
00:21:39.570 at xt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:1971:1)
00:21:39.570 at Yt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2025:1)
00:21:39.570 at Nt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2316:1)
00:21:39.570 at Ht (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2386:1)
00:21:39.570 at http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2320:1
00:21:39.571 at xt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:1971:1)
00:21:39.571 at Yt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2025:1)
00:21:39.571 at Nt (http://localhost:3000/ynab_shared_library/node_modules/lodash/index.js:2316:1)"
```
I am investigating to see what we've changed recently that would have caused this, but we didn't upgrade Electron. Is there an easy way for me to see the code in `browser/rpc-server.js:76:41` to get an idea of what this might be? I assume we're doing something wrong, and the fact that it's crashing in Electron is a red herring, but I'm not sure yet.
|
https://github.com/electron/electron/issues/5215
|
https://github.com/electron/electron/pull/5223
|
965c3f605ee53ebce72785c73e6a18940deadd51
|
3fdcbcef03388e788ae58ad4f4851e6c32b3eba5
| 2016-04-19T18:23:19Z |
c++
| 2016-04-20T05:47:16Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,206 |
["atom/browser/native_window_views.cc"]
|
BrowserWindow.focus() does not focus
|
- Electron version: the one bundled with Atom 1.7.1, also 0.36.0
- Operating system: Linux
The "focus()" call does not actually focus the window, it only raises it. Focus remains in the caller app (terminal, for instance).
No "focus stealing prevention" is used. This can be reproduced on multiple window managers (xfwm, unity).
Steps to reproduce, using Atom (as an example -- works with any other Electron-based app that focuses itself):
1. open terminal
2. `atom myfile.txt`
3. switch back to terminal
4. `atom myfile.txt`
5. note that Atom raised itself, but the focus is still in terminal.
|
https://github.com/electron/electron/issues/5206
|
https://github.com/electron/electron/pull/5888
|
438cab1f562a80c3a658007421e7a0903b3b42b4
|
3e809901e07a77cec781c4d3f5ee5d7f4450b7b7
| 2016-04-19T10:13:47Z |
c++
| 2016-06-06T08:26:47Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,200 |
["atom/browser/atom_resource_dispatcher_host_delegate.cc", "atom/browser/web_contents_permission_helper.cc", "atom/browser/web_contents_permission_helper.h", "atom/common/native_mate_converters/content_converter.cc", "docs/api/session.md", "spec/webview-spec.js"]
|
Prevent unknown schemes from being opened in an external app
|
- Electron version: 0.37.6
- Operating system: OS X
As of https://github.com/electron/electron/issues/2687, unknown schemes are automatically opened in an external app. There appears to be no way to prevent this behavior or prompt the user for permission before the external app is opened.
One way to solve this would be to allow wildcards in `protocol.registerXXXProtocol`; then the Electron app can do whatever checks it wants before calling `shell.openExternal` on the URL.
|
https://github.com/electron/electron/issues/5200
|
https://github.com/electron/electron/pull/5231
|
aa29dc0c8a64f61cc0d17d815a6096c7c6d3b44d
|
a836ee4ea74b0f822b10a9317e163a09e963458e
| 2016-04-18T23:58:09Z |
c++
| 2016-04-21T02:50:01Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,187 |
["atom/browser/api/event.cc", "spec/api-ipc-spec.js"]
|
Crash if use 'ipcMain.on' twice to handle ipcRender's synchronous-message
|
- Electron version: v0.37.6
- Operating system: Mac OS
**Test code:**
Simply add 'ipcMain.on' twice in the `main.js` and ipcRenderer.sendSync in `index.html`, run the program and it will crash when started.
**main.js:**
```
'use strict';
const electron = require('electron');
// Module to control application life.
const app = electron.app;
// Module to create native browser window.
const BrowserWindow = electron.BrowserWindow;
const ipcMain = electron.ipcMain;
// Keep a global reference of the window object, if you don't, the window will
// be closed automatically when the JavaScript object is garbage collected.
mainWindow = global.mainWindow = undefined
function createWindow () {
const controller = require('./controller')
// Create the browser window.
mainWindow = new BrowserWindow({width: 800, height: 600});
ipcMain.on('synchronous-message', function(event, status) {console.log("test"); event.returnValue="test"})
ipcMain.on('synchronous-message', function(event, status) {console.log("test"); event.returnValue="test"})
// and load the index.html of the app.
mainWindow.loadURL('file://' + __dirname + '/index.html');
// Open the DevTools.
mainWindow.webContents.openDevTools();
// Emitted when the window is closed.
mainWindow.on('closed', function() {
// Dereference the window object, usually you would store windows
// in an array if your app supports multi windows, this is the time
// when you should delete the corresponding element.
mainWindow = null;
});
}
// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
app.on('ready', createWindow);
// var onlineStatusWindow;
// app.on('ready', function() {
// onlineStatusWindow = new BrowserWindow({ width: 0, height: 0, show: false });
// onlineStatusWindow.loadURL('file://' + __dirname + '/online-status.html');
// });
// Quit when all windows are closed.
app.on('window-all-closed', function () {
// On OS X it is common for applications and their menu bar
// to stay active until the user quits explicitly with Cmd + Q
if (process.platform !== 'darwin') {
app.quit();
}
});
app.on('activate', function () {
// On OS X it's common to re-create a window in the app when the
// dock icon is clicked and there are no other windows open.
if (mainWindow === null) {
createWindow();
}
});
```
**index.html**
```
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Hello World!</title>
</head>
<body>
<h1>Hello World!</h1>
We are using node <script>document.write(process.versions.node)</script>,
Chromium <script>document.write(process.versions.chrome)</script>,
and Electron <script>document.write(process.versions.electron)</script>.
</body>
<script>
const ipcRenderer = require('electron').ipcRenderer;
ipcRenderer.sendSync('synchronous-message')
</script>
</html>
```
|
https://github.com/electron/electron/issues/5187
|
https://github.com/electron/electron/pull/5430
|
e46a50512dbc4eeef7bf044890e21db47b1bf9d4
|
b05fa2ed5b9a1cf2a135d6f61e67f13a221fee5e
| 2016-04-17T16:57:43Z |
c++
| 2016-05-07T07:32:54Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,183 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/api/atom_api_web_contents.h", "docs/api/web-contents.md", "lib/browser/api/web-contents.js", "lib/renderer/web-view/web-view.js", "spec/api-browser-window-spec.js"]
|
`WebContents.executeJavaScript()` never succeeds when called during a resource load, but after page load
|
- Electron version: 0.37.6
- Operating system: All platforms
If you call WebContents’s `executeJavaScript()` method after the main frame finishes loading, but while a subframe is loading, the JS will never get executed and the call will never complete (unless you navigate the main frame to some new page). The culprit is how the JS additions to `WebContents` choose to forward the call to the `WebFrame`: https://github.com/electron/electron/blob/master/lib/browser/api/web-contents.js#L119
`webContents.isLoading()` will be true when a subframe is loading even if the main frame is finished. In that case the JS additions wait for `did-finish-load` before sending the call off to the frame, but that never happens.
I _think_ Chromium’s `WebContents::IsLoadingToDifferentDocument` is the thing we actually want to check (instead of `WebContents::IsLoading`), but that’s not exposed in Electron’s WebContents API. Should it be? If not, we could track the `did-get-response-details` event to determine whether the main frame is loading. (We can’t use `did-start-loading` because that fires for sub-frames and there’s currently no way to differentiate [should there be?]).
On the other hand, is this check really about not running scripts while a page is loading, or is it just about making sure at least the first page has been loaded? (The `this.getURL()` check is what makes me wonder). If so, it would be better and simpler to just have a flag that says a page has been loaded, so any `executeJavaScript` call is now safe to forward along.
Many Nightmare users are hitting this issue in real-world cases (it’s particularly bad on pretty much any page with ads), e.g. https://github.com/segmentio/nightmare/issues/375
Simple Electron app test case:
``` js
var electron = require('electron');
var mainWindow = null;
electron.app.on('ready', function() {
mainWindow = new electron.BrowserWindow({show: true});
mainWindow.webContents.on('did-finish-load', function() {
console.log('Main frame loaded.');
setTimeout(() => {
mainWindow.webContents.executeJavaScript(`
var iframe = document.createElement('iframe');
iframe.src = 'http://cnn.com';
document.body.appendChild(iframe);
`);
}, 40);
setTimeout(function execute() {
console.log('Started executeJavaScript');
mainWindow.webContents.executeJavaScript(
'console.log("hello");',
result => {
console.log('...finished');
setTimeout(execute, 25);
});
}, 25);
});
mainWindow.webContents.loadURL('http://example.com');
});
```
This logs:
```
Main frame loaded.
Started executeJavaScript
...finished
Started executeJavaScript
```
And just stops there, when you should get `...finished` again.
|
https://github.com/electron/electron/issues/5183
|
https://github.com/electron/electron/pull/5199
|
823c4f91a8a1c5f9275412582bf461c51007b937
|
aa29dc0c8a64f61cc0d17d815a6096c7c6d3b44d
| 2016-04-16T17:09:55Z |
c++
| 2016-04-20T11:49:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,180 |
["atom/browser/api/atom_api_web_contents.cc"]
|
Intermittent crash getting `devToolsWebContents.hostWebContents` in `did-get-response-details` event
|
- Electron version: 0.37.6, also current master (8d08c3241dda53753be3e612133df96ceb8ab885)
- Operating system: Mac OS X 10.11.4
If the devtools are already open in a window when it is navigating, trying to access `event.sender.devToolsWebContents.hostWebContents` in the `did-get-response-details` event can sometimes crash Electron at [`atom_api_web_contents:1161`](https://github.com/electron/electron/blob/master/atom/browser/api/atom_api_web_contents.cc#L1161)
I ran into this in the wild when [Nightmare’s](https://github.com/segmentio/nightmare) test suite started intermittently crashing. ~~I have not seen the crash on Linux, so I’m not sure if it is specific to OS X.~~ This happens in Nightmare when some events get forwarded across process boundaries using `JSON.stringify()`, which tries to access `devToolsWebContents.hostWebContents`. I’m guessing the dev tools are in the middle of reloading here and not all references are still (or yet?) valid.
Minimal test case electron script:
``` js
var electron = require('electron');
var mainWindow = null;
electron.app.on('ready', function() {
mainWindow = new electron.BrowserWindow({
width: 1000,
height: 800,
show: true
});
mainWindow.webContents.openDevTools();
setTimeout(navigate, 500);
function navigate() {
mainWindow.webContents.on('did-get-response-details', function(event) {
console.log('did-get-response-details', [].slice.call(arguments, 1));
// the next line crashes intermittently
event.sender.devToolsWebContents && event.sender.devToolsWebContents.hostWebContents;
});
mainWindow.webContents.loadURL('http://example.com');
}
});
```
Crash report (from debug build, so more details):
```
Process: Electron [92065]
Path: /Users/USER/*/Electron-dev.app/Contents/MacOS/Electron
Identifier: com.github.electron
Version: 0.37.6 (0.37.6)
Code Type: X86-64 (Native)
Parent Process: node [92064]
Responsible: Terminal [261]
User ID: 501
Date/Time: 2016-04-15 15:23:20.084 -0700
OS Version: Mac OS X 10.11.4 (15E65)
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libcontent.dylib 0x0000000106f3b544 content::WebContentsObserver::web_contents() const + 4
1 com.github.electron.framework 0x00000001032b99a9 atom::api::WebContents::HostWebContents() + 73 (atom_api_web_contents.cc:1161)
2 com.github.electron.framework 0x00000001032e59b9 base::internal::RunnableAdapter<content::WebContents* (atom::api::WebContents::*)()>::Run(atom::api::WebContents*) + 105 (bind_internal.h:178)
3 com.github.electron.framework 0x00000001032e5949 base::internal::InvokeHelper<false, content::WebContents*, base::internal::RunnableAdapter<content::WebContents* (atom::api::WebContents::*)()>, base::internal::TypeList<atom::api::WebContents* const&> >::MakeItSo(base::internal::RunnableAdapter<content::WebContents* (atom::api::WebContents::*)()>, atom::api::WebContents* const&) + 41 (bind_internal.h:290)
4 com.github.electron.framework 0x00000001032e5915 base::internal::Invoker<base::IndexSequence<>, base::internal::BindState<base::internal::RunnableAdapter<content::WebContents* (atom::api::WebContents::*)()>, content::WebContents* (atom::api::WebContents*)>, base::internal::TypeList<>, base::internal::InvokeHelper<false, content::WebContents*, base::internal::RunnableAdapter<content::WebContents* (atom::api::WebContents::*)()>, base::internal::TypeList<atom::api::WebContents* const&> >, content::WebContents* (atom::api::WebContents* const&)>::Run(base::internal::BindStateBase*, atom::api::WebContents* const&) + 69 (bind_internal.h:347)
5 com.github.electron.framework 0x00000001032e5656 base::Callback<content::WebContents* (atom::api::WebContents*)>::Run(atom::api::WebContents* const&) const + 70 (callback.h:394)
6 com.github.electron.framework 0x00000001032e55a8 void mate::internal::Invoker<mate::internal::IndicesHolder<0ul>, atom::api::WebContents*>::DispatchToCallback<content::WebContents*>(base::Callback<content::WebContents* (atom::api::WebContents*)>) + 40 (function_template.h:187)
7 com.github.electron.framework 0x00000001032e53e9 mate::internal::Dispatcher<content::WebContents* (atom::api::WebContents*)>::DispatchToCallback(v8::FunctionCallbackInfo<v8::Value> const&) + 313 (function_template.h:228)
8 libv8.dylib 0x0000000104c26ca3 v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 163
9 libv8.dylib 0x0000000104c5dc3e 0x104bef000 + 453694
10 libv8.dylib 0x0000000104c5d7db v8::internal::Builtins::InvokeApiFunction(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 411
11 libv8.dylib 0x0000000104ea0fe8 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 520
12 libv8.dylib 0x0000000104f969e4 v8::internal::Object::GetPropertyWithAccessor(v8::internal::LookupIterator*, v8::internal::LanguageMode) + 644
13 libv8.dylib 0x0000000104f95e45 v8::internal::Object::GetProperty(v8::internal::LookupIterator*, v8::internal::LanguageMode) + 245
14 libv8.dylib 0x0000000104f3b7f2 v8::internal::LoadIC::Load(v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Name>) + 978
15 libv8.dylib 0x0000000104f42253 v8::internal::Runtime_LoadIC_Miss(int, v8::internal::Object**, v8::internal::Isolate*) + 771
16 ??? 0x00001a6f79b0c1fb 0 + 29066085319163
17 ??? 0x00001a6f79cbe8ac 0 + 29066087098540
18 ??? 0x00001a6f79b0f6b7 0 + 29066085332663
19 ??? 0x00001a6f79cbe490 0 + 29066087097488
20 ??? 0x00001a6f79c3aea6 0 + 29066086559398
21 ??? 0x00001a6f79b0f6b7 0 + 29066085332663
22 ??? 0x00001a6f79b36e64 0 + 29066085494372
23 ??? 0x00001a6f79b19a62 0 + 29066085374562
24 libv8.dylib 0x0000000104ea12b0 0x104bef000 + 2826928
25 libv8.dylib 0x0000000104ea0fa8 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 456
26 libv8.dylib 0x0000000104c0d13c v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) + 300
27 libnode.dylib 0x00000001041f1dcd node::MakeCallback(node::Environment*, v8::Local<v8::Value>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*) + 1357 (node.cc:1198)
28 libnode.dylib 0x00000001041f267e node::MakeCallback(node::Environment*, v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*) + 174 (node.cc:1276)
29 libnode.dylib 0x00000001041f26f1 node::MakeCallback(node::Environment*, v8::Local<v8::Object>, char const*, int, v8::Local<v8::Value>*) + 97 (node.cc:1286)
30 libnode.dylib 0x00000001041f27a1 node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, char const*, int, v8::Local<v8::Value>*) + 161 (node.cc:1300)
31 com.github.electron.framework 0x00000001033e21ca mate::internal::CallEmitWithArgs(v8::Isolate*, v8::Local<v8::Object>, std::__1::vector<v8::Local<v8::Value>, std::__1::allocator<v8::Local<v8::Value> > >*) + 170 (event_emitter_caller.cc:25)
32 com.github.electron.framework 0x00000001032c92ab v8::Local<v8::Value> mate::EmitEvent<base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, v8::Local<v8::Object>, bool, GURL, GURL, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, net::HttpResponseHeaders*, char const*>(v8::Isolate*, v8::Local<v8::Object>, base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, v8::Local<v8::Object> const&, bool const&, GURL const&, GURL const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, net::HttpResponseHeaders* const&, char const* const&) + 907 (event_emitter_caller.h:48)
33 com.github.electron.framework 0x00000001032c8e43 bool mate::EventEmitter::EmitWithEvent<bool, GURL, GURL, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, net::HttpResponseHeaders*, char const*>(base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, v8::Local<v8::Object>, bool const&, GURL const&, GURL const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, net::HttpResponseHeaders* const&, char const* const&) + 339 (event_emitter.h:65)
34 com.github.electron.framework 0x00000001032c8cb7 bool mate::EventEmitter::EmitWithSender<bool, GURL, GURL, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, net::HttpResponseHeaders*, char const*>(base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, content::WebContents*, IPC::Message*, bool const&, GURL const&, GURL const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, net::HttpResponseHeaders* const&, char const* const&) + 327 (event_emitter.h:51)
35 com.github.electron.framework 0x00000001032bd36e bool mate::EventEmitter::Emit<bool, GURL, GURL, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, net::HttpResponseHeaders*, char const*>(base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&, bool const&, GURL const&, GURL const&, int const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, net::HttpResponseHeaders* const&, char const* const&) + 174 (event_emitter.h:39)
36 com.github.electron.framework 0x00000001032b5e3d atom::api::WebContents::DidGetResourceResponseStart(content::ResourceRequestDetails const&) + 269 (atom_api_web_contents.cc:590)
37 libcontent.dylib 0x00000001072df0f6 content::WebContentsImpl::DidGetResourceResponseStart(content::ResourceRequestDetails const&) + 342
38 libcontent.dylib 0x000000010715073e 0x106f2c000 + 2246462
39 libbase.dylib 0x000000010565293a base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&) + 202
40 libbase.dylib 0x000000010567c1c9 base::MessageLoop::RunTask(base::PendingTask const&) + 489
41 libbase.dylib 0x000000010567c818 base::MessageLoop::DoWork() + 632
42 libbase.dylib 0x0000000105643cf1 0x105641000 + 11505
43 libbase.dylib 0x000000010566fa5a base::mac::CallWithEHFrame(void () block_pointer) + 10
44 libbase.dylib 0x00000001056436f4 0x105641000 + 9972
45 com.apple.CoreFoundation 0x00007fff9ad26881 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
46 com.apple.CoreFoundation 0x00007fff9ad05fbc __CFRunLoopDoSources0 + 556
47 com.apple.CoreFoundation 0x00007fff9ad054df __CFRunLoopRun + 927
48 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
49 com.apple.HIToolbox 0x00007fff8ea8f935 RunCurrentEventLoopInMode + 235
50 com.apple.HIToolbox 0x00007fff8ea8f76f ReceiveNextEventCommon + 432
51 com.apple.HIToolbox 0x00007fff8ea8f5af _BlockUntilNextEventMatchingListInModeWithFilter + 71
52 com.apple.AppKit 0x00007fff8b250efa _DPSNextEvent + 1067
53 com.apple.AppKit 0x00007fff8b25032a -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
54 com.apple.AppKit 0x00007fff8b244e84 -[NSApplication run] + 682
55 libbase.dylib 0x000000010564464f 0x105641000 + 13903
56 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
57 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
58 libcontent.dylib 0x0000000106fcb75b content::BrowserMainLoop::MainMessageLoopRun() + 155
59 libcontent.dylib 0x0000000106fcb573 content::BrowserMainLoop::RunMainMessageLoopParts() + 67
60 libcontent.dylib 0x0000000106fcdd82 0x106f2c000 + 662914
61 libcontent.dylib 0x0000000106fc73dd content::BrowserMain(content::MainFunctionParams const&) + 173
62 libcontent.dylib 0x0000000106f311ec 0x106f2c000 + 20972
63 libcontent.dylib 0x0000000106f306e6 content::ContentMain(content::ContentMainParams const&) + 54
64 com.github.electron.framework 0x00000001031fa4a8 AtomMain + 104 (atom_library_main.mm:24)
65 com.github.electron 0x00000001031f1e08 main + 72 (atom_main.cc:194)
66 libdyld.dylib 0x00007fff92f6f5ad start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff93a6d5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a2b5578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a2b3341 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff93a6defa kevent_qos + 10
1 libdispatch.dylib 0x00007fff9f68a165 _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff9f689dcd _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x00007fff93a6d5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a2b5578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a2b3341 start_wqthread + 13
Thread 4:: WorkerPool/14595
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b675e _pthread_cond_wait + 821
2 libbase.dylib 0x00000001056aa25b base::ConditionVariable::TimedWait(base::TimeDelta const&) + 91
3 libbase.dylib 0x00000001056c19ed base::PosixDynamicThreadPool::WaitForTask() + 205
4 libbase.dylib 0x00000001056c1ea4 0x105641000 + 528036
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 5:: WorkerPool/14095
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b675e _pthread_cond_wait + 821
2 libbase.dylib 0x00000001056aa25b base::ConditionVariable::TimedWait(base::TimeDelta const&) + 91
3 libbase.dylib 0x00000001056c19ed base::PosixDynamicThreadPool::WaitForTask() + 205
4 libbase.dylib 0x00000001056c1ea4 0x105641000 + 528036
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 6:: WorkerPool/12807
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b675e _pthread_cond_wait + 821
2 libbase.dylib 0x00000001056aa25b base::ConditionVariable::TimedWait(base::TimeDelta const&) + 91
3 libbase.dylib 0x00000001056c19ed base::PosixDynamicThreadPool::WaitForTask() + 205
4 libbase.dylib 0x00000001056c1ea4 0x105641000 + 528036
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff93a6d07a __select + 10
1 libnode.dylib 0x000000010446b883 uv__stream_osx_select + 659 (stream.c:169)
2 libnode.dylib 0x000000010446f48d uv__thread_start + 61 (thread.c:49)
3 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
4 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
5 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff93a6d07a __select + 10
1 libnode.dylib 0x000000010446b883 uv__stream_osx_select + 659 (stream.c:169)
2 libnode.dylib 0x000000010446f48d uv__thread_start + 61 (thread.c:49)
3 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
4 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
5 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff93a6d5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a2b5578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a2b3341 start_wqthread + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff93a6d5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a2b5578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a2b3341 start_wqthread + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff93a6d5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a2b5578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a2b3341 start_wqthread + 13
Thread 12:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 com.apple.Foundation 0x00007fff97053dd9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270
6 libbase.dylib 0x000000010564446e base::MessagePumpNSRunLoop::DoRun(base::MessagePump::Delegate*) + 126
7 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
8 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
9 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
10 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
11 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
12 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
13 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
14 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 13:: DnsConfigService
0 libsystem_kernel.dylib 0x00007fff93a6deca kevent + 10
1 libbase.dylib 0x00000001056f3207 0x105641000 + 729607
2 libbase.dylib 0x00000001056f0b4b 0x105641000 + 719691
3 libbase.dylib 0x0000000105643001 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 417
4 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
5 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
6 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
7 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
8 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
9 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
10 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 14:: CrShutdownDetector
0 libsystem_kernel.dylib 0x00007fff93a6e362 read + 10
1 com.github.electron.framework 0x0000000103322c44 atom::(anonymous namespace)::ShutdownDetector::ThreadMain() + 228 (atom_browser_main_parts_posix.cc:124)
2 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
3 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
4 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
5 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 15:: Chrome_DBThread
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 libbase.dylib 0x00000001056440ff base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + 79
6 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
7 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
8 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
9 libcontent.dylib 0x0000000106fd52a8 content::BrowserThreadImpl::DBThreadRun(base::MessageLoop*) + 24
10 libcontent.dylib 0x0000000106fd55f6 content::BrowserThreadImpl::Run(base::MessageLoop*) + 102
11 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
12 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
13 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
14 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
15 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 16:: Chrome_FileThread
0 libsystem_kernel.dylib 0x00007fff93a6deca kevent + 10
1 libbase.dylib 0x00000001056f3207 0x105641000 + 729607
2 libbase.dylib 0x00000001056f0b4b 0x105641000 + 719691
3 libbase.dylib 0x0000000105642fe9 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 393
4 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
5 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
6 libcontent.dylib 0x0000000106fd5328 content::BrowserThreadImpl::FileThreadRun(base::MessageLoop*) + 24
7 libcontent.dylib 0x0000000106fd5603 content::BrowserThreadImpl::Run(base::MessageLoop*) + 115
8 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
9 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
10 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
11 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
12 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 17:: Chrome_FileUserBlockingThread
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 libbase.dylib 0x00000001056440ff base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + 79
6 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
7 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
8 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
9 libcontent.dylib 0x0000000106fd53a8 content::BrowserThreadImpl::FileUserBlockingThreadRun(base::MessageLoop*) + 24
10 libcontent.dylib 0x0000000106fd5610 content::BrowserThreadImpl::Run(base::MessageLoop*) + 128
11 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
12 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
13 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
14 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
15 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 18:: Chrome_ProcessLauncherThread
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 libbase.dylib 0x00000001056440ff base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + 79
6 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
7 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
8 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
9 libcontent.dylib 0x0000000106fd5428 content::BrowserThreadImpl::ProcessLauncherThreadRun(base::MessageLoop*) + 24
10 libcontent.dylib 0x0000000106fd561d content::BrowserThreadImpl::Run(base::MessageLoop*) + 141
11 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
12 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
13 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
14 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
15 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 19:: Chrome_CacheThread
0 libsystem_kernel.dylib 0x00007fff93a6deca kevent + 10
1 libbase.dylib 0x00000001056f3207 0x105641000 + 729607
2 libbase.dylib 0x00000001056f0b4b 0x105641000 + 719691
3 libbase.dylib 0x0000000105642fe9 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 393
4 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
5 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
6 libcontent.dylib 0x0000000106fd54a8 content::BrowserThreadImpl::CacheThreadRun(base::MessageLoop*) + 24
7 libcontent.dylib 0x0000000106fd562a content::BrowserThreadImpl::Run(base::MessageLoop*) + 154
8 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
9 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
10 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
11 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
12 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 20:: Chrome_IOThread
0 libsystem_kernel.dylib 0x00007fff93a6deca kevent + 10
1 libbase.dylib 0x00000001056f3207 0x105641000 + 729607
2 libbase.dylib 0x00000001056f0b4b 0x105641000 + 719691
3 libbase.dylib 0x0000000105642fe9 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 393
4 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
5 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
6 libcontent.dylib 0x0000000106fd5528 content::BrowserThreadImpl::IOThreadRun(base::MessageLoop*) + 24
7 libcontent.dylib 0x0000000106fd5637 content::BrowserThreadImpl::Run(base::MessageLoop*) + 167
8 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
9 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
10 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
11 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
12 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 21:: IndexedDB
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 libbase.dylib 0x00000001056440ff base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + 79
6 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
7 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
8 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
9 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
10 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
11 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 22:: CompositorTileWorker1/37123
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b6728 _pthread_cond_wait + 767
2 libcc.dylib 0x0000000106b76ff8 non-virtual thunk to cc::SingleThreadTaskGraphRunner::Run() + 56
3 libbase.dylib 0x00000001056bd6e3 base::DelegateSimpleThread::Run() + 19
4 libbase.dylib 0x00000001056bd3dd base::SimpleThread::ThreadMain() + 125
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 23:: handle-watcher-thread
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b6728 _pthread_cond_wait + 767
2 libmojo_system_impl.dylib 0x00000001098aca38 mojo::system::Waiter::Wait(unsigned long long, unsigned long*) + 216
3 libmojo_system_impl.dylib 0x000000010988e3e9 mojo::system::Core::WaitManyInternal(unsigned int const*, unsigned int const*, unsigned int, unsigned long long, unsigned int*, mojo::system::HandleSignalsState*) + 505
4 libmojo_system_impl.dylib 0x000000010988e1bf mojo::system::Core::Wait(unsigned int, unsigned int, unsigned long long, mojo::system::UserPointer<MojoHandleSignalsState>) + 79
5 libmojo_system_impl.dylib 0x0000000109883d7b MojoWait + 155
6 libmojo_message_pump_lib.dylib 0x0000000109874c99 mojo::common::MessagePumpMojo::WaitForReadyHandles(mojo::common::MessagePumpMojo::RunState const&) const + 41
7 libmojo_message_pump_lib.dylib 0x00000001098749eb mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*, base::MessagePump::Delegate*) + 139
8 libmojo_message_pump_lib.dylib 0x0000000109874931 mojo::common::MessagePumpMojo::Run(base::MessagePump::Delegate*) + 81
9 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
10 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
11 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
12 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
13 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
14 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
15 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 24:
0 libsystem_kernel.dylib 0x00007fff93a66fae semaphore_wait_trap + 10
1 libnode.dylib 0x000000010446f957 uv_sem_wait + 23 (thread.c:246)
2 com.github.electron.framework 0x0000000103431166 atom::NodeBindings::EmbedThreadRunner(void*) + 38 (node_bindings.cc:258)
3 libnode.dylib 0x000000010446f48d uv__thread_start + 61 (thread.c:49)
4 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
5 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
6 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 25:: AudioThread
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 libbase.dylib 0x00000001056440ff base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + 79
6 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
7 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
8 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
9 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
10 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
11 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 26:: BrowserBlockingWorker1/52535
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b6728 _pthread_cond_wait + 767
2 libbase.dylib 0x00000001056b9c1d base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) + 2333
3 libbase.dylib 0x00000001056b92bd base::SequencedWorkerPool::Worker::Run() + 125
4 libbase.dylib 0x00000001056bd3dd base::SimpleThread::ThreadMain() + 125
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 27:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 com.apple.Foundation 0x00007fff97053dd9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270
6 libbase.dylib 0x000000010564446e base::MessagePumpNSRunLoop::DoRun(base::MessagePump::Delegate*) + 126
7 libbase.dylib 0x0000000105643b44 0x105641000 + 11076
8 libbase.dylib 0x00000001056941e3 base::RunLoop::Run() + 99
9 libbase.dylib 0x000000010567b8fd base::MessageLoop::Run() + 29
10 libbase.dylib 0x00000001056bf218 base::Thread::ThreadMain() + 248
11 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
12 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
13 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
14 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 28:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff93a66f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff93a663b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9ad061c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9ad0568c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9ad04ed8 CFRunLoopRunSpecific + 296
5 com.apple.AppKit 0x00007fff8b3a6e99 _NSEventThread + 149
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 29:: CachePoolWorker1/73751
0 libsystem_kernel.dylib 0x00007fff93a6cdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a2b6728 _pthread_cond_wait + 767
2 libbase.dylib 0x00000001056b9c1d base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) + 2333
3 libbase.dylib 0x00000001056b92bd base::SequencedWorkerPool::Worker::Run() + 125
4 libbase.dylib 0x00000001056bd3dd base::SimpleThread::ThreadMain() + 125
5 libbase.dylib 0x00000001056b8b1c 0x105641000 + 490268
6 libsystem_pthread.dylib 0x00007fff9a2b599d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a2b591a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a2b3351 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007f9078e48d50 rbx: 0x00007fff5ca0aba8 rcx: 0x78325f7368707a2c rdx: 0x00007fff5ca0a968
rdi: 0x78325f7368707a2c rsi: 0x0000000000000000 rbp: 0x00007fff5ca0a7f0 rsp: 0x00007fff5ca0a7f0
r8: 0x00007fff5ca0ac88 r9: 0x0000000000000000 r10: 0x0000000000007d23 r11: 0x00000ff344704299
r12: 0x0000000000000000 r13: 0x000000010538e05f r14: 0x00000001032e52b0 r15: 0x00007f9079838c00
rip: 0x0000000106f3b544 rfl: 0x0000000000010202 cr2: 0x000021878e36d000
Logical CPU: 2
Error Code: 0x00000000
Trap Number: 13
```
|
https://github.com/electron/electron/issues/5180
|
https://github.com/electron/electron/pull/5191
|
a8032e8fefe803feabd5d0e7b1c09d31c1accfb4
|
eeccd904558d3a94d758a81d1a3b21dae5c5f071
| 2016-04-15T22:46:12Z |
c++
| 2016-04-18T06:13:41Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,164 |
["atom/browser/api/atom_api_app.cc", "atom/browser/browser.h", "atom/browser/browser_linux.cc", "atom/browser/browser_mac.mm", "atom/browser/browser_win.cc", "docs/api/app.md"]
|
Add `isDefaultProtocolClient` API
|
The new `setAsDefaultProtocolClient` and `removeAsDefaultProtocolClient` APIs are great, but without a way to query the current state, it's not possible to implement a UI element like this one. I think it'd be great to add `isDefaultProtocolClient`!
Also, I find the naming of these APIs pretty confusing. On Mac OS X and iOS `mailto` is referred to as a "URL Scheme", not a protocol (https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference), and it seems like that might be the case on Windows too. (https://msdn.microsoft.com/en-us/library/aa767914(v=vs.85).aspx)
It'd be nice to clarify that this is registering the app system-wide, while the other `protocol` module is only for handling requests initiated from within the app.
Maybe we could change these to `registerForURLScheme`, `isRegisteredForURLScheme`?
|
https://github.com/electron/electron/issues/5164
|
https://github.com/electron/electron/pull/5302
|
122652a3683d457b2721f2c48381b58a65500d43
|
d9db23185cba1bc7cedc3b73a56af3093812a726
| 2016-04-14T22:06:31Z |
c++
| 2016-04-28T07:13:06Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,163 |
["lib/browser/api/auto-updater/squirrel-update-win.js"]
|
autoUpdater.quitAndInstall does not restart when app.makeSingleInstance is used
|
- Electron version: 0.37.2
- Operating system: Window 7 x64
I'm doing auto update of app and run `autoUpdater.quitAndInstall()` on 'update-downloaded' event.
With using `app.makeSingleInstance` quiteAndInstall() will not start my app again, just quit.
Is it possible to fix?
|
https://github.com/electron/electron/issues/5163
|
https://github.com/electron/electron/pull/6037
|
f4c10060af0de64c47959a11cc6a46915776997b
|
b0f3443d72fcc6546d17736d7e45d3062479f4a5
| 2016-04-14T21:55:37Z |
c++
| 2016-06-14T05:59:40Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,150 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/native_window_mac.mm"]
|
Window: backgroundColor is not applied as I pass it in?
|
- Electron version: 0.37.5
- Operating system: Mac OS X 10.11.4
When I pass `backgroundColor: '#FF0000' to a window, the color that shows up on the screen is actually '#FF301E'.
|
https://github.com/electron/electron/issues/5150
|
https://github.com/electron/electron/pull/5155
|
64d37065bd0896d2457ce839e267c94687364c04
|
075da45b748bdcb8829dc9c0458b5995779b080f
| 2016-04-14T07:12:30Z |
c++
| 2016-04-14T23:48:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,148 |
["lib/renderer/override.js"]
|
Error message includes local PC user name and can be accessed by injected script on remote server
|
I found electron's error messages include install path and some electron apps for windows are installed into user's home directory.
This error message can be accessed by JavaScript on remote web site. It means arbitrary web site that is loaded on electron app can steal user names. Relative path should be used for error messages.
PoC
``` javascript
try{
alert(1,1);
}catch(e){
console.log(e.message);
e.message.match(/:\\Users\\(.*)\\AppData/);
alert(RegExp.$1);
}
```
Error Message
```
Could not call remote function ``. Check that the function signature is correct. Underlying error: Error processing argument at index 5, conversion failure from
Error: Could not call remote function ``. Check that the function signature is correct. Underlying error: Error processing argument at index 5, conversion failure from
at callFunction (C:\Users\harupuxa\AppData\Local\xxxxx\app-2.0.3\resources\atom.asar\browser\lib\rpc-server.js:205:11)
at EventEmitter.<anonymous> (C:\Users\harupuxa\AppData\Local\xxxxx\app-2.0.3\resources\atom.asar\browser\lib\rpc-server.js:295:12)
at emitMany (events.js:108:13)
at EventEmitter.emit (events.js:182:7)
at EventEmitter.<anonymous> (C:\Users\harupuxa\AppData\Local\xxxxx\app-2.0.3\resources\atom.asar\browser\api\lib\web-contents.js:133:25)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:172:7)
```
- Electron version: 0.37.5
- Operating system: Windows
|
https://github.com/electron/electron/issues/5148
|
https://github.com/electron/electron/pull/6038
|
b0f3443d72fcc6546d17736d7e45d3062479f4a5
|
12a35a05c695151cdb9b3fc16a59d0ae13a7c494
| 2016-04-14T03:30:33Z |
c++
| 2016-06-14T06:36:00Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,128 |
["atom/browser/api/atom_api_web_contents.cc", "lib/browser/api/web-contents.js", "spec/api-browser-window-spec.js"]
|
Race condition between WebContents `did-fail-load` and `did-finish-load` events
|
- Electron version: 0.37.5
- Operating system: Mac OS X 10.11.4
It’s not stated in the documentation, but Electron generally seems to guarantee that the `did-fail-load` event happens before the `did-finish-load` event on `WebContents`. However, if the failure is in _provisional_ loading, there is a race condition where `did-fail-load` can come after `did-finish-load`.
Test following Electron program will intermittently cause the problem, though I can’t find a way to reliably reproduce every time:
``` js
const electron = require('electron');
var mainWindow = null;
electron.app.on('ready', function() {
function logEvent(eventName) {
mainWindow.webContents.on(eventName, function() {
console.log(eventName, [].slice.call(arguments, 1));
});
}
mainWindow = new electron.BrowserWindow({width: 1000, height: 800});
logEvent('did-start-loading');
logEvent('did-fail-provisional-load');
logEvent('did-fail-load');
logEvent('did-finish-load');
mainWindow.loadURL('http://somewhere-that-does-not.exist');
});
```
Which _should_ give you output like:
```
did-start-loading []
did-fail-provisional-load [ -105, '', 'http://somewhere-that-does-not.exist/' ]
did-fail-load [ -105, '', 'http://somewhere-that-does-not.exist/' ]
did-finish-load []
```
But occasionally gives:
```
did-start-loading []
did-fail-provisional-load [ -105, '', 'http://somewhere-that-does-not.exist/' ]
did-finish-load []
did-fail-load [ -105, '', 'http://somewhere-that-does-not.exist/' ]
```
---
The issue seems to be caused by the fact that when there is a provisional loading error, `did-fail-provisional-load` simulates the `did-fail-load` event, but does so _later:_ https://github.com/electron/electron/blob/master/lib/browser/api/web-contents.js#L153, which appears to have been introduced in https://github.com/electron/electron/commit/1b3eb1cc5df74ed2dac3f8e7e0fea17497ddda28
Most of the time, the delay causes no problems, but occasionally the function that triggers `did-fail-load` gets scheduled after the `did-finish-load` event gets emitted. I ran across this issue while working on a change to Nightmare (an automated browser based on Electron) to better handle URL loading (https://github.com/segmentio/nightmare/pull/553). The tests would fail intermittently as a result.
There is an easy workaround (listen for both `did-fail-load` and `did-fail-provisional-load`; take action on the first one that occurs), but non-obvious—you’d have to do some spelunking in Electron’s code to understand what’s happening. Further, I don’t think users should really have to do this kind of extra effort if they don’t have a use-case that requires differentiating between provisional and normal loading failures. And, of course, `did-fail-provisional-load` is not even documented. (should it be?)
I can think of a few ways to address this:
1. Delay `loadURL` calls to the next tick (there are a few sites, but not too many, that would have to be addressed). This would be fairly easy on the JS side, not sure how simple on the C++ side.
2. Internally on the C++ side of `loadURL`, check whether it’s safe to take action or wait until it is. I have _no_ idea whether the relevant information to do this is even really available, let alone what the right calls to get it would be.
3. Delay emitting `did-finish-frame-load` and `did-finish-load` by a tick. I _think_ this would have to happen on the JS side to really ensure that the events can’t get queued before the synthetic `did-fail-load`, but I’m extremely sketchy on the particulars there.
4. Track the fact that `content::WebContentsObserver::DidFailProvisionalLoad` was received on the C++ side, but don’t emit a JS event until some later time just before `content::WebContentsObserver::DidFinishLoad` is received. Not sure on the ideal point in time there.
|
https://github.com/electron/electron/issues/5128
|
https://github.com/electron/electron/pull/5137
|
49d25693ee40a21aff43efd2c02bde0d8a8795b6
|
07572965dfc6cedb4b0125890fe6636e52d7c81c
| 2016-04-12T21:07:32Z |
c++
| 2016-04-13T11:12:50Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,120 |
["atom/browser/native_window.cc"]
|
Black background and frame on window with "frame: false" set
|
Found this issue on a project, tested against the electron-quick-start and found the problem still exists.
Simply adding "frame: false" to the new BrowserWindow() call will cause it.
- Electron version: 0.37.5
- Operating system: Windows
|
https://github.com/electron/electron/issues/5120
|
https://github.com/electron/electron/pull/5153
|
9e85cb4c110ce70963d6399479a49259295e7938
|
7501a02b34dbdb55ffe5415917afc34c0e11c419
| 2016-04-12T07:52:31Z |
c++
| 2016-04-14T11:05:35Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,111 |
["lib/browser/rpc-server.js", "lib/renderer/api/remote.js", "spec/api-ipc-spec.js", "spec/fixtures/module/rejected-promise.js"]
|
promise reject in remote not work
|
- Electron version:0.36.5
- Operating system: MAC OS 10.11.3
I upgrade my electron v0.36.3 to v0.37.5
example：
```
main process
getUserMe() {
if(this.authToken) {
return this.call('user.me').then(this._afterAuth);
}
return Promise.reject({
code: 400011,
error: 'invalid_refresh',
error_description: 'The refresh token is invalid.'
})
}
```
```
render process
let _service = remote.require('./main/service_export');
getUserMe() {
return _service.getUserMe()
.then((user) => {
return JSON.parse(user);
}).catch((err)=>{
console.log(err);
});
}
```
i can't get any return from promise reject . someone can help me thank!
|
https://github.com/electron/electron/issues/5111
|
https://github.com/electron/electron/pull/5666
|
9d924bb6d7b353278bc774c724cdbc8c4754a86a
|
cd444e82f9438d4475c34cca0dc89a7469e5a45c
| 2016-04-11T10:50:10Z |
c++
| 2016-05-24T04:30:25Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,097 |
["lib/browser/api/auto-updater/squirrel-update-win.js"]
|
autoUpdater.checkForUpdates() during an update emits an error on Windows
|
- Electron version: v0.37.3
- Operating system: Windows 10
Here's the stack trace that's included with the error event:
```
Command failed: 4294967295
System.AggregateException: One or more errors occurred.
---> System.Exception: Couldn't acquire lock, is another instance running
at Squirrel.SingleGlobalInstance..ctor(String key, TimeSpan timeOut)
at Squirrel.UpdateManager.<acquireUpdateLock>b__1e()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.<CheckForUpdate>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.Update.Program.<Download>d__5d.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at System.Threading.Tasks.Task`1.get_Result()
at Squirrel.Update.Program.executeCommandLine(String[] args)
at Squirrel.Update.Program.main(String[] args)
at Squirrel.Update.Program.Main(String[] args)
---> (Inner Exception #0) System.Exception: Couldn't acquire lock, is another instance running
at Squirrel.SingleGlobalInstance..ctor(String key, TimeSpan timeOut)
at Squirrel.UpdateManager.<acquireUpdateLock>b__1e()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.UpdateManager.<CheckForUpdate>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Squirrel.Update.Program.<Download>d__5d.MoveNext()<---
```
|
https://github.com/electron/electron/issues/5097
|
https://github.com/electron/electron/pull/5161
|
44bc24174c4f26d909014098246304b88bd6c845
|
cb947873c4cf4d6be06d59522e8686e8f25e8f97
| 2016-04-09T00:12:50Z |
c++
| 2016-04-15T11:10:03Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,094 |
["atom/browser/api/atom_api_web_contents.cc", "docs/api/web-contents.md"]
|
Add option to open devtools docked on right or bottom side.
|
- Electron version: v0.37.5
- Operating system: Any
It would be useful if we can open DevTools choosing all of it's available position: detached, docked right or docked bottom.
The new API could be something like this:
# webContents.openDevTools([options])
Opens the devtools.
- options Object (optional)
- mode String - ['detached' | 'right' | 'bottom'] . opens DevTools in specified position. Defaults to last used mode.
- detach Boolean - opens DevTools in a new window (deprecated, use mode: 'detached')
|
https://github.com/electron/electron/issues/5094
|
https://github.com/electron/electron/pull/5208
|
a3e8591a41b98fa0cd8a9cff9a344bb300bc9db7
|
d3bff7fffc58405848f0f39e2aa603756816e260
| 2016-04-08T19:06:48Z |
c++
| 2016-04-20T04:34:52Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,057 |
["lib/browser/api/auto-updater/auto-updater-win.js", "lib/browser/api/auto-updater/squirrel-update-win.js"]
|
auto-updater-win.js downloads updates twice when available.
|
- Electron version: 0.37.3
- Operating system: Windows
When you look at the code for auto-updater-win.js, `squirrelUpdate.download` gets called and if succesful then `squirrelUpdate.update` gets called too.
```
AutoUpdater.prototype.checkForUpdates = function () {
if (!this.updateURL) {
return this.emitError('Update URL is not set')
}
if (!squirrelUpdate.supported()) {
return this.emitError('Can not find Squirrel')
}
this.emit('checking-for-update')
squirrelUpdate.download(this.updateURL, (error, update) => {
if (error != null) {
return this.emitError(error)
}
if (update == null) {
return this.emit('update-not-available')
}
this.emit('update-available')
squirrelUpdate.update(this.updateURL, (error) => {
var date, releaseNotes, version
if (error != null) {
return this.emitError(error)
}
releaseNotes = update.releaseNotes
version = update.version
// Following information is not available on Windows, so fake them.
date = new Date()
this.emit('update-downloaded', {}, releaseNotes, version, date, this.updateURL, () => {
this.quitAndInstall()
})
})
})
}
```
These two calls in turn call Squirrel's `Update.exe --download` and `Update.exe --update`.
If you look at [Squirrel's source code](https://github.com/Squirrel/Squirrel.Windows/blob/master/src/Update/Program.cs), in both cases this will call `UpdateManager.DownloadReleases`, effectively downloading the whole release twice.
I may be wrong, but I think it could possibly be more efficient to just call `Update.exe --update` and that's it. Please let me know if I'm missing something.
|
https://github.com/electron/electron/issues/5057
|
https://github.com/electron/electron/pull/10483
|
928d2f78c363bb403e139d88263aa30e6d771c4c
|
945fef8a5a5a975a712c3560dad8cbec4fa3e350
| 2016-04-06T19:30:04Z |
c++
| 2017-09-27T17:26:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,051 |
["default_app/main.js", "spec/node-spec.js"]
|
process.stdout no longer output logs to terminal in renderer process
|
- Electron version: v0.37.3, v0.37.4
- Operating system: Mac OSX
This starts from 0.37.3, I used to output renderer console logs to terminal through `process.stdout.write`, it works very well in v0.37.2 and v0.36.*, but since v0.37.3 and the version above, it will not output my text to terminal, is this an expect behaviour or just a bug?
|
https://github.com/electron/electron/issues/5051
|
https://github.com/electron/electron/pull/6130
|
6d6f0cae62a4c78a6a44de2a3f27a5ad8fca013c
|
b74522d9f3a7cddcc2e60b5a809afdc86157a9f7
| 2016-04-06T10:13:23Z |
c++
| 2016-06-19T12:32:06Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,023 |
["atom/browser/net/atom_network_delegate.cc", "docs/api/session.md", "spec/api-web-request-spec.js"]
|
webRequest.onHeadersReceived doesn't obey "Location" redirects
|
- Electron version: v0.37.4
- Operating system: OSX 10.10.5
When _listening_ on [`onHeadersReceived`](https://github.com/electron/electron/blob/master/docs/api/session.md#seswebrequestonheadersreceivedfilter-listener), "Location" headers are no longer obeyed, and redirects are not followed, even when passing the original `responseHeaders` untouched. I'm not sure if this behaviour is intentional or a bug, it feels like the latter.
**Follows redirect:**
``` js
// Assuming the following
var win = new BrowserWindow({});
var sess = win.webContents.session;
// The page is loaded as expected
win.loadURL("http://bbc.co.uk");
```
**Does not follow redirect (ends early):**
``` js
// Same as above
var win = new BrowserWindow({});
var sess = win.webContents.session;
// But, this time, let's listen to `onHeadersReceived`
sess.webRequest.onHeadersReceived(function (details, callback) {
console.log(details.responseHeaders);
callback({cancel: false, responseHeaders: details.responseHeaders});
});
// The page is not loaded / the redirect is not obeyed...
win.loadURL("http://bbc.co.uk");
```
And below is the output of the `console.log`:
```
{ Connection: [ 'Keep-Alive' ],
'Content-Length': [ '0' ],
'Content-Type': [ 'text/html' ],
Date: [ 'Mon, 04 Apr 2016 21:32:18 GMT' ],
Location: [ 'http://www.bbc.co.uk/' ] }
```
|
https://github.com/electron/electron/issues/5023
|
https://github.com/electron/electron/pull/5030
|
056aaa2a62ea8fe875a8202578802b7485ee5cfd
|
5659ee5c0bb4996986e4b8effb2e89e0b7f9f656
| 2016-04-04T21:38:20Z |
c++
| 2016-04-11T11:04:32Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,022 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/atom_security_state_model_client.cc", "atom/browser/atom_security_state_model_client.h", "atom/browser/common_web_contents_delegate.cc", "atom/browser/common_web_contents_delegate.h", "atom/common/atom_constants.cc", "atom/common/atom_constants.h", "filenames.gypi"]
|
Dev Tools in Electron 0.37.3 Does Not Show SSL Cert Info in Security Tab
|
- Electron version: 0.37.3
- Operating system: OSX 10.11.4
So in Chrome, When you click on the green lock (github.com used as an example) and click the details link you are directed to the Security Tab in ChromeDevTools:
1. Details Link:
<img width="298" alt="secureconnectiondetailslinkinchrome" src="https://cloud.githubusercontent.com/assets/470705/14258268/95250fb2-fa56-11e5-9a60-e8b69f7ce698.png">
2. Security Tab in ChromeDevTools: <img width="464" alt="Security Tab in ChromeDevTools" src="https://cloud.githubusercontent.com/assets/470705/14258321/e161d284-fa56-11e5-826b-5ab3e287deb3.png">
Here's what happens when you view the Dev Tools Security Tab using Electron:
1. Note that using Electron there is no visibility into the Security Status of the Site's Cert. There is no visibility into the Secure TLS Connection and that the Site is using a 'strong protocol version and cipher suite' like Chrome displays. Nor is there any visibility in Dev Tools to Verify that Secure Resources 'are all served securely'. <img width="1042" alt="" src="https://cloud.githubusercontent.com/assets/470705/14258427/4fdccf02-fa57-11e5-8fc5-6ce842d7d475.png">
|
https://github.com/electron/electron/issues/5022
|
https://github.com/electron/electron/pull/5117
|
7501a02b34dbdb55ffe5415917afc34c0e11c419
|
64d37065bd0896d2457ce839e267c94687364c04
| 2016-04-04T20:21:17Z |
c++
| 2016-04-14T11:23:58Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,019 |
["spec/node-spec.js", "vendor/node"]
|
node version is 6.0.0-pre
|
- Electron version: 0.37.4
- Operating system: xubuntu 14.04 x64
``` js
process.versions.node
```
```
6.0.0-pre
```
It should be 5.10. Seems that my app is broken because some breaking changes in node major update
|
https://github.com/electron/electron/issues/5019
|
https://github.com/electron/electron/pull/5033
|
fa271204293865ee6ff3a7013659dca659bdd121
|
b48788af43ed8e9e94cc0bd0a86f28221cf9acc1
| 2016-04-04T14:44:49Z |
c++
| 2016-04-05T11:44:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,013 |
["atom/browser/api/atom_api_web_contents.cc", "docs-translations/ko-KR/api/web-contents.md", "docs-translations/zh-CN/api/web-contents.md", "docs/api/web-contents.md", "lib/renderer/web-view/guest-view-internal.js", "spec/api-browser-window-spec.js", "spec/fixtures/api/did-fail-load-iframe.html"]
|
Provide frame info in webContents `did-fail-load` event
|
The `did-fail-load` event on WebContents fires for other frames inside the main frame. It would be nice to get some information about whether the frame that failed was the main frame (as in the `did-frame-finish-load` event) or to not get this event at all if it didn’t happen in the main frame.
If I understand correctly, this is mainly a matter of checking whether the `RenderFrameHost` provided to the relevant callbacks in https://github.com/atom/electron/blob/e5aa712bf39178d89352332105c06d315dca0ca6/atom/browser/api/atom_api_web_contents.cc has a parent.
Happy to write a PR for this if someone can tell me which approach would be preferable (a boolean indicating mainFrame or just not having the event on child frames). Or some other approach.
- Electron version: 0.37.4
- Operating system: Mac OS X 10.11.4
|
https://github.com/electron/electron/issues/5013
|
https://github.com/electron/electron/pull/5029
|
7d3f8cb2223fdec784b0f565c9fad8c7913cb32f
|
82856eb0994246a56298c4bffd258c3bba9faf03
| 2016-04-04T07:01:37Z |
c++
| 2016-04-07T11:22:02Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 5,003 |
["spec/node-spec.js", "vendor/node"]
|
0.37.4: EXC_CRASH (SIGABRT)
|
- Electron version: 0.37.4
- Operating system: Mac OS 10.11.4
Right after startup of VS Code using Electron 0.37.4 I am presented with the following native crash:
```
Process: Electron Helper [7880]
Path: /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper
Identifier: com.github.electron.helper
Version: 0
Code Type: X86-64 (Native)
Parent Process: Electron [7762]
Responsible: Electron [7762]
User ID: 501
Date/Time: 2016-04-03 18:34:46.572 +0200
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: 3D5A7922-E0E0-4E9F-18BA-3E2F75C953A6
Sleep/Wake UUID: 4B340E88-BB4F-43C8-A342-1E8336477CB9
Time Awake Since Boot: 22000 seconds
Time Since Wake: 5600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrRendererMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Thread 0 Crashed:: CrRendererMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff829fff06 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff90a524ec pthread_kill + 90
2 libsystem_c.dylib 0x00007fff915a06e7 abort + 129
3 libnode.dylib 0x00000001072633b2 node::Buffer::CallbackInfo::CallbackInfo(v8::Isolate*, v8::Local<v8::ArrayBuffer>, void (*)(char*, void*), char*, void*) + 226
4 libnode.dylib 0x00000001072632c9 node::Buffer::CallbackInfo::CallbackInfo(v8::Isolate*, v8::Local<v8::ArrayBuffer>, void (*)(char*, void*), char*, void*) + 9
5 libnode.dylib 0x0000000107260e13 node::Buffer::CallbackInfo::New(v8::Isolate*, v8::Local<v8::ArrayBuffer>, void (*)(char*, void*), char*, void*) + 67
6 libnode.dylib 0x000000010725e6d8 node::Buffer::New(v8::Isolate*, char*, unsigned long) + 232
7 libnode.dylib 0x000000010725e5ab node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) + 219
8 libnode.dylib 0x000000010725ee7d node::Buffer::CreateFromString(v8::FunctionCallbackInfo<v8::Value> const&) + 205
9 libnode.dylib 0x00000001075d9ca3 v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 163
10 libnode.dylib 0x0000000107610c3e 0x107243000 + 3988542
11 libnode.dylib 0x000000010761f5eb 0x107243000 + 4048363
12 ??? 0x000038836d10c1fb 0 + 62137121686011
13 ??? 0x000038836d697b8b 0 + 62137127500683
14 ??? 0x000038836d6977d6 0 + 62137127499734
15 ??? 0x000038836d24ff81 0 + 62137123012481
16 ??? 0x000038836d10f6b7 0 + 62137121699511
17 ??? 0x000038836d13232f 0 + 62137121841967
18 ??? 0x000038836db934a2 0 + 62137132725410
19 ??? 0x000038836d10f6b7 0 + 62137121699511
20 ??? 0x000038836dd9dd09 0 + 62137134865673
21 ??? 0x000038836d136e64 0 + 62137121861220
22 ??? 0x000038836d119a62 0 + 62137121741410
23 libnode.dylib 0x00000001078542b0 0x107243000 + 6361776
24 libnode.dylib 0x0000000107853fa8 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 456
25 libnode.dylib 0x00000001075c016c v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) + 300
26 com.github.electron.framework 0x00000001051cdd50 0x10310c000 + 34348368
27 com.github.electron.framework 0x000000010519c8e0 0x10310c000 + 34146528
28 com.github.electron.framework 0x000000010519b31b 0x10310c000 + 34140955
29 com.github.electron.framework 0x000000010577310b 0x10310c000 + 40268043
30 com.github.electron.framework 0x000000010336231f 0x10310c000 + 2450207
31 com.github.electron.framework 0x0000000103362413 0x10310c000 + 2450451
32 com.github.electron.framework 0x0000000104b8a9d8 0x10310c000 + 27781592
33 com.github.electron.framework 0x00000001032ca5ca 0x10310c000 + 1828298
34 com.github.electron.framework 0x0000000104b833c0 0x10310c000 + 27751360
35 com.github.electron.framework 0x0000000104b821ee 0x10310c000 + 27746798
36 com.github.electron.framework 0x00000001032ca5ca 0x10310c000 + 1828298
37 com.github.electron.framework 0x00000001032e9149 0x10310c000 + 1954121
38 com.github.electron.framework 0x00000001032e991e 0x10310c000 + 1956126
39 com.github.electron.framework 0x00000001032c012d 0x10310c000 + 1786157
40 com.github.electron.framework 0x00000001032e0f8a 0x10310c000 + 1920906
41 com.github.electron.framework 0x00000001032bfb14 0x10310c000 + 1784596
42 com.apple.CoreFoundation 0x00007fff9675f881 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
43 com.apple.CoreFoundation 0x00007fff9673efbc __CFRunLoopDoSources0 + 556
44 com.apple.CoreFoundation 0x00007fff9673e4df __CFRunLoopRun + 927
45 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
46 com.apple.Foundation 0x00007fff8ecd5dd9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270
47 com.github.electron.framework 0x00000001032c07ce 0x10310c000 + 1787854
48 com.github.electron.framework 0x00000001032bff64 0x10310c000 + 1785700
49 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
50 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
51 com.github.electron.framework 0x0000000103e823e7 0x10310c000 + 14115815
52 com.github.electron.framework 0x0000000103878c5c 0x10310c000 + 7785564
53 com.github.electron.framework 0x0000000103878156 0x10310c000 + 7782742
54 com.github.electron.framework 0x000000010310db4d AtomMain + 77
55 com.github.electron.helper 0x0000000103102e56 main + 38
56 libdyld.dylib 0x00007fff818c35ad start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff82a00efa kevent_qos + 10
1 libdispatch.dylib 0x00007fff85b99165 _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff85b98dcd _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff82a005e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff90a4f578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff90a4d341 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff82a005e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff90a4f578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff90a4d341 start_wqthread + 13
Thread 4:
Thread 5:
Thread 6:: Chrome_ChildIOThread
0 libsystem_kernel.dylib 0x00007fff82a00eca kevent + 10
1 com.github.electron.framework 0x0000000103f9e147 0x10310c000 + 15278407
2 com.github.electron.framework 0x0000000103f9ba8b 0x10310c000 + 15268491
3 com.github.electron.framework 0x00000001032bf421 0x10310c000 + 1782817
4 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
5 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
6 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
7 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
8 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
9 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
10 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 7:: CompositorTileWorker1/18703
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 com.github.electron.framework 0x0000000103e34cb8 0x10310c000 + 13798584
3 com.github.electron.framework 0x0000000103319663 0x10310c000 + 2152035
4 com.github.electron.framework 0x00000001033194ad 0x10310c000 + 2151597
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 8:: CompositorTileWorker2/16471
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 com.github.electron.framework 0x0000000103e34cb8 0x10310c000 + 13798584
3 com.github.electron.framework 0x0000000103319663 0x10310c000 + 2152035
4 com.github.electron.framework 0x00000001033194ad 0x10310c000 + 2151597
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 9:: CompositorTileWorker3/15883
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 com.github.electron.framework 0x0000000103e34cb8 0x10310c000 + 13798584
3 com.github.electron.framework 0x0000000103319663 0x10310c000 + 2152035
4 com.github.electron.framework 0x00000001033194ad 0x10310c000 + 2151597
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 10:: CompositorTileWorker4/17231
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 com.github.electron.framework 0x0000000103e34cb8 0x10310c000 + 13798584
3 com.github.electron.framework 0x0000000103319663 0x10310c000 + 2152035
4 com.github.electron.framework 0x00000001033194ad 0x10310c000 + 2151597
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 11:: Compositor
0 libsystem_kernel.dylib 0x00007fff829f9f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff829f93b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9673f1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9673e68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
5 com.github.electron.framework 0x00000001032c04df 0x10310c000 + 1787103
6 com.github.electron.framework 0x00000001032bff64 0x10310c000 + 1785700
7 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
8 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
9 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
10 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
11 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 12:: handle-watcher-thread
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 com.github.electron.framework 0x00000001047065e8 0x10310c000 + 23045608
3 com.github.electron.framework 0x00000001046ef819 0x10310c000 + 22951961
4 com.github.electron.framework 0x00000001046ef5ef 0x10310c000 + 22951407
5 com.github.electron.framework 0x00000001046e652b 0x10310c000 + 22914347
6 com.github.electron.framework 0x00000001046d9459 0x10310c000 + 22860889
7 com.github.electron.framework 0x00000001046d925b 0x10310c000 + 22860379
8 com.github.electron.framework 0x00000001046d91a1 0x10310c000 + 22860193
9 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
10 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
11 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
12 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
13 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
14 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
15 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 13:: HTMLParserThread
0 libsystem_kernel.dylib 0x00007fff829f9f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff829f93b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9673f1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9673e68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
5 com.github.electron.framework 0x00000001032c04df 0x10310c000 + 1787103
6 com.github.electron.framework 0x00000001032bff64 0x10310c000 + 1785700
7 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
8 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
9 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
10 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
11 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff82a00eca kevent + 10
1 com.github.electron.framework 0x00000001031f664c atom::NodeBindingsMac::PollEvents() + 140
2 com.github.electron.framework 0x00000001031f538f atom::NodeBindings::EmbedThreadRunner(void*) + 63
3 libnode.dylib 0x000000010739e1b9 0x107243000 + 1421753
4 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
5 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
6 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 15:: WorkerPool/29443
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 libnode.dylib 0x000000010739e559 uv_cond_wait + 9
3 libnode.dylib 0x0000000107393023 0x107243000 + 1376291
4 libnode.dylib 0x000000010739e1b9 0x107243000 + 1421753
5 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
7 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 17:
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 libnode.dylib 0x000000010739e559 uv_cond_wait + 9
3 libnode.dylib 0x0000000107393023 0x107243000 + 1376291
4 libnode.dylib 0x000000010739e1b9 0x107243000 + 1421753
5 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
7 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 libnode.dylib 0x000000010739e559 uv_cond_wait + 9
3 libnode.dylib 0x0000000107393023 0x107243000 + 1376291
4 libnode.dylib 0x000000010739e1b9 0x107243000 + 1421753
5 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
7 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a50728 _pthread_cond_wait + 767
2 libnode.dylib 0x000000010739e559 uv_cond_wait + 9
3 libnode.dylib 0x0000000107393023 0x107243000 + 1376291
4 libnode.dylib 0x000000010739e1b9 0x107243000 + 1421753
5 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
7 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 20:
0 libsystem_kernel.dylib 0x00007fff829f9f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff829f93b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9673f1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9673e68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
5 com.apple.CoreFoundation 0x00007fff9677f9b1 CFRunLoopRun + 97
6 libnode.dylib 0x00000001073a1cc6 0x107243000 + 1436870
7 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
8 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
9 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 21:: WorkerPool/38215
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 22:: DedicatedWorker Thread
0 libsystem_kernel.dylib 0x00007fff829f9f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff829f93b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9673f1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9673e68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
5 com.github.electron.framework 0x00000001032c04df 0x10310c000 + 1787103
6 com.github.electron.framework 0x00000001032bff64 0x10310c000 + 1785700
7 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
8 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
9 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
10 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
11 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 23:: DedicatedWorker Thread
0 libsystem_kernel.dylib 0x00007fff829f9f72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff829f93b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9673f1c4 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9673e68c __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9673ded8 CFRunLoopRunSpecific + 296
5 com.github.electron.framework 0x00000001032c04df 0x10310c000 + 1787103
6 com.github.electron.framework 0x00000001032bff64 0x10310c000 + 1785700
7 com.github.electron.framework 0x00000001032f9de3 0x10310c000 + 2022883
8 com.github.electron.framework 0x00000001032e88ed 0x10310c000 + 1951981
9 com.github.electron.framework 0x0000000103319e88 0x10310c000 + 2154120
10 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
11 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
12 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
13 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 24:: WorkerPool/42043
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 25:: WorkerPool/41299
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 26:: WorkerPool/47107
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 27:: WorkerPool/47363
0 libsystem_kernel.dylib 0x00007fff829ffdb6 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff90a5075e _pthread_cond_wait + 821
2 com.github.electron.framework 0x000000010330903b 0x10310c000 + 2084923
3 com.github.electron.framework 0x000000010331b78d 0x10310c000 + 2160525
4 com.github.electron.framework 0x000000010331bc44 0x10310c000 + 2161732
5 com.github.electron.framework 0x0000000103315f1c 0x10310c000 + 2137884
6 libsystem_pthread.dylib 0x00007fff90a4f99d _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff90a4f91a _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff90a4d351 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5cafb0c8 rdx: 0x0000000000000000
rdi: 0x000000000000050f rsi: 0x0000000000000006 rbp: 0x00007fff5cafb0f0 rsp: 0x00007fff5cafb0c8
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x00007fff740af000 r15: 0x00007fd1ec0602a8
rip: 0x00007fff829fff06 rfl: 0x0000000000000206 cr2: 0x00007fff74254008
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
Binary Images:
0x103102000 - 0x103102fff +com.github.electron.helper (0) <5A31A538-10DE-3E6B-BA3C-700B3953DBFA> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS/Electron Helper
0x10310c000 - 0x1069a7ee7 +com.github.electron.framework (0) <ACA9AD94-579C-36CE-9E4B-729ABCE68B00> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
0x107107000 - 0x10711cff7 +com.github.Squirrel (1.0 - 1) <C39DE518-902E-3EBE-B1A6-B4E7AE668521> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Squirrel.framework/Versions/A/Squirrel
0x10713d000 - 0x1071a0ff7 +org.reactivecocoa.ReactiveCocoa (1.0 - 1) <701B20DE-3ADD-3643-B52A-E05744C30DB3> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/ReactiveCocoa.framework/Versions/A/ReactiveCocoa
0x107216000 - 0x10722afff +org.mantle.Mantle (1.0 - ???) <31915DD6-48E6-3706-A076-C9D4CE17F4F6> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Mantle.framework/Versions/A/Mantle
0x107243000 - 0x107f61fff +libnode.dylib (0) <E207AC45-8F53-38F3-BFB4-AFB3A5DCF50B> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib
0x1083ce000 - 0x108607fef +libffmpeg.dylib (0) <6F49E894-75FB-39E3-B530-B09F13B1EA98> /Applications/Visual Studio Code - Alpha.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib
0x1087a2000 - 0x1087d9fff com.apple.audio.midi.CoreMIDI (1.10 - 88) <51E79766-51D8-3A95-A7FD-18E7E11528F3> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x108803000 - 0x10881cfff libexpat.1.dylib (12.40.1) <405B65BE-42E4-36FA-AA41-5B717CB3F5E7> /usr/lib/libexpat.1.dylib
0x10cb46000 - 0x10cb4fff7 +keymapping.node (???) <5220F9EE-50EF-3C88-9160-487EAA143B76> /Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/node_modules/native-keymap/build/Release/keymapping.node
0x1149b0000 - 0x114a02fff +onig_scanner.node (???) <CD780998-E857-3B80-9698-1EED0DF456CF> /Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/node_modules/vscode-textmate/node_modules/oniguruma/build/Release/onig_scanner.node
0x7fff68f57000 - 0x7fff68f8e0d7 dyld (360.21) <D9B236BC-4AC1-325F-B3EF-3F06DBDA7119> /usr/lib/dyld
0x7fff80857000 - 0x7fff808dffff com.apple.CoreSymbolication (3.1 - 58048.1) <4730422E-4178-34F9-8550-BB92F2A4F44B> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x7fff808e6000 - 0x7fff808f2ff7 com.apple.OpenDirectory (10.11 - 194) <31A67AD5-5CC2-350A-96D7-821DF4BC4196> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff808f3000 - 0x7fff808f6ff7 libCoreFSCache.dylib (119.5) <2389D7DA-B8EF-3EB4-AAAF-FBEDE01CDECA> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0x7fff808f7000 - 0x7fff8098dfff com.apple.ColorSync (4.9.0 - 4.9.0) <8FC37E20-6579-3CB2-9D49-BC39FC38DF87> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff8098e000 - 0x7fff8098efff com.apple.Cocoa (6.11 - 22) <807787AB-D231-3F51-A99B-A9314623C571> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff81231000 - 0x7fff8123cfff com.apple.CrashReporterSupport (10.11 - 717) <474544AD-1199-3ECC-90E5-071847BA72C6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
0x7fff8123d000 - 0x7fff81282ff7 com.apple.coreservices.SharedFileList (24.4 - 24.5) <1D2AD77B-778F-3253-A295-3D0A32A8121C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
0x7fff81283000 - 0x7fff815feffb com.apple.VideoToolbox (1.0 - 1731.15.202) <B839BE14-9503-3B5E-A54A-C7FCEED34EA3> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff816c4000 - 0x7fff816cfff7 libcommonCrypto.dylib (60075.40.2) <B9D08EB8-FB35-3F7B-8A1C-6FCE3F07B7E7> /usr/lib/system/libcommonCrypto.dylib
0x7fff817a7000 - 0x7fff817a7fff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <054DFE32-737D-3211-9A14-0FC5E1A880E3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff818c0000 - 0x7fff818c3ffb libdyld.dylib (360.21) <8390E026-F7DE-3C32-9486-3DFF6BD131B0> /usr/lib/system/libdyld.dylib
0x7fff818c4000 - 0x7fff81a8afe7 com.apple.ImageIO.framework (3.3.0 - 1444) <54F18254-F31B-3464-BB51-BAF9E9620419> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff81a8b000 - 0x7fff81afafff com.apple.datadetectorscore (7.0 - 460) <8EF4EECC-4FF1-36DF-84CF-65545555A225> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff81b62000 - 0x7fff81b71ffb com.apple.LangAnalysis (1.7.0 - 1.7.0) <18D21123-A3E7-3851-974A-08E5D4540475> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff81e59000 - 0x7fff81e5efff com.apple.TCC (1.0 - 1) <50F7EC60-5B21-3B9B-BF2F-F037EA7B12FB> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff81ebb000 - 0x7fff81eeaff7 com.apple.DictionaryServices (1.2 - 250.3) <30250542-CBAA-39C1-91AA-B57A5DE17594> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff81fd9000 - 0x7fff820feff7 com.apple.LaunchServices (728.8 - 728.8) <FDA38B17-82E2-322F-A008-B9207A6EA668> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff820ff000 - 0x7fff8220dff3 com.apple.desktopservices (1.10.3 - 1.10.3) <3A6906D4-C0B8-30D1-B589-0466E5E42B69> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x7fff8222c000 - 0x7fff82240fe3 libCGInterfaces.dylib (317.9) <5079DE4F-3717-32FF-B76A-77F53236D17D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
0x7fff82241000 - 0x7fff82251fff libbsm.0.dylib (34) <7E14504C-A8B0-3574-B6EB-5D5FABC72926> /usr/lib/libbsm.0.dylib
0x7fff82252000 - 0x7fff82260fff com.apple.opengl (12.0.40 - 12.0.40) <AEA28993-BA3E-3E0F-A2F5-88C312ABB634> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff82261000 - 0x7fff82263fff libsystem_coreservices.dylib (19.2) <1B3F5AFC-FFCD-3ECB-8B9A-5538366FB20D> /usr/lib/system/libsystem_coreservices.dylib
0x7fff82277000 - 0x7fff8227afff com.apple.Mangrove (1.0 - 1) <2D86B3AD-64C3-3BB4-BC66-1CFD0C90E844> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove
0x7fff8227b000 - 0x7fff82354fff com.apple.CoreMedia (1.0 - 1731.15.202) <D2A49E52-9D26-35A8-BDDC-3BCDBEC5A19E> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff82364000 - 0x7fff82386ff7 com.apple.Sharing (442.13.6 - 442.13.6) <DDD2811C-6ECB-32F2-8EE1-69BF9657B4A8> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
0x7fff82622000 - 0x7fff82696ff7 com.apple.Heimdal (4.0 - 2.0) <5D365381-8B5E-3259-8867-FC4A7D307BDE> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff82697000 - 0x7fff826aefff libmarisa.dylib (4) <E4919B03-D9BD-3AF8-B436-C415C98E3F0A> /usr/lib/libmarisa.dylib
0x7fff826fb000 - 0x7fff82702ff7 libcompiler_rt.dylib (62) <A13ECF69-F59F-38AE-8609-7B731450FBCD> /usr/lib/system/libcompiler_rt.dylib
0x7fff827a2000 - 0x7fff827aafff com.apple.NetFS (6.0 - 4.0) <842A5346-24C3-3F22-9ECF-E586A10EA1F2> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff827ab000 - 0x7fff827bcfff libSparseBLAS.dylib (1162.2) <EBEB3848-3468-342A-91A6-5C47F2369CD9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
0x7fff827dd000 - 0x7fff827f9ff7 libextension.dylib (78) <FD952DA6-BBEC-3CB6-98B3-E1D111C5C54E> /usr/lib/libextension.dylib
0x7fff82801000 - 0x7fff82809fff libMatch.1.dylib (27) <3AC0BFB8-7E69-3DBE-A175-7F3946FC4554> /usr/lib/libMatch.1.dylib
0x7fff8280a000 - 0x7fff8282cfff com.apple.IconServices (68.1 - 68.1) <CDEEDBE6-F53B-3BA1-82D4-23BCA3DD8949> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
0x7fff82884000 - 0x7fff828b2ff7 com.apple.CoreServicesInternal (248.2 - 248.2) <6E111F0A-D7F1-3738-ADE7-CF983BD4EC8B> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
0x7fff828e8000 - 0x7fff828ecfff libGIF.dylib (1444) <D3F44A33-355E-3154-A465-1C732AAC5F75> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff82936000 - 0x7fff82937fff libDiagnosticMessagesClient.dylib (100) <4243B6B4-21E9-355B-9C5A-95A216233B96> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff82938000 - 0x7fff829e8fff com.apple.backup.framework (1.7.4 - 1.7.4) <F304E9D1-991A-379E-9659-BF85C35B4808> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff829e9000 - 0x7fff82a07ff7 libsystem_kernel.dylib (3248.40.184) <88C17B7F-1CD8-3979-A1A9-F7BDB4FCE789> /usr/lib/system/libsystem_kernel.dylib
0x7fff82a45000 - 0x7fff82a53ff7 libbz2.1.0.dylib (38) <28E54258-C0FE-38D4-AB76-1734CACCB344> /usr/lib/libbz2.1.0.dylib
0x7fff83962000 - 0x7fff83a12fe7 libvMisc.dylib (563.5) <6D73C20D-D1C4-3BA5-809B-4B597C15AA86> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x7fff83a8a000 - 0x7fff83a8efff com.apple.CommonPanels (1.2.6 - 96) <4AE7E5AE-55B3-37FA-9BDE-B23147ADA2E9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x7fff83a8f000 - 0x7fff83a98ff3 libsystem_notify.dylib (150.40.1) <D48BDE34-0F7E-34CA-A0FF-C578E39987CC> /usr/lib/system/libsystem_notify.dylib
0x7fff83a99000 - 0x7fff83aa1fff com.apple.CoreServices.FSEvents (1223.10.1 - 1223.10.1) <7F5B7A23-BC1D-3FA9-A9B8-D534F1E1979A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
0x7fff83b0c000 - 0x7fff83b81fff com.apple.framework.IOKit (2.0.2 - 1179.40.20) <FB2AD43B-905D-3BD0-BE17-ACE7D4D13E24> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff83b82000 - 0x7fff83ce9fff libBLAS.dylib (1162.2) <A1398FE0-39D2-33EA-9A0F-B2644EEA29A0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff83cef000 - 0x7fff83cf4fff com.apple.DiskArbitration (2.7 - 2.7) <F55902AA-5316-3255-A701-FDED5B553065> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff84127000 - 0x7fff8419bff3 com.apple.securityfoundation (6.0 - 55126) <1F6BDF18-3CF0-3E85-8D9B-0663599B9949> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff8419d000 - 0x7fff8419fff7 libRadiance.dylib (1444) <A5EFA292-AFD4-3FCE-8802-958AD60F75DA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff841a0000 - 0x7fff841a1fff libsystem_blocks.dylib (65) <1244D9D5-F6AA-35BB-B307-86851C24B8E5> /usr/lib/system/libsystem_blocks.dylib
0x7fff84368000 - 0x7fff843b4fff com.apple.print.framework.PrintCore (11.2 - 472.2) <5AE8AA6B-CE09-397D-B0D4-0F9CCBF1F77D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x7fff843b5000 - 0x7fff843baff3 libunwind.dylib (35.3) <F6EB48E5-4D12-359A-AB54-C937FBBE9043> /usr/lib/system/libunwind.dylib
0x7fff843bb000 - 0x7fff84750fdb com.apple.vImage (8.0 - 8.0) <4BAC9B6F-7482-3580-8787-AB0A5B4D331B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff84773000 - 0x7fff8477efff libGL.dylib (12.0.40.6) <4FC6D3F9-6582-3E7D-A7D1-E035F0E26697> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff84a1b000 - 0x7fff84a1bff7 liblaunch.dylib (765.40.36) <1CD7619D-AF2E-34D1-8EC6-8021CF473D9B> /usr/lib/system/liblaunch.dylib
0x7fff84a1c000 - 0x7fff84a2ffff com.apple.CoreBluetooth (1.0 - 1) <E54CA9A2-A5C6-30C5-9D6E-8472DBA9371E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
0x7fff84a33000 - 0x7fff84a84ff7 libcups.2.dylib (435.1) <4198A94D-A46C-39AA-92B6-83D0BA507D6C> /usr/lib/libcups.2.dylib
0x7fff84e58000 - 0x7fff84ea3ff7 com.apple.CoreMediaIO (703.0 - 4791) <B974A225-61C6-34DD-AC2A-495BD6A393B3> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
0x7fff84f04000 - 0x7fff84f20fff com.apple.GenerationalStorage (2.0 - 239.1) <8C821448-4294-3736-9CEF-467C93785CB9> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
0x7fff84f2d000 - 0x7fff84fc2fff com.apple.ink.framework (10.9 - 214) <1F76CF36-3F79-36B8-BC37-C540AF34B338> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff84fc3000 - 0x7fff85005ff7 com.apple.Metal (56.6 - 56.6) <7DCBE573-B713-3C50-A16E-2F33A84C3CFB> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
0x7fff85006000 - 0x7fff85009fff libsystem_sandbox.dylib (460.40.33) <30671DCC-265F-325A-B33D-11CD336B3DA3> /usr/lib/system/libsystem_sandbox.dylib
0x7fff855c2000 - 0x7fff855c2fff libmetal_timestamp.dylib (600.0.44.1) <6576F284-BACA-332A-A6E7-FA1C347636E3> /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib
0x7fff855c3000 - 0x7fff855c9ff7 com.apple.speech.recognition.framework (5.1.1 - 5.1.1) <9E5A980A-F455-32D5-BBEE-3BD6018CC45E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff857bb000 - 0x7fff857dffff com.apple.MultitouchSupport.framework (304.10.2 - 304.10.2) <CE75EDA3-2B22-3968-834E-550EA870ECC8> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff857e0000 - 0x7fff857fbff7 libCRFSuite.dylib (34) <078B4CD8-6A8C-3067-B2BA-0C2A0BAB8AC3> /usr/lib/libCRFSuite.dylib
0x7fff85b8b000 - 0x7fff85b90fff com.apple.MediaAccessibility (1.0 - 79) <C5E61B45-1967-3602-A48C-31E132B998B2> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
0x7fff85b91000 - 0x7fff85bbefff libdispatch.dylib (501.40.12) <C7499857-61A5-3D7D-A5EA-65DCC8C3DF92> /usr/lib/system/libdispatch.dylib
0x7fff85bbf000 - 0x7fff85c66fff com.apple.LanguageModeling (1.0 - 1) <58C18A47-BDE7-3CBE-81C0-797029D170A1> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
0x7fff864a0000 - 0x7fff864a0fff libOpenScriptingUtil.dylib (169.1) <AD0DAC8A-9849-3077-999F-9AEC6112BDAB> /usr/lib/libOpenScriptingUtil.dylib
0x7fff86545000 - 0x7fff865e5fff com.apple.Metadata (10.7.0 - 972.29.1) <F19E0200-6937-3799-9C67-D26C2CE5AA5F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x7fff865e6000 - 0x7fff86651ff7 com.apple.framework.CoreWLAN (11.0 - 1101.20) <3B35C543-7FCE-333F-80C1-432FA41DDCDE> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff86bae000 - 0x7fff86bc5ff7 libsystem_coretls.dylib (83.40.5) <C90DAE38-4082-381C-A185-2A6A8B677628> /usr/lib/system/libsystem_coretls.dylib
0x7fff86bc6000 - 0x7fff86bc8fff com.apple.loginsupport (1.0 - 1) <9B2F5F9B-ED38-313F-B798-D2B667BCD6B5> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
0x7fff86bc9000 - 0x7fff86d13ff7 com.apple.coreui (2.1 - 366.1) <A3868F31-ACF4-3EA5-9E75-79ED44FA7F06> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff86dda000 - 0x7fff86ddcff7 libquarantine.dylib (80) <0F4169F0-0C84-3A25-B3AE-E47B3586D908> /usr/lib/system/libquarantine.dylib
0x7fff86ddd000 - 0x7fff86de8fff com.apple.AppSandbox (4.0 - 261.40.2) <52766210-B6EB-3B73-AB1B-42E0A9AD2EE8> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
0x7fff87316000 - 0x7fff8733fffb libRIP.A.dylib (957) <5F18F20D-5921-3314-A9F8-F1B1CB62C83D> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fff87347000 - 0x7fff87388ff7 libGLU.dylib (12.0.40.6) <C56DDF90-CF6D-30D2-A3E6-89288BE69DCB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff874d3000 - 0x7fff8755cff7 com.apple.PerformanceAnalysis (1.0 - 1) <608E8C50-6F59-3FEB-B822-D9B02F328716> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
0x7fff8755d000 - 0x7fff8755dfff libenergytrace.dylib (10.40.1) <0A491CA7-3451-3FD5-999A-58AB4362682B> /usr/lib/libenergytrace.dylib
0x7fff877cf000 - 0x7fff87815ff7 libauto.dylib (186) <999E610F-41FC-32A3-ADCA-5EC049B65DFB> /usr/lib/libauto.dylib
0x7fff87816000 - 0x7fff8782bfff com.apple.AppContainer (4.0 - 261.40.2) <F220E702-1C00-3BD2-9943-C7E75C3B4418> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
0x7fff8782f000 - 0x7fff87867ff7 com.apple.RemoteViewServices (2.0 - 101) <B2881449-8CFE-3D1C-B4BF-155640392533> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
0x7fff87942000 - 0x7fff87970ff7 libsandbox.1.dylib (460.40.33) <26158471-870A-3269-9E2B-7D7963B8E9F3> /usr/lib/libsandbox.1.dylib
0x7fff87a70000 - 0x7fff87c91ff7 com.apple.CoreImage (11.4.0 - 366.4.19) <6EE4A686-50C8-3D77-A036-BE8AA0F8A2FD> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x7fff87c92000 - 0x7fff87ca3ff7 libsystem_trace.dylib (201.10.3) <25104542-5251-3E8D-B14A-9E37207218BC> /usr/lib/system/libsystem_trace.dylib
0x7fff88088000 - 0x7fff880ebfff libAVFAudio.dylib (161.2) <1A98DBF3-490B-37FB-928A-AB1E36E6E5DD> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Resources/libAVFAudio.dylib
0x7fff8813a000 - 0x7fff8815fff7 libPng.dylib (1444) <47ACF98D-B5F1-3A03-B6FD-4107D5FAE5E9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff88162000 - 0x7fff88167ff7 libheimdal-asn1.dylib (453.40.10) <981DE40B-FA16-36F7-BE92-8C8A115D6CD9> /usr/lib/libheimdal-asn1.dylib
0x7fff88168000 - 0x7fff8816dfff com.apple.ImageCapture (9.0 - 9.0) <ACECF0B7-7D92-3A22-BF47-E8FADF4C5378> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x7fff881a9000 - 0x7fff881b4ff7 libChineseTokenizer.dylib (16) <79B8C67A-3061-3C78-92CD-4650719E68D4> /usr/lib/libChineseTokenizer.dylib
0x7fff887f3000 - 0x7fff888e2ffb libxml2.2.dylib (29.5) <4096C2EA-6659-3F22-AC60-1E2F30BDD2B7> /usr/lib/libxml2.2.dylib
0x7fff88941000 - 0x7fff88949fff libGFXShared.dylib (12.0.40.6) <1CDE5AEF-3E44-3547-879E-BB490EE7702C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff8897e000 - 0x7fff889b8fff com.apple.QD (3.12 - 302) <0FE53180-2895-3D14-A1E7-F82DE1D106E1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x7fff88f40000 - 0x7fff88f49ff7 com.apple.CommonAuth (4.0 - 2.0) <4B8673E1-3697-3FE2-8D30-AC7AC5D4F8BF> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff88f4d000 - 0x7fff88f4dfff com.apple.ApplicationServices (48 - 48) <ADD57D3A-142F-3EF5-BFD8-EACD82164884> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff88f4e000 - 0x7fff88ff2fff com.apple.Bluetooth (4.4.4 - 4.4.4f4) <BCF89EFE-853D-3AEA-AE31-DC8293C7284F> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff88ff3000 - 0x7fff892e8fff com.apple.HIToolbox (2.1.1 - 807.2) <871E5223-5D03-3649-98AF-9CCA3B41E307> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff892e9000 - 0x7fff892f1fff libcopyfile.dylib (127) <A48637BC-F3F2-34F2-BB68-4C65FD012832> /usr/lib/system/libcopyfile.dylib
0x7fff89302000 - 0x7fff89730fff com.apple.vision.FaceCore (3.3.1 - 3.3.1) <E54028EA-4217-3078-A2B1-C52E4214D59E> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
0x7fff89731000 - 0x7fff8993cfff libFosl_dynamic.dylib (16.24) <5F9DB82D-FD4B-3952-8531-CE020F93ED49> /usr/lib/libFosl_dynamic.dylib
0x7fff8993d000 - 0x7fff89bd7fff com.apple.security (7.0 - 57337.40.85) <7C5B8DEF-3D02-3410-9BD3-2B1251F84D4B> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff89bd8000 - 0x7fff8a130ff7 com.apple.MediaToolbox (1.0 - 1731.15.202) <A19F9D25-5333-3AA0-90FB-97F3F420A7EA> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
0x7fff8a40f000 - 0x7fff8a476fff com.apple.framework.CoreWiFi (11.0 - 1101.20) <993592F1-B3F1-3FAD-87BD-EA83C361BCCF> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
0x7fff8a477000 - 0x7fff8a4c6ff7 com.apple.opencl (2.7.0 - 2.7.0) <307263BA-0368-38C9-A7FB-25920343D0DF> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff8a63d000 - 0x7fff8a66efff com.apple.GSS (4.0 - 2.0) <B490333A-3B3E-397A-AD75-68846E9A9140> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff8a66f000 - 0x7fff8a677fef libsystem_platform.dylib (74.40.2) <29A905EF-6777-3C33-82B0-6C3A88C4BA15> /usr/lib/system/libsystem_platform.dylib
0x7fff8a678000 - 0x7fff8a6c6ff7 libstdc++.6.dylib (104.1) <76E2AFB1-07E5-3F19-B692-F6E21B7E470D> /usr/lib/libstdc++.6.dylib
0x7fff8a757000 - 0x7fff8a770fff com.apple.CFOpenDirectory (10.11 - 194) <11F95672-55E0-3F9D-9171-5E8C56AEE948> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff8bb93000 - 0x7fff8bbcdff7 com.apple.DebugSymbols (132 - 132) <23A42C53-B941-3871-9EE2-4C87A46005B5> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x7fff8bbce000 - 0x7fff8bbd9fff libkxld.dylib (3248.40.184) <6F776D34-D06C-3C48-B753-D0FB375A4A8A> /usr/lib/system/libkxld.dylib
0x7fff8bc04000 - 0x7fff8bc0cffb libsystem_dnssd.dylib (625.40.20) <86A05653-DCA0-3345-B29F-F320029AA05E> /usr/lib/system/libsystem_dnssd.dylib
0x7fff8bcd7000 - 0x7fff8bcf4ff7 com.apple.AppleVPAFramework (2.1.2 - 2.1.2) <F4AF2363-B28E-3097-AB1E-FDA1C92F8F56> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA
0x7fff8c5c6000 - 0x7fff8c6eafff libsqlite3.dylib (216.4) <280D67B8-F93D-3587-A146-19F36C817548> /usr/lib/libsqlite3.dylib
0x7fff8c6fe000 - 0x7fff8c6feff7 libkeymgr.dylib (28) <8371CE54-5FDD-3CE9-B3DF-E98C761B6FE0> /usr/lib/system/libkeymgr.dylib
0x7fff8c6ff000 - 0x7fff8c72effb libsystem_m.dylib (3105) <08E1A4B2-6448-3DFE-A58C-ACC7335BE7E4> /usr/lib/system/libsystem_m.dylib
0x7fff8c9fa000 - 0x7fff8ca58fff com.apple.SystemConfiguration (1.14 - 1.14) <10082F58-6190-3A7C-8B6C-C12B16DC793A> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff8ca59000 - 0x7fff8ca63fff com.apple.NetAuth (6.0 - 6.0) <D692B1EF-534F-3892-8E2F-2BBA7C8AFD74> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff8cafb000 - 0x7fff8ced3fef com.apple.CoreAUC (214.0.0 - 214.0.0) <F80C19CA-6CD0-3052-9C22-0288A257CCC8> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
0x7fff8ced4000 - 0x7fff8ced6fff libCGXType.A.dylib (957) <B901C222-E779-32EB-96C2-5A707A09FC5B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x7fff8ced7000 - 0x7fff8cf4efeb libcorecrypto.dylib (335.40.8) <9D300121-CAF8-3894-8774-DF38FA65F238> /usr/lib/system/libcorecrypto.dylib
0x7fff8cf52000 - 0x7fff8cf79fff com.apple.ChunkingLibrary (167 - 167) <AD7F285C-005E-36BB-98A3-5826413533BE> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
0x7fff8d0b9000 - 0x7fff8d0bcfff libspindump.dylib (197.1) <48F4C673-9F0C-38BE-B550-88241E812518> /usr/lib/libspindump.dylib
0x7fff8d0bd000 - 0x7fff8d0c1fff libpam.2.dylib (20) <CFCD19BD-87BC-3F2B-BB1C-4C23E8E55F1A> /usr/lib/libpam.2.dylib
0x7fff8d0c2000 - 0x7fff8d0c2fff com.apple.Carbon (154 - 157) <8F6ED602-5943-3E29-A793-BC331E2C183D> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff8d118000 - 0x7fff8d16bff7 libc++.1.dylib (120.1) <8FC3D139-8055-3498-9AC5-6467CB7F4D14> /usr/lib/libc++.1.dylib
0x7fff8d16c000 - 0x7fff8d178fff com.apple.speech.synthesis.framework (5.4.12 - 5.4.12) <71DA00B8-5EA2-326B-8814-59DB25512F65> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff8d1a6000 - 0x7fff8d296fff libJP2.dylib (1444) <27371567-A122-3217-ADA0-3A446EF6A3E9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff8d297000 - 0x7fff8d2cbff7 com.apple.CoreVideo (1.8 - 191.3) <1AA24A1B-CB84-3F6B-B6DE-11494542649C> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff8d2cc000 - 0x7fff8d2e8ff7 libsystem_malloc.dylib (67.40.1) <5748E8B2-F81C-34C6-8B13-456213127678> /usr/lib/system/libsystem_malloc.dylib
0x7fff8d34c000 - 0x7fff8d362fff com.apple.CoreMediaAuthoring (2.2 - 953) <06C2E0E2-BA5C-3BB1-8DD7-55613EDD654D> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring
0x7fff8d363000 - 0x7fff8d3d1ff7 com.apple.ApplicationServices.ATS (377 - 394.3) <847DBFBA-8D6B-367B-99FD-C6CAA8C05C65> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x7fff8d3f5000 - 0x7fff8d3f7ff7 libsystem_configuration.dylib (802.40.13) <3DEB7DF9-6804-37E1-BC83-0166882FF0FF> /usr/lib/system/libsystem_configuration.dylib
0x7fff8d408000 - 0x7fff8d45dfff com.apple.AE (701 - 701) <AD492742-F884-386B-A450-FAC281B9FFA4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x7fff8d4b5000 - 0x7fff8d661fff com.apple.avfoundation (2.0 - 1046.9.11) <DE524245-B7EF-3E9D-8AA1-3D99A3304EF4> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
0x7fff8d662000 - 0x7fff8d68bff7 libxpc.dylib (765.40.36) <2CC7CF36-66D4-301B-A6D8-EBAE7405B008> /usr/lib/system/libxpc.dylib
0x7fff8dd66000 - 0x7fff8de62ff7 libFontParser.dylib (158.5) <62796E99-36B7-36B6-8D33-5349F88014C3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff8de63000 - 0x7fff8de66fff com.apple.IOSurface (108.2.1 - 108.2.1) <A0037B0A-277A-393E-9BF6-688595BD564D> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff8dfce000 - 0x7fff8e330f3f libobjc.A.dylib (680) <7489D2D6-1EFD-3414-B18D-2AECCCC90286> /usr/lib/libobjc.A.dylib
0x7fff8e357000 - 0x7fff8e63cffb com.apple.CoreServices.CarbonCore (1136.2 - 1136.2) <2DBAFC9A-6CD6-351D-B1F4-87D81AA6D640> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x7fff8e6fd000 - 0x7fff8e703fff com.apple.XPCService (2.0 - 1) <5E2122D6-FFA2-3552-BF16-9FD3F36B40DB> /System/Library/PrivateFrameworks/XPCService.framework/Versions/A/XPCService
0x7fff8e704000 - 0x7fff8e8d2ff3 com.apple.QuartzCore (1.11 - 410.14) <0283748A-8318-36AC-8B30-8A951FEB305A> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff8e8d3000 - 0x7fff8e8edfff com.apple.Kerberos (3.0 - 1) <1B4744BF-E5AE-38E2-AA56-E22D3270F2E8> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff8e8ee000 - 0x7fff8ea94ff7 com.apple.audio.toolbox.AudioToolbox (1.13 - 1.13) <082319FC-59F2-3D36-AC9B-94759724E302> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff8ecb1000 - 0x7fff8f005fff com.apple.Foundation (6.9 - 1258) <51833143-6CAE-3E1C-9FBA-BCDEB48D4ADF> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8f006000 - 0x7fff8f02afff libJPEG.dylib (1444) <AECB826C-8B14-3D04-8DEC-33EE85F5150D> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff8f02b000 - 0x7fff8f03cfff libcmph.dylib (6) <BA4BF2C6-7F4E-33B8-9DD7-619C9EB83ECF> /usr/lib/libcmph.dylib
0x7fff8f044000 - 0x7fff8f044ff7 libunc.dylib (29) <DDB1E947-C775-33B8-B461-63E5EB698F0E> /usr/lib/system/libunc.dylib
0x7fff8f047000 - 0x7fff8f077ff3 com.apple.CoreAVCHD (5.8.0 - 5800.4.2) <4AAFB1C4-3708-30F9-ACFA-90564347204C> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
0x7fff8f078000 - 0x7fff8f0d5fff com.apple.CoreServices.OSServices (728.8 - 728.8) <4CE49D8A-8304-3347-9379-6075CB906419> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x7fff8f2a1000 - 0x7fff8f310fff com.apple.SearchKit (1.4.0 - 1.4.0) <F159A888-34CA-36F1-AC8E-EB1B38C9DFB3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x7fff8f31c000 - 0x7fff8f338ff3 libresolv.9.dylib (60) <A650B5C8-1950-36A0-86D1-0B2465318BFA> /usr/lib/libresolv.9.dylib
0x7fff9048c000 - 0x7fff9048dff3 com.apple.print.framework.Print (10.0 - 266) <3E85F70C-D7D4-34E1-B88A-C1F503F99CDA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x7fff9048e000 - 0x7fff904dfff7 com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <3D62A9B3-67A8-3F8A-A102-05E310249075> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff90a16000 - 0x7fff90a17fff liblangid.dylib (122) <9CC4F0D1-5C51-3B69-BC8F-EE3A51FD0822> /usr/lib/liblangid.dylib
0x7fff90a4c000 - 0x7fff90a55ff7 libsystem_pthread.dylib (138.10.4) <3DD1EF4C-1D1B-3ABF-8CC6-B3B1CEEE9559> /usr/lib/system/libsystem_pthread.dylib
0x7fff90b4a000 - 0x7fff90b69ff7 com.apple.framework.Apple80211 (11.0 - 1121.34) <AE7795B8-4590-3714-999D-3FBFF6BF5D93> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff90be0000 - 0x7fff90bf9fff com.apple.openscripting (1.7.1 - 169.1) <36EBF6A7-334A-3197-838F-E8C7B27FCDBB> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x7fff90dd6000 - 0x7fff90df0ff3 liblzma.5.dylib (10) <CC03591B-FA57-3CA5-AC81-0D76033AC0CE> /usr/lib/liblzma.5.dylib
0x7fff90f88000 - 0x7fff90f88fff com.apple.Accelerate (1.10 - Accelerate 1.10) <185EC96A-5AF0-3620-A4ED-4D3654D25B39> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff90f89000 - 0x7fff90fd5ffb com.apple.HIServices (1.22 - 549) <E4E1BD10-F475-3E19-9E0B-A5071D158F47> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x7fff90fd6000 - 0x7fff910c8ff7 libiconv.2.dylib (44) <F05A0A5A-92A9-3668-8F20-F27CBDA26BE9> /usr/lib/libiconv.2.dylib
0x7fff91197000 - 0x7fff911dcff3 libFontRegistry.dylib (155.1) <F3355C6E-ED33-3506-B10E-2F6995D34BC1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff911e9000 - 0x7fff913f6fff libicucore.A.dylib (551.51) <35315A29-E21C-3CC5-8BD6-E07A3AE8FC0D> /usr/lib/libicucore.A.dylib
0x7fff913fa000 - 0x7fff91406fff com.apple.SpeechRecognitionCore (2.2.7 - 2.2.7) <6BA06290-D4A3-351C-87F9-B61EF61FF055> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
0x7fff91407000 - 0x7fff9141eff7 libsystem_asl.dylib (323.40.3) <007F9094-317A-33EA-AF62-BAEAAB48C0F7> /usr/lib/system/libsystem_asl.dylib
0x7fff91446000 - 0x7fff9146ffff libsystem_info.dylib (477.40.5) <6B01C09E-A3E5-3C71-B370-D0CABD11A436> /usr/lib/system/libsystem_info.dylib
0x7fff91470000 - 0x7fff91475ff7 libmacho.dylib (875.1) <318264FA-58F1-39D8-8285-1F6254EE410E> /usr/lib/system/libmacho.dylib
0x7fff914c8000 - 0x7fff914c9fff libsystem_secinit.dylib (20) <32B1A8C6-DC84-3F4F-B8CE-9A52B47C3E6B> /usr/lib/system/libsystem_secinit.dylib
0x7fff914ca000 - 0x7fff9151aff7 com.apple.Symbolication (1.4 - 58044) <F70BF765-FBE9-3F1E-85CA-BB2F8E53E8C2> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
0x7fff91542000 - 0x7fff915cffff libsystem_c.dylib (1082.20.4) <CDEBF2BB-A578-30F5-846F-96274951C3C5> /usr/lib/system/libsystem_c.dylib
0x7fff91631000 - 0x7fff917affff com.apple.UIFoundation (1.0 - 436.1) <AABB5267-E7B7-3D75-B051-E665BDA8DEF4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7fff917d7000 - 0x7fff91864dd7 com.apple.AppleJPEG (1.0 - 1) <558ACADA-C41F-3EEF-82A0-C2D7B13C5428> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
0x7fff9187a000 - 0x7fff9187cfff libCVMSPluginSupport.dylib (12.0.40.6) <4AA6710A-6267-3062-BFF2-27DB5E6B5892> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
0x7fff919d4000 - 0x7fff919e2fff libxar.1.dylib (302) <03207F66-2C4A-3DBD-8D81-70F4C85903C4> /usr/lib/libxar.1.dylib
0x7fff919eb000 - 0x7fff919f1fff com.apple.IOAccelerator (205.3 - 205.3) <851B6BF8-5B7F-3FB5-9E45-10AAE3BF7438> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x7fff91c62000 - 0x7fff91c63ffb libSystem.B.dylib (1226.10.1) <CD307E99-FC5C-3575-BCCE-0C861AA63124> /usr/lib/libSystem.B.dylib
0x7fff91c8e000 - 0x7fff91cc0ff7 libTrueTypeScaler.dylib (158.5) <EA63B45B-22D3-3546-9BD6-EEEB7F1B48B6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
0x7fff91ced000 - 0x7fff91d16fff libc++abi.dylib (125) <DCCC8177-3D09-35BC-9784-2A04FEC4C71B> /usr/lib/libc++abi.dylib
0x7fff91d17000 - 0x7fff91d55ff7 libGLImage.dylib (12.0.40.6) <734B133F-E789-3A25-9DE6-1CCBA4896D4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff92737000 - 0x7fff92737fff com.apple.CoreServices (728.9 - 728.9) <78CB3EAC-A66E-3FD9-A1DF-A9CF227ED3C3> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff9281f000 - 0x7fff93a6afeb com.apple.CoreGraphics (1.600.0 - 957) <8C9F8E1A-274C-36CE-93FB-49906A9B9EE2> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff93a6b000 - 0x7fff93b7afe7 libvDSP.dylib (563.5) <9AB6CA3C-4F0E-35E6-9184-9DF86E7C3DAD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x7fff93b7b000 - 0x7fff93bd7fff libTIFF.dylib (1444) <2A22E6B7-213B-3253-838F-C3EC3C8F2727> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff93bd8000 - 0x7fff93be0fff libsystem_networkextension.dylib (385.40.36) <66095DC7-6539-38F2-95EE-458F15F6D014> /usr/lib/system/libsystem_networkextension.dylib
0x7fff93c9f000 - 0x7fff93cb0ff7 libz.1.dylib (61.20.1) <B3EBB42F-48E3-3287-9F0D-308E04D407AC> /usr/lib/libz.1.dylib
0x7fff93d0e000 - 0x7fff93d10ff7 com.apple.securityhi (9.0 - 55006) <A4CEFD45-C51C-381C-A57B-FF75D90C680F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x7fff93d11000 - 0x7fff93f98ff7 com.apple.CFNetwork (760.4.2 - 760.4.2) <24C4A390-3079-358A-8D51-75A3E818A6DF> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff93f99000 - 0x7fff93febfff com.apple.AppleVAFramework (5.0.32 - 5.0.32) <FC1AED2C-B3E2-31D9-B163-37989CD8A073> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff9435e000 - 0x7fff94361ffb libScreenReader.dylib (426.42) <16FC79D1-4573-3E90-945F-CBA22D5185FD> /usr/lib/libScreenReader.dylib
0x7fff9479d000 - 0x7fff9479dfff com.apple.audio.units.AudioUnit (1.13 - 1.13) <93C1D642-37D4-3692-AD35-DCAD04F9610B> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff947b3000 - 0x7fff947c9ff7 libLinearAlgebra.dylib (1162.2) <FFE54EDF-F06F-3C0A-864A-4CA7BBFD4B2D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
0x7fff9480e000 - 0x7fff94ab4ff7 com.apple.CoreData (120 - 641.3) <A29A5491-6169-372B-828F-84EE0CFD4BC4> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff94c61000 - 0x7fff94c62ffb libremovefile.dylib (41) <552EF39E-14D7-363E-9059-4565AC2F894E> /usr/lib/system/libremovefile.dylib
0x7fff94cde000 - 0x7fff94ce0fff com.apple.xpc.ServiceManagement (1.0 - 1) <F3E14561-5DF4-3429-98ED-8F27A87A343A> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
0x7fff94d26000 - 0x7fff94d29fff libCoreVMClient.dylib (119.5) <560D70FB-709F-3030-96C9-F249FCB7DA6D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff94da5000 - 0x7fff959cefff com.apple.AppKit (6.9 - 1404.46) <2492D315-76B6-320B-B542-231FCA44CA48> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff95a20000 - 0x7fff95a86ff7 libsystem_network.dylib (583.40.20) <269E5ADD-6922-31E2-8D55-7B777263AC0D> /usr/lib/system/libsystem_network.dylib
0x7fff95cc4000 - 0x7fff95cc7ff7 com.apple.help (1.3.3 - 46) <35DA4D48-0BC2-35A1-8D7C-40905CDF4F64> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x7fff95e25000 - 0x7fff960bbfff libmecabra.dylib (696.5) <EF6C0BD4-5FE8-34FB-8ADF-69A53CEC97A9> /usr/lib/libmecabra.dylib
0x7fff960bc000 - 0x7fff960e7ffb libarchive.2.dylib (33.20.2) <6C370A21-63FD-3A68-B4B3-5333F24B770B> /usr/lib/libarchive.2.dylib
0x7fff960e8000 - 0x7fff96215ff3 com.apple.CoreText (352.0 - 494.11) <08E8640E-6602-3A00-BC28-94235FD311B4> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff96256000 - 0x7fff96258fff com.apple.SecCodeWrapper (4.0 - 261.40.2) <1F832591-59A8-3B3F-943F-D6D827463782> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper
0x7fff962c7000 - 0x7fff962f0ff7 libxslt.1.dylib (14.1) <27DE3F2E-CE96-3327-A563-788EE3E2775B> /usr/lib/libxslt.1.dylib
0x7fff962f1000 - 0x7fff96309fef libcompression.dylib (28) <E7601B62-1053-369D-8A9E-91CF86239220> /usr/lib/libcompression.dylib
0x7fff9652f000 - 0x7fff96533fff libcache.dylib (75) <9548AAE9-2AB7-3525-9ECE-A2A7C4688447> /usr/lib/system/libcache.dylib
0x7fff9655c000 - 0x7fff966a1fff com.apple.QTKit (7.7.3 - 2943.3) <88AA19A7-7170-3798-8CBA-B1B8D4763ADB> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff966b5000 - 0x7fff96b2bfff com.apple.CoreFoundation (6.9 - 1258.1) <943A1383-DA6A-3DC0-ABCD-D9AEB3D0D34D> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff96c19000 - 0x7fff97015fff libLAPACK.dylib (1162.2) <987E42B0-5108-3065-87F0-9DF7616A8A06> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
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: 12219
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=311.4M resident=0K(0%) swapped_out_or_unallocated=311.4M(100%)
Writable regions: Total=445.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=445.8M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Activity Tracing 2048K 2
CG shared images 144K 6
CoreAnimation 8K 2
CoreUI image file 160K 3
Dispatch continuations 16.0M 2
IOKit 43.0M 65
Kernel Alloc Once 8K 3
MALLOC 84.9M 39
MALLOC guard page 32K 7
Memory Tag 255 1.7G 197
Memory Tag 255 (reserved) 768K 4 reserved VM address space (unallocated)
STACK GUARD 56.1M 27
Stack 139.8M 51
Stack (reserved) 1040K 3 reserved VM address space (unallocated)
Stack Guard 8K 3
VM_ALLOCATE 34.5M 95
__DATA 23.2M 219
__IMAGE 528K 2
__LINKEDIT 100.6M 14
__TEXT 210.8M 222
__UNICODE 552K 2
mapped file 154.4M 26
shared memory 22.4M 14
=========== ======= =======
TOTAL 2.5G 985
TOTAL, minus reserved VM space 2.5G 985
```
I can try to reproduce with a locally built version of Electron with symbols to find out more of the stack, but thought I would file this in case the stack rings any bell.
|
https://github.com/electron/electron/issues/5003
|
https://github.com/electron/electron/pull/5033
|
fa271204293865ee6ff3a7013659dca659bdd121
|
b48788af43ed8e9e94cc0bd0a86f28221cf9acc1
| 2016-04-03T16:39:22Z |
c++
| 2016-04-05T11:44:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,985 |
["atom/browser/api/atom_api_web_contents.cc", "atom/common/color_util.cc"]
|
Blinking / Flashing while loading
|
- Electron version: 0.37.3
- Operating system: Windows 10 x64
Hello, is there a way do turn off the white flash while loading a site?
|
https://github.com/electron/electron/issues/4985
|
https://github.com/electron/electron/pull/4995
|
8bc95fe279e7af30c9d14527ca835ff991e57de3
|
e5aa712bf39178d89352332105c06d315dca0ca6
| 2016-04-01T10:18:07Z |
c++
| 2016-04-03T02:14:27Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,938 |
["docs/api/web-view-tag.md"]
|
openExternal allows a malicious script to execute arbitrary local files
|
Since addEventListener with 'new-window' can receive file: scheme, this code will allows a remote user to execute arbitrary local files via injected window.open().
https://github.com/atom/electron/blob/master/docs/api/web-view-tag.md#event-new-window
> webview.addEventListener('new-window', function(e) {
> require('electron').shell.openExternal(e.url);
> });
This script in wevbiew with event listener described above could execute calc.exe:
`
window.open('c:/windows/system32/calc.exe')
`
I tested it with electron v0.37.2 on windows.
I think this sample code should validate e.url before execution with openExternal or file: scheme should be prohibited on openExternal.
|
https://github.com/electron/electron/issues/4938
|
https://github.com/electron/electron/pull/4959
|
ccbbf3569624091c3f8ecece197fd5c8538bb802
|
9e2dd13f9a746d6281311a41a4916a63363d9200
| 2016-03-29T16:17:33Z |
c++
| 2016-03-31T22:41:33Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,937 |
["docs/faq/electron-faq.md"]
|
electron-v0.37.3-win32-ia32 webpage background color is black
|
- Electron version:electron-v0.37.3-win32-ia32
- Operating system:windows 10 x64
|
https://github.com/electron/electron/issues/4937
|
https://github.com/electron/electron/pull/4941
|
664f59a8ebb947db19a504ac7d7fdaead8f9a7e4
|
7dbf07edfc9cde8325d212a01dfe9f634f8fb5d2
| 2016-03-29T15:18:17Z |
c++
| 2016-03-29T23:31:51Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,936 |
["lib/browser/api/dialog.js"]
|
dialog: passing undefined as callback has unexpected behaviour from renderer
|
- Electron version: 0.35.6
- Operating system: all
I would assume that a call to `remote.dialog.showSaveDialog()` with `undefined` or `null` as 3rd argument for the callback would make the call a sync call as opposed to an async call. However I notice that passing `undefined` as callback lets the renderer hang in a weird state.
|
https://github.com/electron/electron/issues/4936
|
https://github.com/electron/electron/pull/4969
|
b2ad0a05d71e69d8d81dd0c4164ef6ec132c82da
|
ef08138a8dc29c00b9fe7b27def5e7239bfa5b0a
| 2016-03-29T13:53:53Z |
c++
| 2016-04-01T23:11:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,928 |
["atom/browser/net/url_request_fetch_job.cc"]
|
Crash when running tests with devtools opened
|
- Electron version: v0.37.x
- Operating system: All
Steps:
1. run `script/test.py`
2. open devtools
3. Electron crashed after running a few tests
Stack trace:
```
Crashed Thread: 17 Chrome_IOThread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
Thread 17 Crashed:: Chrome_IOThread
0 libnet.dylib 0x000000010f5fca1f net::URLRequestJob::GatherRawReadStats(net::Error, int) + 63
1 libnet.dylib 0x000000010f5fc958 net::URLRequestJob::ReadRawDataComplete(int) + 232
2 com.github.electron.framework 0x00000001089d7b91 atom::URLRequestFetchJob::DataAvailable(net::IOBuffer*, int) + 369 (url_request_fetch_job.cc:189)
3 com.github.electron.framework 0x00000001089d8092 atom::(anonymous namespace)::ResponsePiper::Write(net::IOBuffer*, int, base::Callback<void (int)> const&) + 82 (url_request_fetch_job.cc:62)
4 libnet.dylib 0x000000010f5e7870 0x10f39f000 + 2394224
5 libnet.dylib 0x000000010f5e74f5 0x10f39f000 + 2393333
6 libnet.dylib 0x000000010f5fc9b6 net::URLRequestJob::ReadRawDataComplete(int) + 326
7 libnet.dylib 0x000000010f50610c net::HttpCache::Transaction::DoLoop(int) + 2092
8 libnet.dylib 0x000000010f49fd9c 0x10f39f000 + 1052060
9 libnet.dylib 0x000000010f49ffa4 0x10f39f000 + 1052580
10 libbase.dylib 0x000000010b0cc93a base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&) + 202
11 libbase.dylib 0x000000010b0f61c9 base::MessageLoop::RunTask(base::PendingTask const&) + 489
12 libbase.dylib 0x000000010b0f6818 base::MessageLoop::DoWork() + 632
13 libbase.dylib 0x000000010b0bd031 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 465
14 libbase.dylib 0x000000010b10e1e3 base::RunLoop::Run() + 99
15 libbase.dylib 0x000000010b0f58fd base::MessageLoop::Run() + 29
16 libcontent.dylib 0x000000010ca55378 content::BrowserThreadImpl::IOThreadRun(base::MessageLoop*) + 24
17 libcontent.dylib 0x000000010ca55487 content::BrowserThreadImpl::Run(base::MessageLoop*) + 167
18 libbase.dylib 0x000000010b139218 base::Thread::ThreadMain() + 248
19 libbase.dylib 0x000000010b132b1c 0x10b0bb000 + 490268
20 libsystem_pthread.dylib 0x00007fff8a5d3c13 _pthread_body + 131
21 libsystem_pthread.dylib 0x00007fff8a5d3b90 _pthread_start + 168
22 libsystem_pthread.dylib 0x00007fff8a5d1375 thread_start + 13
```
|
https://github.com/electron/electron/issues/4928
|
https://github.com/electron/electron/pull/4929
|
07fc0880fbec810875c81a425fae990fca81bed0
|
293ca4ef559f92c090c670309062f4a9dc8112d8
| 2016-03-27T12:44:28Z |
c++
| 2016-03-31T10:37:28Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,925 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/api/atom_api_web_contents.h", "docs/api/browser-window.md", "script/lib/config.py", "spec/static/main.js"]
|
Disable throttling of requestAnimationFrame
|
The `--disable-renderer-backgrounding` command line switch only disables throttling for timers, there is currently no way to disable throttling of `requestAnimationFrame`.
Refs https://github.com/atom/electron/issues/4317#issuecomment-190990964.
|
https://github.com/electron/electron/issues/4925
|
https://github.com/electron/electron/pull/5086
|
d169ebf7371865a3b486b0b15db50b02d3ec6af1
|
5ff97317fed93768a69bb25be19bd013c6d05aac
| 2016-03-27T02:43:38Z |
c++
| 2016-04-08T07:25:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,919 |
["docs/api/app.md"]
|
app.getLocale() returnes '' on windows.
|
- Electron version: 0.37.2
- Operating system: Windows 7
On windows I see the empty string as a result of `app.getLocale()` if I invoke it before the `ready` event.
Should it be in docs?
|
https://github.com/electron/electron/issues/4919
|
https://github.com/electron/electron/pull/4965
|
996ad103445cc60ff5e9b056c13eb72475926986
|
303290bfb4dc25d4ddf1eb7ee26b9fd6bf822680
| 2016-03-25T21:37:57Z |
c++
| 2016-03-31T08:38:39Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,906 |
["atom/app/atom_main_delegate.cc", "atom/utility/atom_content_utility_client.cc", "atom/utility/atom_content_utility_client.h", "chromium_src/chrome/utility/printing_handler_win.cc", "chromium_src/chrome/utility/printing_handler_win.h", "script/lib/config.py", "vendor/brightray"]
|
webContents.print doesn't do anything on Windows 7
|
- Electron version: 0.37.2
- Operating system: Windows 7 64-bit
I have tried to call `mainWindow.webContents.print`, which showed the printer dialog but when I choose the printer, it just does nothing. Not even an error.
I have tried with multiple printers such as physical and virtual one (like print to XPS/PDF).
I suspect its my code, so I tried this [this example](https://github.com/hokein/electron-sample-apps/tree/master/printing) as well but I got same result.
After that I tested it on another computer (Microsoft surface 4) and still nothing.
Then I run the same code on Mac OS, and it was working ok.
So I'm confusing right now and wondering if anybody else have same issue or not...
PS: `webContents.printToPDF` was also okay on windows since I guess has nothing to do with OS printing functionality.
|
https://github.com/electron/electron/issues/4906
|
https://github.com/electron/electron/pull/5152
|
47cc390e41afaa3f78ac1a34cac3ca6a2fad096a
|
9e85cb4c110ce70963d6399479a49259295e7938
| 2016-03-24T17:25:33Z |
c++
| 2016-04-14T10:22:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,905 |
["script/create-dist.py"]
|
ffmpeg library for linux is not stripped in the ffmpeg binaries archive
|
- Electron version: all
- Operating system: Linux
The library in the electron binaries archive is stripped. Download electron-v0.37.2-linux-x64.zip and ffmpeg-v0.37.2-linux-x64.zip. Extract both archive and check the libffmpeg.so. In the electron archive it is stripped, but not in the ffmpeg archive. Shouldn't it be stripped?
|
https://github.com/electron/electron/issues/4905
|
https://github.com/electron/electron/pull/5668
|
cd444e82f9438d4475c34cca0dc89a7469e5a45c
|
994cc620312310f6be55c80508dcc716286b2676
| 2016-03-24T13:50:50Z |
c++
| 2016-05-24T04:33:09Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,879 |
["atom/browser/api/atom_api_web_view_manager.cc", "atom/browser/web_contents_preferences.cc", "atom/browser/web_view_manager.cc", "atom/browser/web_view_manager.h", "lib/renderer/web-view/web-view.js", "spec/fixtures/pages/visibilitychange.html", "spec/fixtures/pages/webview-visibilitychange.html", "spec/webview-spec.js"]
|
<webview>'s visibilityState is always "visible" and doesn't receive visibilitychange events
|
- Electron version: 0.37.2
- Operating system: OS X 10.11.3
https://github.com/atom/electron/pull/4700 added support for the `visibilitychange` event (thank you @zcbenz!), but that event doesn't make its way into `<webview>`s, which are always "visible" regardless of their host page's `document.visibilityState`.
Tested using the following setup
Host page:
``` coffee
console.log "<webview> host page initial visibilityState =", document.visibilityState
document.addEventListener "visibilitychange", ->
console.log "<webview> host page visibilitychange event, visibilityState =", document.visibilityState
```
`<webview>`:
``` coffee
console.log "<webview> initial visibilityState =", document.visibilityState
addEventListener "visibilitychange", ->
console.log "<webview> visibilitychange, visibilityState =", document.visibilityState
setInterval ->
console.log "<webview> visibilityState =", document.visibilityState
, 3000
```
Host page logs:
```
<webview> host page initial visibilityState = visible
<webview> host page visibilitychange event, visibilityState = hidden
<webview> host page visibilitychange event, visibilityState = visible
```
`<webview>` logs:
```
<webview> initial visibilityState = visible
(24) <webview> visibilityState = visible
```
|
https://github.com/electron/electron/issues/4879
|
https://github.com/electron/electron/pull/5684
|
fa1246ccf78df4169176e12706abab9fd229bfcd
|
4ea7602871f871441e20847271466d23739c7059
| 2016-03-22T15:23:31Z |
c++
| 2016-05-26T01:07:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,870 |
["atom/common/api/atom_api_v8_util.cc", "atom/renderer/atom_render_view_observer.cc"]
|
Webview Crashes with IPC message
|
Hello,
First of all Thanks for the awesome work on electron, while trying to upgrade our app, we found webview is crashing, upon digging our logging mechanism which logs all object properties going into prototype chain was causing webview to crash. we have given minimal code to reproduce the effect.
0.37.x appends a <empty-string> key with each ipc message. when we encounter that key webview crashes.
Sample app can be found in the below git url, working fine in < 0.37.x
```
https://github.com/kamesh-a/electron-samples/tree/master/0.37.2_webview_crash
```
- Electron version: 0.37.x
- Operating system: Mac and Windows
|
https://github.com/electron/electron/issues/4870
|
https://github.com/electron/electron/pull/4892
|
afb82fcc1fca8712b9228327fb0c98e8c3ed7655
|
c307478d5d484e798480b68ded3f76778252315e
| 2016-03-21T14:03:46Z |
c++
| 2016-03-31T01:22:23Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,857 |
["atom/browser/api/atom_api_app.cc", "atom/browser/browser.h", "atom/browser/browser_linux.cc", "atom/browser/browser_mac.mm", "atom/browser/browser_win.cc", "docs/api/app.md"]
|
API: Register Electron App as Protocol Handler
|
There's no simple, cross-platform way to register protocol handlers in Electron. Every OS requires a different solution. This seems like something that Electron should smooth over.
There's already a W3C API for this: [`Navigator.registerProtocolHandler`](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler). Can Electron implement it?
|
https://github.com/electron/electron/issues/4857
|
https://github.com/electron/electron/pull/4896
|
0e3737423b111a10de8ea55c397bd50a1154bc6f
|
c220753c605f51973f53403e83443dfb51c20e4d
| 2016-03-20T00:26:57Z |
c++
| 2016-03-31T01:38:57Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,842 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/api/atom_api_web_contents.h", "lib/browser/api/web-contents.js", "vendor/brightray"]
|
Developer tools: does not pause execution at `debugger`
|
- Electron version: 0.37.2
- Operating system: OS X (El Capitan 10.11.3)
If you use `debugger` it will not pause the execution of the program. If I downgrade to electron version `0.36.x`, then it works.
Same happens when you set up breakpoints in the Developer Tools.
|
https://github.com/electron/electron/issues/4842
|
https://github.com/electron/electron/pull/5119
|
c9a3fc4317496d32b8ede116f85367f4ed48dee5
|
313883b1fc86fb522b605007a28011ba0d63699c
| 2016-03-18T13:58:44Z |
c++
| 2016-04-12T08:57:27Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,825 |
["atom/browser/api/atom_api_app.cc", "atom/browser/api/atom_api_app.h", "atom/browser/api/atom_api_session.cc", "atom/browser/api/atom_api_session.h", "atom/browser/atom_browser_context.cc", "atom/browser/atom_browser_context.h", "docs/api/app.md", "docs/api/chrome-command-line-switches.md", "docs/api/session.md", "lib/browser/api/app.js"]
|
v0.37.x not send kerberos ticket
|
- Electron version: >=0.37
- Operating system: ubuntu linux x64
When server send header 'WWW-Authenticate: Negotiate' electron not send kerberos ticket.
`app.allowNTLMCredentialsForAllDomains(true)` is called.
On electron v0.36.x it work's fine.
|
https://github.com/electron/electron/issues/4825
|
https://github.com/electron/electron/pull/5638
|
1b9bced8c02ede3ad0dc57cb7ef93e7387ee689b
|
c489d6d4b3b6a6ecbc1c555e484126dd1480f954
| 2016-03-16T14:17:46Z |
c++
| 2016-05-23T10:48:30Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,802 |
["atom/common/api/atom_api_v8_util.cc", "atom/renderer/atom_render_view_observer.cc"]
|
DevTools: Console Object Inspector shows empty key
|
- Electron version: 0.37.2
- Operating system: OS X
If you print an object to the console you are able to expand it.
A regression was added in 0.37.0 that causes a blank key (`""`) to show up.
This key is also expandable, if you try to do this it will cause the following error to appear:
```
DevTools was disconnected from the page.
Once page is reloaded, DevTools will automatically reconnect.
```
The following error will also occur when trying to expand the scope variables in the debugger.
For whatever reason, the empty key is "expanded", so when you expand the object containing the empty key, the error will occur.
|
https://github.com/electron/electron/issues/4802
|
https://github.com/electron/electron/pull/4892
|
afb82fcc1fca8712b9228327fb0c98e8c3ed7655
|
c307478d5d484e798480b68ded3f76778252315e
| 2016-03-14T23:34:49Z |
c++
| 2016-03-31T01:22:23Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,776 |
["docs/api/desktop-capturer.md", "lib/browser/desktop-capturer.ts", "lib/browser/rpc-server.js", "lib/renderer/api/desktop-capturer.ts", "shell/browser/api/electron_api_desktop_capturer.cc", "shell/browser/api/electron_api_desktop_capturer.h", "spec-main/api-desktop-capturer-spec.ts", "spec/ts-smoke/electron/renderer.ts", "typings/internal-ambient.d.ts"]
|
Capture media for specified WebContents
|
- Electron version: `0.37.0`
- Operating system: All
I've been trying for weeks now to figure this out, I need to somehow capture the audio output from my electron application. But the `desktopCapturer` API appears to exclude that exact use case :cry:
Is there an alternative way of performing this capture WITHOUT capturing the entire computers audio through the "screen" capturer?
https://github.com/atom/electron/blob/master/docs/api/desktop-capturer.md
Also open to any JS methods of capturing a stream from an Audio element
|
https://github.com/electron/electron/issues/4776
|
https://github.com/electron/electron/pull/22701
|
dc72f74020eb64afff7f01f8a9f13db69546724a
|
204f001c5dbb039f12199a28c9aaf022827865f9
| 2016-03-13T02:14:51Z |
c++
| 2020-05-26T20:34:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,760 |
["atom/browser/api/atom_api_app.cc", "atom/browser/api/atom_api_app.h", "atom/browser/api/atom_api_web_contents.cc", "atom/browser/api/atom_api_web_contents.h", "atom/browser/atom_browser_client.cc", "atom/browser/atom_browser_client.h", "lib/browser/api/browser-window.js", "lib/browser/guest-window-manager.js", "lib/renderer/override.js", "script/lib/config.py"]
|
"disposition" should be "background-tab" in "new-window" event when clicking link with ctrl/cmd pressed
|
- Electron version: v0.36.9
- Operating system: Windows 10/OS X
In #779 a `disposition` was added to the `new-window` event in [webContents](https://github.com/atom/electron/blob/master/docs/api/web-contents.md#event-new-window) but it always seems to be set to `new-window` when clicking on target="_blank" links in our web app wrapper: https://github.com/irccloud/irccloud-desktop/blob/v0.1.3/app/main.js#L109
If I Ctrl (Win) or Cmd (OS X) or middle click on links, I would expect to see a `background-tab` disposition, as in Chrome that will open links in a background tab, while keeping focus on the current tab. I'd like to catch this behaviour to set `activate` to false in `shell.openExternal`.
Is this possible?
|
https://github.com/electron/electron/issues/4760
|
https://github.com/electron/electron/pull/4917
|
7353fb4296675aedcb495bc86dfa7e3026e71ac3
|
0416e65b8b209c5599187ba1e8b4263e5fc50864
| 2016-03-11T15:46:17Z |
c++
| 2016-04-01T04:52:29Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,709 |
["atom/browser/native_window_views.cc"]
|
Fullscreen mode does not hide the window menu
|
I built the `electron-quick-start` application. When I toggle the fullscreen mode, the toolbar remains visible.
---
- Electron version: 0.36.10
- Operating system:
```
% uname -a
Linux <hostname> 4.4.1-2-ARCH #1 SMP PREEMPT Wed Feb 3 13:12:33 UTC 2016 x86_64 GNU/Linux
% node --version
v5.7.0
```
running Openbox as the windows manager.
|
https://github.com/electron/electron/issues/4709
|
https://github.com/electron/electron/pull/6429
|
32f3f3244e3aa4a2aa031c13faabc21ab4fc1fb1
|
33e8d5e0aac806d5fad35438fb373d07069ec3f7
| 2016-03-07T18:25:18Z |
c++
| 2016-07-11T04:28:00Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,690 |
["default_app/main.js", "docs/api/process.md"]
|
process.argv differs in built electron apps
|
- Electron version: 0.36.9
- Operating system: OSX
I have an application that can accept CLI arguments. I noticed when I built the app that `process.argv` is not the same as when running electron while developing.
When running electron from the command line `process.argv` looks like:
``` bash
electron ./my-app --foo --ping=123
```
``` js
[
'/Users/bmann/Dev/my-app/node_modules/electron-prebuilt/dist/Electron.app/Contents/MacOS/Electron',
'./my-app',
'--foo',
'--ping=123'
]
```
This is good because typically when you parse CLI args you do something like:
`minimist(process.argv.slice(2))`
This matches what its like to use `node` regularly such as `node index.js --foo --ping=123`
However when passing args directly to my built app, `process.argv` looks like this:
``` bash
./MyApp.app/Contents/MacOS/Electron --foo --ping=123
```
``` js
[
'/Users/bmann/Dev/MyApp.app/Contents/MacOS/Electron',
'--foo',
'--ping=123'
]
```
This is bad because now `minimist(process.argv.slice(2))` misses the args. I get why this is happening but it is unfortunately not easy to work around, and I did not have this problem with `nwjs`.
|
https://github.com/electron/electron/issues/4690
|
https://github.com/electron/electron/pull/5421
|
7b83d920fac75f03f33e458c04edd850a1231322
|
f58b3f853ea4761f828ea567e603cc280a64cf78
| 2016-03-05T20:49:24Z |
c++
| 2016-05-06T13:09:02Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,688 |
["chromium_src/chrome/browser/process_singleton_posix.cc"]
|
LSOpenURLsWithRole() failed with error -10810
|
- Electron version: 0.36.9
- Operating system: OS X 10.11.3
This error happens when I'm using `makeSingleInstance` only when compiling for Mac App Store using sandboxing.
This error happens opening the application from Finder too:
``` shell
$ open tmp/Rocket.Chat.app
LSOpenURLsWithRole() failed with error -10810 for the file /Development/Projects/Rocket.Chat.Electron/tmp/Rocket.Chat.app.
```
``` shell
$ ./tmp/Rocket.Chat.app/Contents/MacOS/Rocket.Chat --safe
[97838:0305/150135:FATAL:process_singleton_posix.cc(215)] Check failed: path.length() < arraysize(addr->sun_path). Socket path too long: /var/folders/cn/yt_3gyn56ss95g0rdz6thk640000gn/T/chat.rocket/.org.chromium.Chromium.eNFrdP/SingletonSocket
0 Electron Framework 0x0000000104375273 _ZN9brightray12MainDelegate24OverrideChildProcessPathEv + 393267
1 Electron Framework 0x000000010438b1ba _ZN9brightray12MainDelegate24OverrideChildProcessPathEv + 483194
2 Electron Framework 0x00000001042cfccd _ZN16ProcessSingleton7CleanupEv + 1053
3 Electron Framework 0x00000001042ce63f _ZN16ProcessSingleton29NotifyOtherProcessWithTimeoutERKN4base11CommandLineEiRKNS0_9TimeDeltaEb + 1935
4 Electron Framework 0x00000001042ce1fa _ZN16ProcessSingleton29NotifyOtherProcessWithTimeoutERKN4base11CommandLineEiRKNS0_9TimeDeltaEb + 842
5 Electron Framework 0x00000001042cee5e _ZN16ProcessSingleton37NotifyOtherProcessWithTimeoutOrCreateERKN4base11CommandLineEiRKNS0_9TimeDeltaE + 30
6 Electron Framework 0x00000001042cee2d _ZN16ProcessSingleton26NotifyOtherProcessOrCreateEv + 45
7 Electron Framework 0x00000001041cad0c _ZN4atom3api3App18MakeSingleInstanceERKN4base8CallbackIFbRKNSt3__16vectorINS4_12basic_stringIcNS4_11char_traitsIcEENS4_9allocatorIcEEEENS9_ISB_EEEERKNS2_8FilePathEEEE + 156
8 Electron Framework 0x00000001041d6070 _ZN4base8internal15RunnableAdapterIMN4atom3api3AppEFbRKNS_8CallbackIFbRKNSt3__16vectorINS6_12basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEENSB_ISD_EEEERKNS_8FilePathEEEEEE3RunEPS4_SO_ + 48
9 Electron Framework 0x00000001041d6028 _ZN4base8internal12InvokeHelperILb0EbNS0_15RunnableAdapterIMN4atom3api3AppEFbRKNS_8CallbackIFbRKNSt3__16vectorINS7_12basic_stringIcNS7_11char_traitsIcEENS7_9allocatorIcEEEENSC_ISE_EEEERKNS_8FilePathEEEEEEENS0_8TypeListIJRKPS5_SP_EEEE8MakeItSoESS_SW_SP_ + 56
10 Electron Framework 0x00000001041d5fda _ZN4base8internal7InvokerINS_13IndexSequenceIJEEENS0_9BindStateINS0_15RunnableAdapterIMN4atom3api3AppEFbRKNS_8CallbackIFbRKNSt3__16vectorINSA_12basic_stringIcNSA_11char_traitsIcEENSA_9allocatorIcEEEENSF_ISH_EEEERKNS_8FilePathEEEEEEEFbPS8_SS_ENS0_8TypeListIJEEEEESZ_NS0_12InvokeHelperILb0EbSV_NSY_IJRKSW_SS_EEEEEFbS13_SS_EE3RunEPNS0_13BindStateBaseES13_SS_ + 58
11 Electron Framework 0x00000001041d5e9c _ZNK4base8CallbackIFbPN4atom3api3AppERKNS0_IFbRKNSt3__16vectorINS5_12basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEENSA_ISC_EEEERKNS_8FilePathEEEEEE3RunERKS4_SN_ + 60
12 Electron Framework 0x00000001041d55ac _ZN4mate8internal7InvokerINS0_13IndicesHolderIJLm0ELm1EEEEJPN4atom3api3AppERKN4base8CallbackIFbRKNSt3__16vectorINSA_12basic_stringIcNSA_11char_traitsIcEENSA_9allocatorIcEEEENSF_ISH_EEEERKNS8_8FilePathEEEEEE18DispatchToCallbackIbEEvNS9_IFT_S7_SS_EEE + 28
13 Electron Framework 0x00000001041d5465 _ZN4mate8internal10DispatcherIFbPN4atom3api3AppERKN4base8CallbackIFbRKNSt3__16vectorINS8_12basic_stringIcNS8_11char_traitsIcEENS8_9allocatorIcEEEENSD_ISF_EEEERKNS6_8FilePathEEEEEE18DispatchToCallbackERKN2v820FunctionCallbackInfoINST_5ValueEEE + 181
14 libnode.dylib 0x000000010860b9f3 _ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE + 163
15 libnode.dylib 0x0000000108634f3c _ZN2v88internal8Builtins17InvokeApiFunctionENS0_6HandleINS0_10JSFunctionEEENS2_INS0_6ObjectEEEiPS6_ + 1644
16 libnode.dylib 0x0000000108639001 _ZN2v88internal8BuiltinsD1Ev + 16177
17 ??? 0x00002c1def208b3b 0x0 + 48507077561147
Trace/BPT trap: 5
```
|
https://github.com/electron/electron/issues/4688
|
https://github.com/electron/electron/pull/5236
|
ec832f418af2b80014c0cc0bdae5dee767431733
|
1c75baa8b3ef9d4d9deb7b42551d5b2d1ac2c254
| 2016-03-05T18:09:29Z |
c++
| 2016-04-21T05:14:24Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,643 |
["atom/browser/browser.cc", "atom/browser/browser.h"]
|
will-quit event fired when app.exit() is called.
|
According to documentation when app.exit() is called the `will-quit` and `before-quit` events should not be fired. This is apparently not the case.
- Electron version: 0.36.5-0.36.9
- Operating system: OSX
|
https://github.com/electron/electron/issues/4643
|
https://github.com/electron/electron/pull/4968
|
aae83cbce8c9c20acdd64e4427406c809b2d454e
|
efb0fc2ea519786b454b9da02550c3d6ef29c61a
| 2016-03-01T11:50:18Z |
c++
| 2016-04-07T07:14:35Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,622 |
["atom/browser/api/atom_api_web_contents.cc", "atom/browser/api/atom_api_web_contents.h", "atom/browser/ui/drag_util.h", "atom/browser/ui/drag_util_mac.mm", "atom/browser/ui/drag_util_views.cc", "docs/api/web-contents.md", "docs/tutorial/desktop-environment-integration.md", "filenames.gypi"]
|
OS native File Drag from Electron to *
|
The best way to start a File-Drag for now, is the downloadURL as i know.
Like here in Nylas N1:
https://github.com/nylas/N1/blob/master/internal_packages/attachments/lib/attachment-component.cjsx#L67
But only Images and PDFs are able to Drop direct on an Application (MAC). Other file formats just can be copied to Folders.
I think I'm not the only one who is looking for a full native file drop and I think chromium offers that already.
On chrome://downloads/ its possible to Drag any File on an Application (Mac).
Is there maybe a way to access this Drag Function in electron or can it become a part of?
Multi File Drag would be very nice too! :)
[chrome://downloads/ > js dragstart > chrome.send('drag', id)](https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/resources/md_downloads/crisper.js&q=crisper.js&sq=package:chromium&type=cs&l=15751)
I have no knowledge, about cc++ but it found that... :D
[drag_download_item_views.cc](https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/download/drag_download_item_views.cc&q=DragDownloadItem&sq=package:chromium&dr=CSs&l=31)
[md_downloads_dom_handler.cc](https://chromium.googlesource.com/chromium/src.git/+/master/chrome/browser/ui/webui/md_downloads/md_downloads_dom_handler.cc)
|
https://github.com/electron/electron/issues/4622
|
https://github.com/electron/electron/pull/6333
|
74ebbf9c78956f5ecc105477d8ac678c044464f7
|
83ae14f2ed627ff73a2c83b152c9c6a69d75460c
| 2016-02-27T10:42:10Z |
c++
| 2016-07-04T04:30:56Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,586 |
["docs/api/browser-window.md"]
|
Ensure that BrowserWindow's height and width can't override minWidth and minHeight
|
- Electron version: 0.36.1
- Operating system: OS X 10.11.3
Currently, setting a `height` and `width` on a `BrowserWindow` instance overrides `minWidth` and `minHeight` properties, if set. So if you had a `minWidth` and `minheight` of `500`, but set the `height` and `width` to `100`, the `BrowserWindow` would be `100` x `100`, instead of `500` x `500` like I'd expect. I'd expect `minWidth` and `minHeight` to take precedence over a manually set `height` like it does in CSS. This probably also applies to `maxWidth` and `maxHeight`, but I haven't tested that yet.
(Not sure if this counts as a bug or enhancement, because I'm not sure what the intended behavior was.)
Let me know if you need any more information! :smile:
|
https://github.com/electron/electron/issues/4586
|
https://github.com/electron/electron/pull/5411
|
aa516ae01aa35a13c7c58e4fbfd133561fe06020
|
16bfc195479da9ff814ce5f684f2a743f43f80d8
| 2016-02-24T00:05:49Z |
c++
| 2016-05-06T05:24:59Z |
closed
|
electron/electron
|
https://github.com/electron/electron
| 4,573 |
["atom/browser/ui/views/menu_layout.cc", "atom/browser/ui/win/atom_desktop_window_tree_host_win.cc", "atom/browser/ui/win/atom_desktop_window_tree_host_win.h"]
|
Maximized frameless window has border on Windows 10
|
- Electron version: v0.36.8
- Operating system: Windows 10
I'm trying to make a frameless window that still has the native functionality (double click to maximize, for example), but for some reason when I maximize using the double click or `BrowserWindow.maximize()` it shows a blue border like in this image:
However when I maximize by dragging the window to the top of the screen the border is still here but black. That's the same border that appears when the web contents lag during the resize.
Apparently [Discord](https://discordapp.com) "solved" this issue (their border is dark gray so it blends better with the application), but I don't know how they actually did it.
|
https://github.com/electron/electron/issues/4573
|
https://github.com/electron/electron/pull/8404
|
9089d553422bc8b76dd31ffaf4773ace6f9fa39c
|
170f2f61f9be92ecf16dba54113d840730400199
| 2016-02-22T14:02:38Z |
c++
| 2017-01-16T19:24:39Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,657 |
["packages/react-dom-bindings/src/shared/ReactControlledValuePropTypes.js", "packages/react-dom/src/__tests__/ReactDOMSelect-test.js"]
|
Bug: Select when passed a value as Prop errors with a suggestion to pass readOnly
|
Seems weird when we try to use a `select` component, and pass a value as a prop, it prompts with the error to either set `onChange` or `readOnly`.
the `readOnly` at the last seems misleading since the `select` component does not have a `readOnly` prop, unlike inputs which do have a `readOnly` attribute.
**SELECT PROPS**
https://react.dev/reference/react-dom/components/select
seems an easy fix would be to check if the mounted component is a `select` component and then conditionally just change the error message, though would need to add tests to support the same.
https://github.com/facebook/react/assets/72331432/12674152-7d57-4d98-99e6-635577b31bfe
cc @sophiebits
codesandbox link to tinker:- https://codesandbox.io/s/admiring-wright-9sctsn?file=/src/App.js
|
https://github.com/facebook/react/issues/27657
|
https://github.com/facebook/react/pull/27740
|
3e97c00debbd6706b6ec6b7da15094bf2ba81ef4
|
5dd35968bef791ccc5948c657fabf191a77fff3f
| 2023-11-06T04:04:20Z |
javascript
| 2023-12-01T15:55:55Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,585 |
["packages/react-dom-bindings/src/client/ReactFiberConfigDOM.js", "packages/react-dom/src/__tests__/ReactDOMFloat-test.js"]
|
Bug: hoisted stylesheets should not reorder when re-rendered in a transition
|
vercel.com observed a bug where a stylesheet hoisted using a `precedence` was reordered after an update. This is not correct semantics (once a hoisted stylesheet is inserted it should remain in place until removed)
Investigating the React implementation I observed that if you insert a hoisted stylesheet during a synchronous render and later render a new reference to that stylesheet in a transition React incorrectly considers the stylesheet not loaded and tries to coordinate it's loading the the commit. This is erroneous as once a stylesheet is in the DOM it should never be re-inserted (moved).
|
https://github.com/facebook/react/issues/27585
|
https://github.com/facebook/react/pull/27586
|
51ffd3564f97b58737df395d30628a27fa71a39d
|
a9985529f1aa55477f0feafe2398d36707cf6108
| 2023-10-25T18:10:51Z |
javascript
| 2023-10-25T18:51:01Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,572 |
["packages/react-dom-bindings/src/client/validateDOMNesting.js"]
|
Bug: 'Warning: validateDOMNesting: <hr> cannot appear as a child of <select>' – but this is now valid HTML
|
The latest version of Chrome and Safari support `hr` elements as children of `select` elements, and the HTML spec has been updated – but React warns about this as it used to be invalid HTML.
- https://developer.chrome.com/blog/hr-in-select
- https://webkit.org/blog/14445/webkit-features-in-safari-17-0/#:~:text=Horizontal%20rules%20inside%20select%20elements
- https://html.spec.whatwg.org/#the-select-element-2:~:text=Zero%20or%20more%20option%2C%20optgroup%2C%20hr%2C%20and%20script%2Dsupporting%20elements.
- https://html.spec.whatwg.org/#the-select-element-2:~:text=Occasionally%20it%20can%20be%20useful%20to%20have%20a%20separator%3A
<img width="800" height="811" src="https://wd.imgix.net/image/HodOHWjMnbNw56hvNASHWSgZyAf2/55LrQnjhGNU5h22nq2PK.jpg?auto=format"
alt="Screenshot of before and after with hr in select. The after image has dividers between groups.">
React version: `18.2.0`
## Steps To Reproduce
1. Add a `hr` element as a child of `select`
## The current behavior
`Warning: validateDOMNesting: <hr> cannot appear as a child of <select>`
## The expected behavior
No `validateDOMNesting` warning.
|
https://github.com/facebook/react/issues/27572
|
https://github.com/facebook/react/pull/27632
|
0c6348758f89be250070560972e736171201f82d
|
ca16c26356221a4b52185d7425d77675f0307250
| 2023-10-24T10:43:54Z |
javascript
| 2023-10-31T21:43:16Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,540 |
["packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js", "packages/react-dom/src/__tests__/ReactDOMFizzServerBrowser-test.js", "packages/react-server/src/ReactFizzServer.js"]
|
Bug: ReadableStream can be written to after close
|
As reported in https://github.com/vercel/next.js/issues/56919 it is possible for the ReadableStream controller to be written to after it is already closed. This is because inside an async context a Float method such as `ReactDOM.preload()` can attempt to flush newly created Resources even after the stream has completed.
React version:
The underlying bug has been in React since Float landed. The expression of the Bug as reported in the Next.js repo was landed in: https://github.com/facebook/react/commit/701ac2e57290f913502c6012c15e815f412f84b7
The first Canary release to have this new expression was: [18.3.0-canary-f81c0f1ed-20230927](https://www.npmjs.com/package/react-dom/v/18.3.0-canary-f81c0f1ed-20230927)
## Steps To Reproduce
1. use `react-dom/server.edge`
2. Ensure the environment supports AsyncLocalStorage
3. Call Float method like `ReactDOM.preload(...)` after an await after the stream has closed
## The current behavior
If the conditions are right the Float call will initiate a write after the stream has closed and there will be a thrown exception
## The expected behavior
The Float call is ignored after the stream has closed. There are no errors
|
https://github.com/facebook/react/issues/27540
|
https://github.com/facebook/react/pull/27541
|
20c91b65341fd404185fc778c6844ac29ab815d5
|
601e5c38505ebc0ee099d8666b2f7a8b03159ac4
| 2023-10-18T16:01:21Z |
javascript
| 2023-10-18T17:05:18Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,296 |
["packages/react-reconciler/src/ReactFiber.js", "packages/react-reconciler/src/ReactFiberBeginWork.js", "packages/react-reconciler/src/ReactFiberCommitWork.js"]
|
Bug: devtools source field disappears after component remount
|
On actions that cause a component to remount (e.g. changing a value of a hook inside the component), the `devtools` source field disappears.
https://github.com/facebook/react/assets/75563024/64d84583-d8d9-44ca-b1d7-1cb232baccce
---
React version: 18.2.0
## Steps To Reproduce
1. Clone this repo: https://github.com/idango10/fiber-debug-source-issue (simple project made with `create-react-app`, only difference is `src/App.js` and `src/Comp.js`.
2. Open `devtools` -> `Components`, and navigate to the `Comp`.
3. Verify that the source field exists.
4. Change the value of the hook (e.g. from `'initial value'` to `'new value'`) and save the file.
5. Go back to the browser. and navigate back to the `Comp` in `devtools`.
6. You'll see that the source field vanished.
## Code example:
Let's say I have two components:
```js
export function InnerComp() {
const [value] = React.useState('initial value');
return <span>{value}</span>;
}
```
```js
import { InnerComp } from './InnerComp';
function OuterComp() {
return <InnerComp />;
}
```
Looking at `Comp` in `devtools` -> `Components`, we'll see that there's a source field.
If I change `'initial value'` to `'new value'` inside `useState` of `InnerComp`:
```js
export function InnerComp() {
const [value] = React.useState('new value');
return <span>{value}</span>;
}
```
The source field of `Comp` will vanish.
## The current behavior
The `devtools` source field of a component vanishes after remount.
## The expected behavior
The field should stay visible.
|
https://github.com/facebook/react/issues/27296
|
https://github.com/facebook/react/pull/27297
|
4129ea8c922b950be3964f98d2bb74ff4a1c5431
|
eaa696876ee40bb048727aefe995be1bbb7384a8
| 2023-08-28T17:56:14Z |
javascript
| 2023-08-29T15:42:35Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,286 |
["packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js", "packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js"]
|
Bug: Hydration fails in Next.js with server actions actions custom tags
|
I'm currently testing the experimental server actions feature in Next.js. Once this feature is enabled Next.js uses React's experimental build. This however results in hydration failed error messages when using custom HTML tags with a dash like `my-tag` in JSX. The server response does not include any output for this tag and its children. Replacing the custom tag with a regular tag like `<div>` works completely fine.
I previously reported this issue at vercel/next.js#51141 where they suspect this to be an issue within React itself.
React version: Experimental
## Steps To Reproduce
1. Install latest next.js: npx create-[next-app](https://linear.app/vercel/issue/NEXT-app)@latest
2. Enable server actions in next.config.js
3. Wrap {children} in root layout with custom HTML tag like `<my-tag>`
Link to code example:
https://github.com/mritzerfeld/next-server-action-with-custom-tag
## The current behavior
Server-generated contents with custom HTML tags do no produce any output for such.
## The expected behavior
Server-generated contents within custom HTML tags to be included in server response, as using Next without server actions or with regular HTML tags.
|
https://github.com/facebook/react/issues/27286
|
https://github.com/facebook/react/pull/27511
|
ea8a8619ce51a0f8f0a78f87485e4e2a6f9d8c27
|
bb778528d1ca22b44dad832f0258aaa4c0e6d4a4
| 2023-08-26T13:58:05Z |
javascript
| 2023-10-12T22:02:26Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,200 |
["packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js"]
|
Bug: `ReactDOM.preload()`
|
React version: `18.3.0-canary-9377e1010-20230712`
## Steps To Reproduce
1. Add `<meta name="viewport" content="width=device-width, initial-scale=1" />` inside of `<head>`
2. Call `ReactDOM.preload('/img.png', { as: 'image' })`
## The current behavior
The `<link>` generated from the preload is before the `<meta>` for the viewport.
## The expected behavior
The `<link>` should come after the `<meta>` for the viewport.
## Related
- https://github.com/vercel/next.js/issues/53574
cc @gnoff
|
https://github.com/facebook/react/issues/27200
|
https://github.com/facebook/react/pull/27201
|
997f52fbb30ec4b777b66edcdd75f594d9fe0c55
|
ea17cc18f458010c89c1bf494be08bb782d034af
| 2023-08-07T19:21:39Z |
javascript
| 2023-08-07T22:22:48Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 27,177 |
["packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js", "packages/react-dom-bindings/src/server/ReactFizzConfigDOMLegacy.js", "packages/react-dom/src/__tests__/ReactDOMLegacyFloat-test.js"]
|
Bug: [18.3.0-canary] renderToString hoists some tags to top(working in 18.2)
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
React version: 18.3.0-canary-493f72b0a-20230727
## Steps To Reproduce
1. run following code.
```js
import * as ReactDOMServer from "react-dom/server";
const element = (
<html>
<head>
{/* meta and title are hoisted */}
<meta charSet="utf-8" />
<title>title</title>
{/* the script tag is not hoisted */}
<script src="foo"></script>
{/* but this is hoisted */}
<script src="foo" async></script>
</head>
</html>
);
console.log(ReactDOMServer.renderToString(element));
```
<!--
Your bug will get fixed much faster if we can run your code and it doesn't
have dependencies other than React. Issues without reproduction steps or
code examples may be immediately closed as not actionable.
-->
Link to code example:
https://codesandbox.io/s/react1830-canary-493f72b0a-20230727-ssr-hoist-bug-lvhj45?file=/src/index.js
<!--
Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
repository on GitHub, or provide a minimal code example that reproduces the
problem. You may provide a screenshot of the application if you think it is
relevant to your bug report. Here are some tips for providing a minimal
example: https://stackoverflow.com/help/mcve.
-->
## The current behavior
console.log outputs `<meta charSet="utf-8"/><script src="foo" async=""></script><title>title</title><html><head><script src="foo"></script></head></html>`
## The expected behavior
console.log outputs `<html><head><meta charSet="utf-8"/><title>title</title><script src="foo"></script><script src="foo" async=""></script></head></html>`
|
https://github.com/facebook/react/issues/27177
|
https://github.com/facebook/react/pull/27269
|
dd480ef923930c8906a02664b01bcdea50707b5d
|
86198b923199224b60533952b636348bb0484a6d
| 2023-08-02T02:26:00Z |
javascript
| 2023-08-22T17:54:33Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,911 |
["packages/react-devtools-extensions/build.js", "packages/react-devtools-extensions/edge/build.js", "packages/react-devtools-extensions/src/utils.js", "packages/react-devtools-extensions/webpack.backend.js", "packages/react-devtools-extensions/webpack.config.js"]
|
[DevTools Bug]: React devtools stuck at Loading React Element Tree, troubleshooting instructions are Chrome-specific
|
### Website or app
corporate project (private)
### Repro steps
Load page, then open React DevTools. Reloading or closing and reopening the tab does not fix the problem. Quitting and reopening Firefox sometimes fixes the problem.
<img width="837" alt="image" src="https://github.com/facebook/react/assets/2292782/0fbcaf7c-533f-4afd-819c-b9f2749aa765">
The [linked troubleshooting instructions](https://github.com/facebook/react/blob/main/packages/react-devtools/README.md#the-react-tab-shows-no-components) provide no guidance for users of browsers other than Chrome; I am running Firefox v114 (on macOS 13.2.1).
### How often does this bug happen?
Often
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26911
|
https://github.com/facebook/react/pull/27179
|
456d153bb582798effa76c09bec2405ab2e392cf
|
2c4c84718810bf3df411d599acc152d08208d35f
| 2023-06-07T17:26:43Z |
javascript
| 2023-08-29T09:40:02Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,876 |
["packages/react-dom-bindings/src/client/ReactDOMInput.js", "packages/react-dom/src/__tests__/ReactDOMInput-test.js"]
|
Bug: Radio button onChange not called in current React Canary
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
React version: 18.3.0-canary-a1f97589f-20230526
## Steps To Reproduce
1. Create radio buttons that toggle `disabled` in `onChange`
2. After selecting each radio button, `onChange` is no longer called
<!--
Your bug will get fixed much faster if we can run your code and it doesn't
have dependencies other than React. Issues without reproduction steps or
code examples may be immediately closed as not actionable.
-->
Link to code example:
The following CodeSandbox demonstrates the issue with the current react canary version. The issue is not present when react & react-dom versions are changed to stable 18.2.0
https://codesandbox.io/s/react-canary-radio-buttons-deiqb3?file=/src/App.js
<!--
Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
repository on GitHub, or provide a minimal code example that reproduces the
problem. You may provide a screenshot of the application if you think it is
relevant to your bug report. Here are some tips for providing a minimal
example: https://stackoverflow.com/help/mcve.
-->
## The current behavior
`<input type="radio" />`'s `onChange` prop is not called on subsequent clicks of the input
## The expected behavior
`<input type="radio" />`'s `onChange` prop should be called on subsequent clicks of the input
|
https://github.com/facebook/react/issues/26876
|
https://github.com/facebook/react/pull/27394
|
2b3d5826836ac59f8446281976762d594e55d97e
|
3c27178a2f2c74f14d90613028e3929e1f06d830
| 2023-05-31T15:17:41Z |
javascript
| 2023-09-21T04:57:09Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,860 |
["packages/react-devtools-extensions/build.js", "packages/react-devtools-extensions/edge/build.js", "packages/react-devtools-extensions/src/utils.js", "packages/react-devtools-extensions/webpack.backend.js", "packages/react-devtools-extensions/webpack.config.js"]
|
[DevTools Bug]: App not recognized in Firefox, but works in Chrome
|
### Website or app
-
### Repro steps
On both Firefox 103 and 104 the react devtools extension says: "This page doesn't appear to be using React".
On the most recent version of Chrome it's working just fine.
I cannot share the project since it's a private project unfortunately, but I suspect this is a regression introduced with the recent https://github.com/facebook/react/pull/26765
Especially since the devtools were working perfectly fine until maybe one or two weeks ago.
It _does_ work in incognito mode in Firefox.
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26860
|
https://github.com/facebook/react/pull/27179
|
456d153bb582798effa76c09bec2405ab2e392cf
|
2c4c84718810bf3df411d599acc152d08208d35f
| 2023-05-26T12:03:19Z |
javascript
| 2023-08-29T09:40:02Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,821 |
["packages/react-devtools-shared/src/devtools/views/Components/InspectedElement.js"]
|
[DevTools Bug]: Strict mode badge points to the old docs
|
### Website or app
https://fb.me/devtools-strict-mode
### Repro steps
The Strict mode warning badge points to https://fb.me/devtools-strict-mode which points to the strict mode section in [the old docs](https://legacy.reactjs.org/docs/strict-mode.html) instead of [the new docs](https://react.dev/reference/react/StrictMode).
Badge:
<img width="273" alt="Screenshot 2023-05-16 at 20 20 59" src="https://github.com/facebook/react/assets/37460589/2b3cbcf0-43b7-4f71-a420-02d31258ef92">
Code:
https://github.com/facebook/react/blob/4cd7065665ea2cf33c306265c8d817904bb401ca/packages/react-devtools-shared/src/devtools/views/Components/InspectedElement.js#L240
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26821
|
https://github.com/facebook/react/pull/26825
|
2468a87358de55137508e777846746091d7a1514
|
d7a98a5e97c3512ba43dd809337ae1691df1ae66
| 2023-05-16T18:27:09Z |
javascript
| 2023-05-17T12:34:34Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,793 |
["packages/react-devtools-shared/src/backend/renderer.js", "packages/react-devtools-shared/src/hook.js"]
|
[DevTools Bug] Cannot remove node "226752" because no matching node was found in the Store.
|
### Website or app
https://travel.testsigma.com/
### Repro steps
https://travel.testsigma.com/
### How often does this bug happen?
Every time
### DevTools package (automated)
react-devtools-extensions
### DevTools version (automated)
4.27.6-7f8c501f6
### Error message (automated)
Cannot remove node "226752" because no matching node was found in the Store.
### Error call stack (automated)
```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28710:43
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26606:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26775:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:57029:39)
```
### Error component stack (automated)
_No response_
### GitHub query string (automated)
```text
https://api.github.com/search/issues?q=Cannot remove node because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
|
https://github.com/facebook/react/issues/26793
|
https://github.com/facebook/react/pull/27147
|
493f72b0a7111b601c16b8ad8bc2649d82c184a0
|
997f52fbb30ec4b777b66edcdd75f594d9fe0c55
| 2023-05-08T06:59:51Z |
javascript
| 2023-08-03T19:02:18Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,787 |
["packages/react-devtools-core/package.json", "packages/react-devtools-extensions/chrome/manifest.json", "packages/react-devtools-extensions/edge/manifest.json", "packages/react-devtools-extensions/firefox/manifest.json", "packages/react-devtools-inline/package.json", "packages/react-devtools-timeline/package.json", "packages/react-devtools/CHANGELOG.md", "packages/react-devtools/package.json"]
|
[DevTools Bug] Cannot add node "1751" because a node with that id is already in the Store.
|
### Website or app
local repo
### Repro steps
Loading a React component with the React profiler recording enabled
### How often does this bug happen?
Every time
### DevTools package (automated)
react-devtools-extensions
### DevTools version (automated)
4.27.6-7f8c501f6
### Error message (automated)
Cannot add node "1751" because a node with that id is already in the Store.
### Error call stack (automated)
```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28581:41
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26606:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26775:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:57029:39)
```
### Error component stack (automated)
_No response_
### GitHub query string (automated)
```text
https://api.github.com/search/issues?q=Cannot add node because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
|
https://github.com/facebook/react/issues/26787
|
https://github.com/facebook/react/pull/26823
|
f8de255e94540f9018d8196b3a34da500707c39b
|
2468a87358de55137508e777846746091d7a1514
| 2023-05-06T23:03:50Z |
javascript
| 2023-05-17T10:40:50Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,756 |
["packages/react-devtools-extensions/src/background.js"]
|
[DevTools Bug]: React pages not being detected as using React in Incognito mode
|
### Website or app
https://opensource.fb.com
### Repro steps
It seems that with the latest update of Chrome and React DevTools, it cannot detect pages as using React on incognito. Screenshot attached below:
<img width="518" alt="image" src="https://user-images.githubusercontent.com/34370238/235575519-8eeaa3c5-80fa-4cc4-a33d-3d2f0541f0d9.png">
* _Chrome version: 112.0.5615.137 (arm64)_
* _React DevTools version: 4.27.6 (4/20/2023)_
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26756
|
https://github.com/facebook/react/pull/26765
|
2c2476834a7c739ca239750b73f74aa1df144a93
|
8a25302c668d6f9a24f6680fb4947e9b388bb7d9
| 2023-05-02T03:53:41Z |
javascript
| 2023-05-03T16:27:39Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,697 |
["scripts/rollup/packaging.js"]
|
[DevTools Bug]: can not build react devtools for local development, instructions lead to error
|
### Website or app
https://github.com/facebook/react/tree/main/packages/react-devtools-extensions
### Repro steps
Follow the instructions here to build local version of react devtools extension: https://github.com/facebook/react/tree/main/packages/react-devtools-extensions
```
git clone https://github.com/facebook/react.git
cd react
yarn install
yarn build-for-devtools
```
Stuck on this step everytime `yarn build-for-devtools`:
```
D:\Other\react\node_modules\flow-parser\flow_parser.js:807
throw a}function
^
Error: SignedSource.signFile(...): Cannot sign file without token: <<SignedSource::*O*zOeWoEQle#+L!plEphiEmie@IsG>>
at Object.<anonymous> (D:\Other\react\node_modules\signedsource\index.js:20:28)
at Module._compile (node:internal/modules/cjs/loader:1196:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
at Module.load (node:internal/modules/cjs/loader:1074:32)
at Function.Module._load (node:internal/modules/cjs/loader:909:12)
at Module.require (node:internal/modules/cjs/loader:1098:19)
at require (node:internal/modules/cjs/helpers:108:18)
at Object.<anonymous> (D:\Other\react\scripts\rollup\packaging.js:18:37)
at Module._compile (node:internal/modules/cjs/loader:1196:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
```
Is there anything else I need to set up in order to make this work?
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26697
|
https://github.com/facebook/react/pull/26727
|
25b99efe0c9c9d593c86829386c86740d409fa8c
|
f87e97a0a67fa7cfd7e6f2ec985621c0e825cb23
| 2023-04-21T21:27:01Z |
javascript
| 2023-04-25T16:26:34Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,500 |
["packages/react-devtools-extensions/src/contentScripts/prepareInjection.js", "packages/react-devtools-shared/src/__tests__/inspectedElement-test.js", "packages/react-devtools-shared/src/__tests__/legacy/inspectElement-test.js", "packages/react-devtools-shared/src/backend/agent.js", "packages/react-devtools-shared/src/backend/legacy/renderer.js", "packages/react-devtools-shared/src/backend/renderer.js", "packages/react-devtools-shared/src/backend/types.js", "packages/react-devtools-shared/src/backend/utils.js", "packages/react-devtools-shared/src/bridge.js", "packages/react-devtools-shared/src/devtools/store.js"]
|
[DevTools Bug]: copy operations don't work in Chrome
|
### Website or app
https://react.dev
### Repro steps
1. Go to components tab.
2. For any component, try to copy the value in props, hooks etc. to clipboard.
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26500
|
https://github.com/facebook/react/pull/26604
|
5426af3d50ff706f3ebeb4764f838e0a3812bf9a
|
21021fb0f06f5b8ccdad0774d53ff5f865faeb6d
| 2023-03-28T19:02:59Z |
javascript
| 2023-04-12T15:12:03Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,419 |
["packages/react-reconciler/src/ReactFiberBeginWork.js", "packages/react-reconciler/src/ReactFiberWorkLoop.js", "packages/react-reconciler/src/__tests__/ReactUse-test.js"]
|
Bug: forwardRef provides an empty object as ref, causing `can't define property "current"` error.
|
React version: 18.3.0-next-3ba7add60-20221201
Hard to reproduce.
In Next.js, in rare cases, and only after a fast refresh, the ref object when using forwardRef is simply `{}`.
This leads to the `TypeError: can't define property "current": Object is not extensible` error when used with `useImperativeHandle`.
```tsx
function Parent() {
const carouselRef = useRef<any>();
return <Suspense><Carousel ref={carouselRef} /></Suspense>
}
const Carousel = forwardRef((props, ref) => {
if (!('current' in ref)) { debugger; }
const thing = use(aPromise);
return ...;
});
```
In `updateImperativeHandle`, the ref is already an empty object.
I haven't investigated it further yet, the stacktraces are quite hard to follow.
|
https://github.com/facebook/react/issues/26419
|
https://github.com/facebook/react/pull/26535
|
0ae348018d5b3a3f1ccdd92de85d9cc581b2b98d
|
7329ea81c154d40800e30104be40f050e8c2af3e
| 2023-03-17T18:14:27Z |
javascript
| 2023-04-02T22:48:28Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,226 |
["packages/react-reconciler/src/ReactFiberHooks.js", "packages/react-reconciler/src/__tests__/ReactTransition-test.js"]
|
Bug: Nested useTransition makes isPending of outer one always false
|
Nested `startTransition` call "takes over" and makes parent `startTransition` unable to track `isPending`.
Seb says it's a bug.
Repro:
https://codesandbox.io/s/pensive-breeze-rg70wn?file=/IndexPage.js:192-288
1. Click the button
2. `isPending` in `IndexPage.js` is `true`
However, `isPending` in `App.js` is `false`.
Expected: `isPending` in `App.js` is also `true`.
|
https://github.com/facebook/react/issues/26226
|
https://github.com/facebook/react/pull/26243
|
21f6dba6a71f16b56a96182233c897468324cf99
|
05777ffb01515679d73541062a4ecc745af04a2f
| 2023-02-24T04:32:07Z |
javascript
| 2023-03-16T01:10:53Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,200 |
["packages/react-devtools-shared/src/backend/views/Highlighter/index.js"]
|
Bug: React dev tools inspect element of hover does not work on shadow elements
|
Using react while making a shadow DOM and then using react devtools inspect element feature does not work as expected video and codesandbox below
**sandboxLink**
https://stackblitz.com/edit/react-zqp67t?file=src/App.js
**while attaching shadowroot**
https://user-images.githubusercontent.com/72331432/219961254-65c9e84c-9774-441f-9eec-e9ef58f1382d.mp4
**without attaching root**
https://user-images.githubusercontent.com/72331432/219961266-b276063e-e0f4-4f30-b614-0af3876a9916.mp4
|
https://github.com/facebook/react/issues/26200
|
https://github.com/facebook/react/pull/26888
|
e6fae308e9300ca545003ac147cc7e4e541f561c
|
910045696bb5f693acb77890e6750c5e4659b420
| 2023-02-19T16:12:16Z |
javascript
| 2023-06-07T15:38:38Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,112 |
["fixtures/attribute-behavior/AttributeTableSnapshot.md", "fixtures/attribute-behavior/src/attributes.js", "packages/react-dom-bindings/src/shared/DOMProperty.js", "packages/react-dom-bindings/src/shared/possibleStandardNames.js"]
|
Bug: transform-origin is not recognized as a valid attribute despite being in SVG specs
|
This is re-opening [this issue](https://github.com/facebook/react/issues/11265), which is likely too stale to get eyes on it
React version: 18
## Steps To Reproduce
1. Go [to this JS fiddle](https://jsfiddle.net/gjb1dxro/)
2. Inspect console to see error about `transform-origin` being invalid
## The current behavior
`transform-origin` is not recognized as a valid attribute
## The expected behavior
`transform-origin` should be recognized as a valid attribute.
From the previous issue, I wrote:
> transform-origin is now a proper SVG attribute ([seen here](https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/transform-origin)), spec references below). I believe this is worth re-opening (and investigating whether there are other missing SVG attributes)
My understanding of the SVG spec reference above is that we should consider this to be valid now.
|
https://github.com/facebook/react/issues/26112
|
https://github.com/facebook/react/pull/26130
|
3ff1540e9bbe30aae52e2c9ab61c843bd0c94237
|
28fcae062bff2b611cd935911f8666b0627b9551
| 2023-02-06T05:42:35Z |
javascript
| 2023-02-09T12:47:50Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,095 |
["packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js", "packages/react-reconciler/src/ReactFiberHooks.js"]
|
Bug: useSyncExternalStore will cause hydration missmatch in `StrictMode` if `serverSnapshot` is different from `snapshot`
|
## React version
React version: 18.3.0-next-b0671f9ea-20230130
## Problem
In `StrictMode`, when using hydrateRoot to render a component that using `useSyncExternalStore` it seems that useSES will do hydration twice.
But in second hydration process, useSES does not use the result of `getServerSnapshot` as initial state, which will cause hydration error.
This problem will only happen in `development` mode,
## Reproduce
Link to code example:
https://codesandbox.io/s/useses-18-3-rojznv
It works well in react 18.2
https://codesandbox.io/s/useses-18-2-13iskc
|
https://github.com/facebook/react/issues/26095
|
https://github.com/facebook/react/pull/26791
|
a389046a529c6d22ba5895dd7f5d4b0b8d17c345
|
4cd7065665ea2cf33c306265c8d817904bb401ca
| 2023-02-02T08:53:46Z |
javascript
| 2023-05-12T21:18:03Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 26,051 |
["packages/react-devtools-extensions/webpack.backend.js", "packages/react-devtools-extensions/webpack.config.js"]
|
[DevTools Bug]: Can not work on devtools, instructions lead to error
|
### Website or app
https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en
### Repro steps
Because react requires java, not on macos (but assumes brew installed!):
```
brew update && brew install java
sudo ln -sfn /usr/local/opt/openjdk/libexec/openjdk.jdk /Library/Java/JavaVirtualMachines/openjdk.jdk
export PATH="/usr/local/opt/openjdk/bin:$PATH"' >> ~/.zshrc
export PATH="/usr/local/opt/openjdk/bin:$PATH" >> ~/.zshrc
export PATH="/usr/local/opt/openjdk/bin:$PATH"
```
Because react requires node before v17 (but assuming you have nvm installed!):
```
nvm install 16
```
then the real stuff (directions inside folders like ./chrome/ are quite wrong):
```
git clone https://github.com/facebook/react.git
cd react
yarn install
yarn build-for-devtools
cd packages/react-devtools-extensions
yarn build:chrome
yarn build:chrome:local
yarn run test:chrome
```
Now inside devtools:
```
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval'".
at ./src/contentScripts/prepareInjection.js (prepareInjection.js:133:1)
at __webpack_require__ (prepareInjection.js:20:30)
at prepareInjection.js:84:18
at prepareInjection.js:87:10
```
What exactly are you doing that works in order to build, test, and develop this extension?
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/26051
|
https://github.com/facebook/react/pull/26067
|
cb16201180a2642696303d4aac3a04e5fd348512
|
78c4bec207795e718b5f4acc48ade19c8b94bf1f
| 2023-01-26T00:43:30Z |
javascript
| 2023-01-27T20:35:07Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,989 |
["packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js", "packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js"]
|
Feat(renderToPipeableStream): Allow passing crossorigin attribute on bootstrapScripts
|
When using `window.onerror` in the bootstrap script that is hosted in a CDN the error message will show `"Script error."` instead of a proper error message. This is because of the [cross-origin](https://blog.sentry.io/2016/05/17/what-is-script-error/) script. To fix this issue a `crossorigin="anonymous"` attribute needs to be added in the script tag.
Currently, `bootstrapScripts` supports [`src` and `integrity`](https://github.com/facebook/react/blob/0fce6bb498357feb4465859912004b2e20fe7084/packages/react-dom-bindings/src/server/ReactDOMServerFormatConfig.js#L226) as configurations, should it also supports a `crossorigin` property?
|
https://github.com/facebook/react/issues/25989
|
https://github.com/facebook/react/pull/26844
|
88df88f9441e0f83917e60e04d4f75118c1adec5
|
90229eb925e2330667fb7c023a5c4317c7ae8363
| 2023-01-12T02:24:01Z |
javascript
| 2023-06-13T16:12:10Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,964 |
["packages/react-reconciler/src/ReactFiberHooks.js", "packages/react-reconciler/src/__tests__/ReactHooks-test.internal.js", "packages/react-reconciler/src/__tests__/ReactThenable-test.js", "scripts/error-codes/codes.json"]
|
Bug: Suspense | client component should have a queue
|
React version: 18.2.0
Next version: 13.1.1
## Steps To Reproduce
1. Suspend using a (fake) promise in a client component in app dir (next)
2. Try to useState after the use() call
````ts
'use client';
import { use, useState } from 'react';
const testPromise = new Promise((resolve) => {
setTimeout(() => {
resolve('use test promise');
});
});
export default function Page() {
use(testPromise);
useState(0);
return <h1>Test</h1>;
}
````
Link to code example:
https://codesandbox.io/s/github/xiel/app-playground/tree/suspense-error/?from-embed=&file=/app/page.tsx
## The current behavior
Suspending for a promise in a client component and using state/reducer after results in errors during hydration:
```
react-dom.development.js?9d87:94 Warning: An error occurred during hydration. The server HTML was replaced with client
react-dom.development.js?9d87:94 Warning: You are accessing "digest" from the errorInfo object passed to onRecoverableError.
on-recoverable-error.js?eb92:17 Uncaught Error: Should have a queue. This is likely a bug in React. Please file an issue.
```
## The expected behavior
No error during hydration.
|
https://github.com/facebook/react/issues/25964
|
https://github.com/facebook/react/pull/26232
|
96cdeaf89bfde7551b4ffe4d685da169b780f2f7
|
a8f971b7a669a9a6321b9f3cea820f68b2e4ac6e
| 2023-01-05T08:46:14Z |
javascript
| 2023-02-24T20:06:27Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,924 |
["packages/react-devtools-extensions/src/contentScripts/prepareInjection.js"]
|
Bug: Scripts injected by browser extensions (e.g. React dev tools) may cause hydration errors
|
_My apologies if this is the wrong place to report the below; but I could not find a more appropriate place to get feedback from the React team. It seems that the below is going to be a common use case._
**React version:** 18.2.0
## Description of the problem
Since I've started using the `renderToPipeableStream` api making React render the whole DOM tree starting from the `html` tag (inspired by Dan's [demo](https://codesandbox.io/s/kind-sammet-j56ro?file=/src/App.js); but now I can see a similar technique [described](https://beta.reactjs.org/apis/react-dom/server/renderToPipeableStream#rendering-a-react-tree-as-html-to-a-nodejs-stream) in the beta docs), I've been seeing occasional hydration errors popping up in our error tracker. Since the html payload that I am rendering server-side is minuscule and limited to just the contents of the `head` tag, I was very puzzled as to the cause of the error. Even more puzzling was that the error occurred only occasionally, which made the diagnosis of the cause difficult. The fact that the production build of React is not even making it obvious which elements caused the mismatch made it harder still.
After a long time spent in debugging, I discovered that at least one possible cause of the hydration error is the script injected by react-devtools chrome extension:
**Screenshot 1:** React (in dev build) complaining about an unexpected script tag:
**Screenshot 2:** Debugger paused in the function that logs out the warning. The offending `child` node is a script tag.
**Screenshot 3:** The unexpected script tag is revealed to be injected by React devtools chrome extension to request react-devtools backend:
**Screenshot 4:** The script tag is injected after the body tag:
This raises several questions:
- In case of React devtools, should it add the `suppress-hydration-warning` attribute (an escape hatch suggested in the docs) to the script added by the chrome extension? Will it help if it did?
- Similar problems might potentially occur when using third-party scripts that modify the DOM (e.g. add `script` or `style` elements to the DOM). Another common example is webpack splitting CSS into small chunks and then adding link tags for the chunks into the `head` dynamically during client-side navigation. Is this a concern for situations when React is responsible for the whole html tree? Is there any advice from the React team regarding this?
- It looks like the recommended SSR option, according to the new docs, is `renderToPipeableStream`/`renderToReadableStream`, with React being in control of the whole `html` element. If third-party scripts are indeed a concern when React controls of the whole DOM tree, then what is the recommended api for server-side rendering? Perhaps this should be addressed in the docs?
|
https://github.com/facebook/react/issues/25924
|
https://github.com/facebook/react/pull/26233
|
a8f971b7a669a9a6321b9f3cea820f68b2e4ac6e
|
564166099b5f46dd33f3356b01a72c0314103a18
| 2022-12-22T10:42:37Z |
javascript
| 2023-02-24T20:13:05Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,806 |
["packages/react-devtools-extensions/src/background.js"]
|
[DevTools Bug]: Components Tab does not show up
|
### Website or app
https://beta.reactjs.org/
### Repro steps
1. Visit website
2. Open dev tools
This happens on https://beta.reactjs.org/ but I first noticed in on a personal project (localhost).
When I open the dev tools, the CPU goes up. At first, the Components tab does not show up. After a loooooong time, it does show up, however when I click on it nothing renders inside.
I don't know if it's the newest Chrome version or the newest extension version that's causing it.
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/25806
|
https://github.com/facebook/react/pull/26068
|
1445acf777a6e503e6c15e78dd4257abbd7a2264
|
c12194f7485f298fadc1e51cfffb93e63d61ad96
| 2022-12-05T10:48:01Z |
javascript
| 2023-02-07T12:59:44Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,682 |
["fixtures/attribute-behavior/AttributeTableSnapshot.md", "fixtures/attribute-behavior/src/attributes.js", "packages/react-dom-bindings/src/shared/possibleStandardNames.js"]
|
Bug: `<img fetchPriority>` attribute is not supported
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
React version: 18.0.0
## Steps To Reproduce
1. Render an `<img src="#" fetchPriority="high" />` tag
<!--
Your bug will get fixed much faster if we can run your code and it doesn't
have dependencies other than React. Issues without reproduction steps or
code examples may be immediately closed as not actionable.
-->
Link to code example: https://playcode.io/1011424
<!--
Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
repository on GitHub, or provide a minimal code example that reproduces the
problem. You may provide a screenshot of the application if you think it is
relevant to your bug report. Here are some tips for providing a minimal
example: https://stackoverflow.com/help/mcve.
-->
## The current behavior
A warning is logged:
```
Warning: React does not recognize the `fetchPriority` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `fetchpriority` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
at img
at div
at App
```
## The expected behavior
React should recognize the `fetchPriority` prop and emit it as `fetchpriority` into HTML.
To be clear, using `<img fetchpriority="high">` works and doesn’t log a warning. However, it is inconsistent [with other DOM APIs](https://reactjs.org/docs/dom-elements.html). In the JS DOM API, the attribute is camel-cased as [`HTMLImageElement.fetchPriority`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/fetchPriority).
`fetchPriority` has been supported in Chromium browsers [since Chromium 101](https://chromestatus.com/feature/5273474901737472) (Apr 26, 2022). [Per Patrick Meenan](https://bugs.webkit.org/show_bug.cgi?id=247291), Mozilla is working on an implementation as well.
|
https://github.com/facebook/react/issues/25682
|
https://github.com/facebook/react/pull/25927
|
81d4ee9ca5c405dce62f64e61506b8e155f38d8d
|
de7d1c90718ea8f4844a2219991f7115ef2bd2c5
| 2022-11-15T00:44:09Z |
javascript
| 2022-12-23T19:31:27Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,667 |
["packages/react-devtools/app.html", "packages/react-devtools/app.js", "packages/react-devtools/package.json", "packages/react-devtools/preload.js", "yarn.lock"]
|
[DevTools Bug]: react-devtools depends on vulnerable version of electron
|
### Website or app
https://github.com/facebook/react/blob/main/packages/react-devtools/package.json
### Repro steps
### Issue
electron package versions <18.3.7 suffer from a security vulnerability: "Exfiltration of hashed SMB credentials on Windows via file:// redirect".
See https://github.com/advisories/GHSA-p2jh-44qj-pf2v
### Solution
Upgrade electron dependency in react-devtools to >18.3.7
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/25667
|
https://github.com/facebook/react/pull/26337
|
161f6ae42cf570d3daec355abcf3b006c58315da
|
aef930314f55d4b445078f83be53d46028d4574c
| 2022-11-11T12:15:45Z |
javascript
| 2023-03-08T03:31:54Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,625 |
["packages/react-dom/src/__tests__/ReactDOMServerPartialHydration-test.internal.js", "packages/react-reconciler/src/ReactFiberBeginWork.new.js", "packages/react-reconciler/src/ReactFiberBeginWork.old.js"]
|
Update before hydration completed error does not clarify which suspense boundary or which update
|
Error in question:
> Uncaught Error: This Suspense boundary received an update before it finished hydrating. This caused the boundary to switch to client rendering. The usual way to fix this is to wrap the original update in startTransition.
The current error gives no indication which part of the code causes the error, making it very hard to debug.
Two suggestions / questions:
**Indicate which suspense boundary**
Is there any way to indicate _which_ suspense boundary received an update? Showing the component tree like in other errors would be a very helpful first step.
**Indicate which update**
Even better of course would be if there could be any indication which update was triggered, with a call stack.
|
https://github.com/facebook/react/issues/25625
|
https://github.com/facebook/react/pull/25692
|
c54e3541b2fb6251bd7cd399e77037220b47de2e
|
e1dd0a2f54f2a3699edd0eb1aceae83ab63839d1
| 2022-11-03T11:20:12Z |
javascript
| 2022-11-16T03:10:54Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,565 |
["packages/react-reconciler/src/ReactFiberHooks.new.js", "packages/react-reconciler/src/ReactFiberHooks.old.js", "packages/react-reconciler/src/__tests__/useSyncExternalStore-test.js"]
|
Bug: useSyncExternalStore does not update internal value if a setState is also called, outside useEffect, causing store sets not re-render
|
In a custom hook, I forgot to wrap my `setState` call in a `useEffect`, which did not pose any problems prior to React 18 but now this does not work anymore. The component does not re-render if the store is changed back to its initial value. I guess this might be expected, but there was no warning whatsoever, so it was hard to find out.
So this is more like a question:
- Is that behavior a bug?
- If it is not, would it be useful to have a warning for another developer making the same mistake?
React version: 18
## Steps To Reproduce
1. Have a component use `useSyncExternalStore` (for example redux 8)
2. Call `setState` outside of `useEffect` or event handlers (in render)
3. Trigger a change to the store back and forth
Link to code example: https://codesandbox.io/s/react-18-redux-8-reproduce-bug-ojdx43
## The current behavior
- The component does re-render if the store value is updated to something different than its initial value
- The component **does not** re-render if the store is updated to its initial value again
## The expected behavior
- The component does re-render if the store value is updated to something different than its initial value
- The component **also does** re-render if the store is updated to its initial value again
## Further digging
When I tried to trace down the issue, I found that the `setState` called outside `useEffect` would mess up with the fiber update queue, in particular the prior `pushEffect` supposedly calling `updateStoreInstance` with the latest value to have the internal cached instance up to date. It does not get called at all (cancelled? overridden?) because of the unwrapped `setState`.
As a consequence, that cached instance never gets updated. Any other value but the initial value hence correctly triggers a re-render, as the `checkIfSnapshotChanged` ends up always comparing against that initial value.
|
https://github.com/facebook/react/issues/25565
|
https://github.com/facebook/react/pull/25578
|
18dff7990a81b3ff1e716dd2cf113c6027bdcc06
|
1e3e30dae2bcfbeb0abc686f2a37aec208eedb39
| 2022-10-26T00:15:04Z |
javascript
| 2022-11-08T10:25:42Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,187 |
["packages/react-devtools-shared/src/backend/renderer.js"]
|
[DevTools Bug]: DevTools shouldn't skip over keyed Fragments in the tree
|
### Website or app
https://github.com/reactjs/reactjs.org/pull/4981
### Repro steps
1. Wrap something into `<Fragment key="stuff">`
2. It doesn't show up in DevTools
We filter out fragments because they tend to be useless. But this one is important! Keys are crucial and we should show anything with a key in the tree.
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/25187
|
https://github.com/facebook/react/pull/25197
|
bfb65681e7d77ba9bd79f7f95ac57930542b57c1
|
c80e54116e2f9c550472116181a5c66ad97adfbf
| 2022-09-05T03:06:52Z |
javascript
| 2022-09-07T17:21:30Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 25,052 |
["packages/react-devtools-extensions/README.md"]
|
Bug: Can't build react-devtools-extension project locally
|
When trying to build the [(]https://github.com/facebook/react/tree/main/packages/react-devtools-extensions) locally:
```
`PS C:\tutorial\extensions\react> yarn build-for-devtools
yarn run v1.22.19
$ cross-env RELEASE_CHANNEL=experimental yarn build react/index,react/jsx,react-dom/index,react-dom/unstable_testing,react-dom/test-utils,react-is,react-debug-tools,scheduler,react-test-renderer,react-refresh,react-art --type=NODE && cp -r ./build/node_modules build/oss-experimental/
$ node ./scripts/rollup/build.js react/index,react/jsx,react-dom/index,react-dom/unstable_testing,react-dom/test-utils,react-is,react-debug-tools,scheduler,react-test-renderer,react-refresh,react-art --type=NODE
node:internal/modules/cjs/loader:936
throw err;
^
Error: Cannot find module 'rollup'
Require stack:
- C:\tutorial\extensions\react\scripts\rollup\build.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (C:\tutorial\extensions\react\scripts\rollup\build.js:3:16)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\\tutorial\\extensions\\react\\scripts\\rollup\\build.js' ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.``
```
## Steps To Reproduce
1. clone react
2. run yarn build-for-devtools from the root repo
node version: Node.js v16.16.0.
|
https://github.com/facebook/react/issues/25052
|
https://github.com/facebook/react/pull/25053
|
2872a26e14627f90e812048f21feb6d0c8cc0244
|
65b3449c89870dbce9c8ca01c892825dc9d74ca3
| 2022-08-05T17:24:18Z |
javascript
| 2022-10-05T15:27:09Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,985 |
["packages/react-dom/src/__tests__/ReactDOMFizzServerNode-test.js", "packages/react-server/src/ReactServerStreamConfigNode.js"]
|
Bug: `renderToPipeableStream()` emit mysterious mojibake whitespace chars in the result
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
`renderToPipeableStream()` emit mojibake whitespace chars in its result.
This would sometimes breaks the final generated html.
React version: 18.2.0
## Steps To Reproduce
Run this test case with jest.
```javascript
import { PassThrough } from 'node:stream';
import { renderToPipeableStream } from 'react-dom/server';
const element = (
<html lang="ja">
<head>
<meta charSet="utf-8" />
<title>吾輩は猫である</title>
</head>
<body>
<p>
どこで生れたかとんと見当がつかぬ。何でも薄暗いじめじめした所でニャーニャー泣いていた事だけは記憶している。吾輩はここで始めて人間というものを見た。しかもあとで聞くとそれは書生という人間中で一番獰悪な種族であったそうだ。この書生というのは時々我々を捕えて煮て食うという話である。しかしその当時は何という考もなかったから別段恐しいとも思わなかった。ただ彼の掌に載せられてスーと持ち上げられた時何だかフワフワした感じがあったばかりである。掌の上で少し落ちついて書生の顔を見たのがいわゆる人間というものの見始であろう。この時妙なものだと思った感じが今でも残っている。第一毛をもって装飾されべきはずの顔がつるつるしてまるで薬缶だ。その後猫にもだいぶ逢ったがこんな片輪には一度も出会わした事がない。のみならず顔の真中があまりに突起している。そうしてその穴の中から時々ぷうぷうと煙を吹く。どうも咽せぽくて実に弱った。これが人間の飲む煙草というものである事はようやくこの頃知った。
</p>
<p>
この書生の掌の裏でしばらくはよい心持に坐っておったが、しばらくすると非常な速力で運転し始めた。書生が動くのか自分だけが動くのか分らないが無暗に眼が廻る。胸が悪くなる。到底助からないと思っていると、どさりと音がして眼から火が出た。それまでは記憶しているがあとは何の事やらいくら考え出そうとしても分らない。
</p>
<p>
ふと気が付いて見ると書生はいない。たくさんおった兄弟が一疋も見えぬ。肝心の母親さえ姿を隠してしまった。その上今までの所とは違って無暗に明るい。眼を明いていられぬくらいだ。はてな何でも容子がおかしいと、のそのそ這い出して見ると非常に痛い。吾輩は藁の上から急に笹原の中へ棄てられたのである。
</p>
</body>
</html>
);
test('renderToPipeableStream', async () => {
const onStreamReady = new Promise((resolve, reject) => {
const stream = renderToPipeableStream(element, {
onAllReady() {
resolve(stream);
},
onError(err) {
reject(err);
},
});
});
const renderingStream = await onStreamReady;
const sink = new PassThrough();
const connected = renderingStream.pipe(sink);
const result = [];
for await (const chunk of connected) {
if (typeof chunk === 'string') {
result.push(chunk);
} else {
const txt = String(chunk);
result.push(txt);
}
}
const actual = result.join('');
expect(actual).toMatchSnapshot();
});
```
## The current behavior
The above testcase generate this result:
```
"<!DOCTYPE html><html lang="ja"><head><meta charSet="utf-8"/><title>吾輩は猫である</title></head><body><p>どこで生れたかとんと見当がつかぬ。何でも薄暗いじめじめした所でニャーニャー泣いていた事だけは記憶している。吾輩はここで始めて人間というものを見た。しかもあとで聞くとそれは書生という人間中で一番獰悪な種族であったそうだ。この書生というのは時々我々を捕えて煮て食うという話である。しかしその当時は何という考もなかったから別段恐しいとも思わなかった。ただ彼の掌に載せられてスーと持ち上げられた時何だかフワフワした感じがあったばかりである。掌の上で少し落ちついて書生の顔を見たのがいわゆる人間というものの見始であろう。この時妙なものだと思った感じが今でも残っている。第一毛をもって装飾されべきはずの顔がつるつるしてまるで薬缶だ。その後猫にもだいぶ逢ったがこんな片輪には一度も出会わした事がない。のみならず顔の真中があまりに突起している。そうしてその穴の中から時々ぷうぷうと煙を吹く。どうも咽せぽくて実に弱った。これが人間の飲む煙草というものである事はようやくこの頃知った。</p><p>この書生の掌の裏でしばらくはよい心持に坐っておったが、しばらくすると非常な速力で運転し始めた。書生が動くのか自分だけが動くのか分らないが無暗に眼が廻る。胸が悪くなる。到底助からないと思っていると、どさりと音がして眼から火が出た。それまでは記憶しているがあとは何の事やらいくら考え出そうとしても分らない。</p><p>ふと気が付いて見ると書生はいない。たくさんおった兄弟が一疋も見えぬ。肝心の母親さえ姿を隠してしまった。その上今まで��の所とは違って無暗に明るい。眼を明いていられぬくらいだ。はてな何でも容子がおかしいと、のそのそ這い出して見ると非常に痛い。吾輩は藁の上から急に笹原の中へ棄てられたのである。</p></body></html>"
```
## The expected behavior
The current behavior's result contains `その上今まで��の所とは違って無暗に明るい`.
But we expect this sentence should be `その上今までの所とは違って無暗に明るい`.
So `renderToPipeableStream()` should not emit mysterious whitespace chars.
|
https://github.com/facebook/react/issues/24985
|
https://github.com/facebook/react/pull/26228
|
ca2cf319fdfcf6e5f048e082f5169bc1b849c129
|
96cdeaf89bfde7551b4ffe4d685da169b780f2f7
| 2022-07-25T13:02:52Z |
javascript
| 2023-02-24T19:33:54Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,959 |
["packages/react-dom/src/__tests__/ReactDOMServerPartialHydration-test.internal.js", "packages/react-reconciler/src/ReactFiberBeginWork.new.js", "packages/react-reconciler/src/ReactFiberBeginWork.old.js"]
|
Bug / Docs / Question: Handling interrupted suspense boundaries
|
In a world where portions of the component tree can hydrate and become intractable with child components still being suspended, does documentation / guidance exist on how to handle these cases?
Example: https://simple-remix-deferred-demo.fly.dev/
Green: Hydrated
Red: Suspended
Clicking either of the "Link" elements in the hydrated portion of the page, this will trigger a re-render and causes the suspense boundary to receive an update before it finishes: https://reactjs.org/docs/error-decoder.html/?invariant=421 This isn't an issue in terms of app functionality as implemented as I was under the assumption parent updates from interactive components would be expected, I mean, why wouldn't they?
So I guess there are a few questions I have:
1) Why does react log this error? Is it an *actual* error?
2) Are there implications I can't think of that would cause your average bare bones suspense usage to fall over and that's the reason this message exists?
3) When you expect updates to happen when boundaries are still suspended, is there a documented way to handle this to avoid this message?
|
https://github.com/facebook/react/issues/24959
|
https://github.com/facebook/react/pull/25692
|
c54e3541b2fb6251bd7cd399e77037220b47de2e
|
e1dd0a2f54f2a3699edd0eb1aceae83ab63839d1
| 2022-07-19T22:50:56Z |
javascript
| 2022-11-16T03:10:54Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,894 |
["package.json", "packages/react-devtools-extensions/package.json", "packages/react-devtools-shared/src/hooks/__tests__/updateMockSourceMaps.js", "packages/react-dom/src/test-utils/FizzTestUtils.js", "scripts/rollup/build.js", "yarn.lock"]
|
Upgrade to modern version of Rollup and related plugins
|
The inspiration for this came from @jasonwilliams 's PR for attempting to add sourcemap output support to React's builds:
- https://github.com/facebook/react/issues/20186
- https://github.com/facebook/react/pull/21946
But I figured that it would be useful to minimise the scope of changes in that PR, and to modernise the build tooling along the way.
---
There have been quite a few version releases for Rollup and the plugins that are currently used, as well as a number of the official Rollup plugins changing package name to use the `@rollup/*` package prefix.
Looking at [`package.json`](https://github.com/facebook/react/blob/main/package.json#L86-L92) we can see all of the current Rollup packages:
```jsonc
// ..snip..
"rollup": "^1.19.4",
"rollup-plugin-babel": "^4.0.1",
"rollup-plugin-commonjs": "^9.3.4",
"rollup-plugin-node-resolve": "^2.1.1",
"rollup-plugin-prettier": "^0.6.0",
"rollup-plugin-replace": "^2.2.0",
"rollup-plugin-strip-banner": "^0.2.0",
// ..snip..
```
And using `grep`, we can see some additional usages under `packages/`:
```shell
⇒ grep -r 'rollup' package.json packages/*/package.json
package.json: "rollup": "^1.19.4",
package.json: "rollup-plugin-babel": "^4.0.1",
package.json: "rollup-plugin-commonjs": "^9.3.4",
package.json: "rollup-plugin-node-resolve": "^2.1.1",
package.json: "rollup-plugin-prettier": "^0.6.0",
package.json: "rollup-plugin-replace": "^2.2.0",
package.json: "rollup-plugin-strip-banner": "^0.2.0",
package.json: "build": "node ./scripts/rollup/build.js",
package.json: "build-combined": "node ./scripts/rollup/build-all-release-channels.js",
package.json: "lint-build": "node ./scripts/rollup/validate/index.js",
packages/react-devtools-extensions/package.json: "rollup": "^1.19.4",
packages/react-devtools-extensions/package.json: "rollup-plugin-babel": "^4.0.1",
packages/react-devtools-extensions/package.json: "rollup-plugin-commonjs": "^9.3.4",
packages/react-devtools-extensions/package.json: "rollup-plugin-node-resolve": "^2.1.1",
```
The following is an attempt to capture all of the relevant information about package name changes, new versions, breaking changes, etc for these packages:
- https://github.com/rollup/rollup
- https://www.npmjs.com/package/rollup
- Lockfile currently resolves to `version "1.31.1"`
- https://github.com/rollup/rollup/blob/master/CHANGELOG.md#1311
- The latest version is `2.76.0`, but there are a number of other breaking changes leading up to that version
- https://github.com/rollup/rollup/blob/master/CHANGELOG.md#200
- > Breaking Changes
- https://github.com/rollup/plugins#plugins-found-here
- https://github.com/rollup/plugins/tree/master/packages/babel
- https://www.npmjs.com/package/@rollup/plugin-babel
- Lockfile currently resolves to `version "4.3.3"`
- Oldest version for `@rollup/plugin-babel` package name is `5.0.0`
- https://github.com/rollup/plugins/blob/master/packages/babel/CHANGELOG.md#500
- > Breaking Changes
- > Minimum compatible Rollup version is 1.2.0
- > Minimum supported Node version is 10.0.0
- > `.custom` factory is now available as separate `createBabelInputPluginFactory` export
- > Removed `externalHelpers` & `runtimeHelpers` options. There is now a single `babelHelpers` option which can take one of `'bundled'`, `'inline'`, `'runtime'` and `'external'` as a value. The default is `'bundled'` which matches `4.x` behavior, but it is recommended to configure this option explicitly.
- There don't seem to be any other breaking changes up till the latest version which is `5.3.1`
- https://github.com/rollup/plugins/tree/master/packages/commonjs
- https://www.npmjs.com/package/@rollup/plugin-commonjs
- Lockfile currently resolves to `version "9.3.4"`
- Oldest version for `@rollup/plugin-commonjs` package name is `11.0.0`
- https://github.com/rollup/plugins/blob/master/packages/commonjs/CHANGELOG.md#1100
- > Breaking: Minimum compatible Rollup version is 1.20.0
- > Breaking: Minimum supported Node version is 8.0.0
- The latest version is `22.0.1`, but there are a number of other breaking changes leading up to that version
- Based on some comments in the source, I believe this dependency is only used for `react-art`, so presumably if that still works properly with the newest version of this lib, we could update to that.
- https://github.com/rollup/plugins/tree/master/packages/node-resolve
- https://www.npmjs.com/package/@rollup/plugin-node-resolve
- Lockfile currently resolves to `version "2.1.1"`
- Oldest version for `@rollup/plugin-node-resolve` package name is `6.0.0`
- https://github.com/rollup/plugins/blob/master/packages/node-resolve/CHANGELOG.md#600
- > Breaking: Minimum compatible Rollup version is 1.20.0
- > Breaking: Minimum supported Node version is 8.0.0
- https://github.com/rollup/plugins/blob/master/packages/node-resolve/CHANGELOG.md#500-2019-05-15
- > Breaking Changes
- > Requires at least [email protected] to work (v1.12.0 for module side-effects to be respected)
- > If used with rollup-plugin-commonjs, it should be at least v10.0.0
- https://github.com/rollup/plugins/blob/master/packages/node-resolve/CHANGELOG.md#300
- > [BREAKING] Remove `options.skip`
- The latest version is `13.3.0`, but there are a number of other breaking changes leading up to that version
- https://github.com/rollup/plugins/tree/master/packages/replace
- https://www.npmjs.com/package/@rollup/plugin-replace
- Lockfile currently resolves to `version "2.2.0"`
- Oldest version for `@rollup/plugin-replace` package name is `2.2.0`
- https://github.com/rollup/plugins/blob/master/packages/replace/CHANGELOG.md#220
- The latest version is `4.0.0`, but there are a number of other breaking changes leading up to that version
- https://github.com/mjeanroy/rollup-plugin-strip-banner
- https://www.npmjs.com/package/rollup-plugin-strip-banner
- Lockfile currently resolves to `version "0.2.0"`
- https://github.com/mjeanroy/rollup-plugin-strip-banner/blob/master/CHANGELOG.md#020-2017-05-10
- The latest version is `2.0.0`. The changelog doesn't explicitly mention any breaking changes, but I didn't look into it too deeply
- **Edit:** Seems there is a secondary changelog in the README, though it still doesn't mention any breaking changes: https://github.com/mjeanroy/rollup-plugin-strip-banner#changelogs
- https://github.com/mjeanroy/rollup-plugin-prettier
- https://www.npmjs.com/package/rollup-plugin-prettier
- Lockfile currently resolves to `version "0.6.0"`
- https://github.com/mjeanroy/rollup-plugin-prettier/blob/master/CHANGELOG.md#060-2019-01-16
- The latest version is `2.2.2`. The changelog doesn't explicitly mention any breaking changes, but I didn't look into it too deeply
- **Edit:** Seems there is a secondary changelog in the README that mentions a breaking change: https://github.com/mjeanroy/rollup-plugin-prettier#changelogs
- > Breaking Change: prettier dependency is now a peer dependency instead of a "direct" dependency: user of the plugin can choose to use prettier 1.x.x or prettier 2.x.x (note that this plugin should be compatible with all versions of prettier).
If any of these updates rely on a node version later than `10.x`, then the following PR may have to land first, otherwise things might break on AppVeyor:
- https://github.com/facebook/react/issues/24891
- https://github.com/facebook/react/pull/24892
---
My plan/intent is to work through all of this and create a PR updating Rollup and the related plugins; but I wanted to create this issue in the meantime to capture what I have done so far, and also check whether there would be any issues/concerns with a PR like this being made.
**Edit:** PR opened in:
- https://github.com/facebook/react/pull/24916
|
https://github.com/facebook/react/issues/24894
|
https://github.com/facebook/react/pull/24916
|
bc38a3dfa74f63e66a8307d34ad6d52e838ab3b0
|
6b6d0617eff48860c5b4e3e79c74cbd3312cf45a
| 2022-07-12T11:04:14Z |
javascript
| 2023-02-20T06:35:56Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,883 |
["packages/react-dom-bindings/src/server/ReactFizzConfigDOM.js", "packages/react-dom-bindings/src/server/ReactFizzConfigDOMLegacy.js", "packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js", "packages/react-dom/src/__tests__/ReactDOMFizzServerBrowser-test.js", "packages/react-dom/src/test-utils/FizzTestUtils.js"]
|
Bug: React 18 renderToPipeableStream missing support for nonce for bootstrapScripts and bootstrapModules
|
React version: 18.1.0-next-af730436c-20220405
## Steps To Reproduce
1. Use server with CSP script-src set to strict-dynamic and with nonce.
2. Use renderToPipeableStream and add nonce to its options. Pass js client assets through bootstrapScripts.
3. Launch development server and try to load app.
## The current behavior
The renderToPipeableStream nonce is only applied to inline scripts (bootstrapScriptContent) in createResponseState().
## The expected behavior
A strict-dynamic script-src CSP applies to both inline scripts and scripts with src. I would expect the nonce to also be applied to scripts with src. The change seems simple enough .The createResponseState() would look like this:
```JS
var startScriptSrcWithNonce = nonce === undefined ? startScriptSrc : stringToPrecomputedChunk('<script nonce="' + escapeTextForBrowser(nonce) + '" src="');
var startModuleSrcWithNonce = nonce === undefined ? startModuleSrc : stringToPrecomputedChunk('<script nonce="' + escapeTextForBrowser(nonce) + '" type="module" src="');
...
if (bootstrapScripts !== undefined) {
for (var i = 0; i < bootstrapScripts.length; i++) {
bootstrapChunks.push(startScriptSrcWithNonce, stringToChunk(escapeTextForBrowser(bootstrapScripts[i])), endAsyncScript);
}
}
if (bootstrapModules !== undefined) {
for (var _i = 0; _i < bootstrapModules.length; _i++) {
bootstrapChunks.push(startModuleSrcWithNonce, stringToChunk(escapeTextForBrowser(bootstrapModules[_i])), endAsyncScript);
}
}
```
Please let me know if I am missing the reason why this was not implemented.
|
https://github.com/facebook/react/issues/24883
|
https://github.com/facebook/react/pull/26738
|
86b0e91998a04b22bb54a95d54f4a7632efa902f
|
9545e4810c2dc8922f575b6d8f726503a7345d0c
| 2022-07-09T21:01:51Z |
javascript
| 2023-05-01T16:19:02Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,781 |
["fixtures/devtools/standalone/index.html", "packages/react-devtools-shared/src/__tests__/utils-test.js", "packages/react-devtools-shared/src/hydration.js", "packages/react-devtools-shared/src/utils.js", "packages/react-devtools-shell/src/app/InspectableElements/UnserializableProps.js"]
|
[DevTools Bug]: Selecting/deselecting boolean from DevTools Component props causing loss of class functions
|
### Website or app
https://github.com/a-gehlot/react-error
### Repro steps
1) Install webpack, react, babel with "npm install" in terminal.
2) Bundle app with webpack via "webpack --watch --mode=developement" in terminal.
3) Open up "index.html" in Chrome and open React DevTools. Under Components, there should be a Dog component within a Person component, where the Person is passed as a prop to the Dog.
4) Under Dog props, there should be a person object with a value of present being true. If you click the button, the value of present should change to false, the number should switch to 0, and the checkbox should get deselected. However, if you manually select the checkbox to change between true/false, the prop seems to lose its prototype references to the original JS class, as an error stating it cannot find the function will be shown.
https://user-images.githubusercontent.com/52260394/175361370-b6ff5dea-788f-4564-a279-57e3cae11a4d.mov
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24781
|
https://github.com/facebook/react/pull/26522
|
7329ea81c154d40800e30104be40f050e8c2af3e
|
b14f8da15598cdc2253529a905421ac795d68ab1
| 2022-06-23T17:43:19Z |
javascript
| 2023-04-03T10:32:17Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,777 |
["packages/eslint-plugin-react-hooks/CHANGELOG.md"]
|
Changes since v4.5.0 of eslint-plugin-react-hooks are not listed in CHANGELOG
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
This may be the same kind of https://github.com/facebook/react/issues/24233, but I can't figure out the changes from CHANGELOG (I'm not sure if this is a bug).
If there are no changes, it would be helpful to note that in the CHANGELOG.
React version: N/A
## Steps To Reproduce
1. https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/package.json#L4
2. https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/CHANGELOG.md
<!--
Your bug will get fixed much faster if we can run your code and it doesn't
have dependencies other than React. Issues without reproduction steps or
code examples may be immediately closed as not actionable.
-->
Link to code example: N/A
<!--
Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
repository on GitHub, or provide a minimal code example that reproduces the
problem. You may provide a screenshot of the application if you think it is
relevant to your bug report. Here are some tips for providing a minimal
example: https://stackoverflow.com/help/mcve.
-->
## The current behavior
Changes since v4.5.0 of eslint-plugin-react-hooks are not listed in CHANGELOG.
## The expected behavior
Changes since v4.5.0 of eslint-plugin-react-hooks are listed in CHANGELOG.
|
https://github.com/facebook/react/issues/24777
|
https://github.com/facebook/react/pull/24853
|
3ddbedd0520a9738d8c3c7ce0268542e02f9738a
|
59bc52a16c5bdec6de5fc87de4d900ebc20389b2
| 2022-06-23T03:01:19Z |
javascript
| 2022-07-21T19:46:10Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,626 |
["packages/react-devtools-extensions/src/main.js"]
|
[DevTools Bug]: Component tree panel becomes unresponsive after clicking on a few components
|
### Website or app
Multiple; but you can check at https://react-bootstrap.github.io/
### Repro steps
1. Access a website in Chrome that uses React.
2. Open Chrome Developer Tools
3. Open the React Developer Tools Components tab/panel
4. Click on 5 - 10 components in the component tree individually to inspect them
Notes:
- This started happening on all React-based websites after updating to Chrome Version 102.0.5005.61 on my work MacBook (x86_64) and my personal MacBook (arm64). Reverting back to Chrome 100 seems to help.
- I had a co-worker test as well, with the same result.
- You can still select individual components using the picker, even after the panel locks up.
- The lock-up seems to happen quicker when `Expand component tree by default` is selected in the `Components` tab in the panel settings, but will still lock up if you manually expand enough components.
### How often does this bug happen?
Every time
### DevTools package (automated)
react-devtools-extensions
### DevTools version (automated)
4.24.6 (5/12/2022)
### Error message (automated)
None
### Error call stack (automated)
N/A
### Error component stack (automated)
N/A
### GitHub query string (automated)
N/A
|
https://github.com/facebook/react/issues/24626
|
https://github.com/facebook/react/pull/26193
|
bfb9cbd8ca2d042677056110887cc62d438f665f
|
ca2cf319fdfcf6e5f048e082f5169bc1b849c129
| 2022-05-26T22:56:27Z |
javascript
| 2023-02-23T21:53:11Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,623 |
["packages/react-debug-tools/src/ReactDebugHooks.js", "packages/react-debug-tools/src/__tests__/ReactHooksInspectionIntegration-test.js"]
|
[DevTools Bug] When inspecting, hook values after `useDeferredValue` are offset
|
### Website or app
https://github.com/Alduino/React-useDeferredValue-DevTools-Reprod
### Repro steps
1. Start the app in either dev or production mode.
2. Open the React dev tools
3. Click on the "App" component
4. The first Memo has the value `3.14` (the value that the second Memo should have) instead of `1.41`
If you want it to throw an error instead of just looking at the values, you can set `window.throwIfIncorrect = true` before DevTools inspects the component.
I tried in CodeSandbox's embedded React dev tools as well - the issue happens in React 18.0 (though the first hook has no value and the second has the first hook's value) but it doesn't happen in 18.1.
### How often does this bug happen?
Every time
### DevTools package (automated)
react-devtools-extensions
### DevTools version (automated)
4.24.0-82762bea5
### Error message (automated)
First is 3.14 when it should be 1.41
### Error call stack (automated)
```text
I@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:14022:6
exports.inspectHooksOfFiber@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:14090:12
inspectElementRaw@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:8847:65
inspectElement@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:9130:38
agent_Agent/<@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:11002:56
emit@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:4137:18
Bridge/this._wallUnlisten<@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:4780:14
listener@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:12986:11
EventListener.handleEvent*listen@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:12989:14
Bridge@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:4778:31
setup@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:12979:18
welcome@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:12958:8
EventListener.handleEvent*@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:12961:8
__webpack_require__@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:20:30
@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:84:18
@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/react_devtools_backend.js:87:10
```
### Error component stack (automated)
```text
InspectedElementContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:39159:43
Suspense
ErrorBoundary_ErrorBoundary@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:37513:5
div
InspectedElementErrorBoundaryWrapper@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:38001:46
NativeStyleContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:40650:38
div
div
OwnersListContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:33491:37
SettingsModalContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:36112:40
Components_Components@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:42701:52
ErrorBoundary_ErrorBoundary@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:37513:5
div
div
ThemeProvider@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:37655:23
PortaledContent@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:37685:34
div
div
div
ThemeProvider@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:37655:23
TimelineContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:42881:35
ProfilerContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:42326:35
TreeContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:30393:31
SettingsContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:31015:35
ModalDialogContextController@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:38064:38
DevTools_DevTools@moz-extension://38b0497f-37d9-49e7-9147-393888469493/build/main.js:54073:27
```
### GitHub query string (automated)
```text
https://api.github.com/search/issues?q=First is 3.14 when it should be 1.41 in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
|
https://github.com/facebook/react/issues/24623
|
https://github.com/facebook/react/pull/24742
|
a7c322c6f5fd33acfecf1d50dec4f911c3e9daf4
|
72ebc703ac8abacd44fdeb1e3d66eb28b75e5a5b
| 2022-05-26T02:08:32Z |
javascript
| 2022-06-17T18:43:10Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,603 |
["packages/react-devtools-shared/src/devtools/views/Profiler/Profiler.js"]
|
[DevTools Bug]: "Reload and profile" aways disabled on Timeline tab
|
### Website or app
beta.reactjs.org (local development)
### Repro steps
1. https://github.com/reactjs/reactjs.org/tree/main/beta
2. `yarn dev`
"Reload and profile" is enabled for Flamegraph:
<img width="724" alt="Screenshot 2022-05-23 at 21 28 07" src="https://user-images.githubusercontent.com/810438/169900687-7c62d7c5-34ad-43c0-b1fa-ca45c8e16dba.png">
But disabled for Timeline:
<img width="671" alt="Screenshot 2022-05-23 at 21 28 12" src="https://user-images.githubusercontent.com/810438/169900693-ba60f1f4-3b37-4141-993a-70bac5647b01.png">
And yet I can "reload and profile" in Flamegraph, then switch to Timeline and it works. So this doesn't add up.
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24603
|
https://github.com/facebook/react/pull/24702
|
a8555c308e06eacf807ec47caafd1e0e789d2c54
|
f7b44539ca9c2d126c7d12cfd0d9d4f13ad5851f
| 2022-05-23T20:29:50Z |
javascript
| 2022-06-10T14:38:33Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,543 |
["packages/react-devtools-shared/src/backend/utils.js", "packages/react-devtools-shared/src/hook.js"]
|
[DevTools Bug]: console.log crashes when I enable DevTools on Chrome
|
### Website or app
https://github.com/coolwind0202/web/blob/23877f77e23837a007aada5be363d65290571c88/web/src/components/page/members/IndexPage/IndexPage.tsx#L27
### Repro steps
For checking whenever my project will work correctly, when I run a command `next dev`, errors which are shown below occurred.
When I pass a first argument which is an **object** to `console.log()`, `console.error()`, `console.warn()`, I can repro the errors.
for example,
```
console.log([]);
console.error({});
```
Before a few days, the errors had never occured.
When I disable DevTools, the errors calm down.
I think, the errors may be caused by the codes which are shown below.
https://github.com/facebook/react/blob/7d9e17a9826595dacbf9e19e8f85b07837adf276/packages/react-devtools-shared/src/backend/utils.js#L193
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24543
|
https://github.com/facebook/react/pull/24546
|
34da5aa69b0694348fee9c3cd1351ecc70cd5bb1
|
852f10b5cf188f8aa797f9a809f0caeaa95a4231
| 2022-05-12T09:55:13Z |
javascript
| 2022-05-12T14:29:36Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,539 |
["packages/react-devtools-shared/src/backend/agent.js", "packages/react-devtools-shared/src/backend/legacy/renderer.js", "packages/react-devtools-shared/src/backend/renderer.js", "packages/react-devtools-shared/src/backend/types.js", "packages/react-devtools-shared/src/backend/views/Highlighter/Highlighter.js", "packages/react-devtools-shared/src/backend/views/Highlighter/Overlay.js", "packages/react-devtools-shared/src/backend/views/Highlighter/index.js"]
|
[DevTools Bug]: When inspecting with DevTools, it fails to select correct react component when there are multiple react-dom instances in the application
|
### Website or app
https://codesandbox.io/s/jtiw8m
### Repro steps
When using devtools in the linked codesandbox, I am not able to select react components that are rendered by the micro-fe using the inspect tool.
Steps to reproduce:
1. Go to https://jtiw8m.csb.app/
2. Open React DevTools and click on Inspect icon with the "Select an element on the page to inspect it" tooltip
3. Inspect the component with the pink background and text "micro-fe example heading"
4. Devtools selects `App` as the component (or if the component type filter is disabled, it selects the `div` where the micro-fe is mounted)
Ideally it would actually select either the `MicroFeRoot` component (or the corresponding html node if the filter is disabled).
I was able to get it working by doing [the following change](https://github.com/facebook/react/compare/main...danielkutt:devtools-microfe-bug) in the `react-devtools-backend/src/backend/agent.js`
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
_No response_
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24539
|
https://github.com/facebook/react/pull/24665
|
42b330c1c9bf71ca512c56c204bca36bdd53b3c6
|
3e92eb0fce762aca49d2ea18b869a2fd8a75089e
| 2022-05-11T10:41:10Z |
javascript
| 2022-06-08T20:01:06Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,458 |
["packages/react-dom/src/__tests__/ReactDOMSafariMicrotaskBug-test.js", "packages/react-reconciler/src/ReactFiberWorkLoop.new.js", "packages/react-reconciler/src/ReactFiberWorkLoop.old.js"]
|
Bug: setState is not flushed if an iframe is added in the same tick in Safari
|
Batched state changes are not flushed if the promise code changes the DOM (= attaching an iframe). Reproduceable with Safari.
React version: 18.1.0
## Steps To Reproduce
1. Open [codepen](https://codepen.io/kh-viewar/pen/wvpVLxM) with Safari.
2. Click "Upload"
3. => "Spinner" text does not render while Promise is in pending
Link to code example:
https://codepen.io/kh-viewar/pen/wvpVLxM
## The current behavior
State changes are not executed.
## The expected behavior
State should change to true and render spinner component. After promise is resolved (2 seconds timeout), state should switch back to false and spinner component should unmount.
## Original discussion
https://github.com/facebook/react/issues/24365
|
https://github.com/facebook/react/issues/24458
|
https://github.com/facebook/react/pull/24459
|
62662633d1293f47ab0f5ee444a2a2fd52df322a
|
2c8a1452b82b9ec5ebfa3f370b31fda19610ae92
| 2022-04-28T14:39:31Z |
javascript
| 2022-05-12T16:58:18Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,441 |
["packages/react-devtools-shared/src/devtools/views/Components/TreeContext.js"]
|
[DevTools Bug]: TreeContext error: Can't access property "id" in undefined
|
### Website or app
https://app.replay.io/
### Repro steps
Unfortunately I don't know how to reproduce this bug. It was just logged to Sentry.
It seems like there's a logic bug here though:
https://github.com/facebook/react/blob/bd4784c8f8c6b17cf45c712db8ed8ed19a622b26/packages/react-devtools-shared/src/devtools/views/Components/TreeContext.js#L386-L416
If `selectedElementIndex` is null or `elementIndicesWithErrorsOrWarnings` is empty, then `flatIndex` would be 0 still– and this statement would result in an undefined entry:
```js
prevEntry =
elementIndicesWithErrorsOrWarnings[
elementIndicesWithErrorsOrWarnings.length - 1
];
```
### How often does this bug happen?
Only once
### DevTools package (automated)
react-devtools-inline
### DevTools version (automated)
4.24.4
### Error message (automated)
Error: can't access property "id", n is undefined
### Error call stack (automated)
```text
React ErrorBoundary Error: can't access property "id", n is undefined
at TreeContextController(./node_modules/react-devtools-inline/dist/frontend.js:20793:10)
at SettingsContextController(./node_modules/react-devtools-inline/dist/frontend.js:21419:10)
at ModalDialogContextController(./node_modules/react-devtools-inline/dist/frontend.js:28526:10)
at DevTools_DevTools(./node_modules/react-devtools-inline/dist/frontend.js:44535:10)
at useMemo(./src/ui/components/SecondaryToolbox/ReactDevTools.tsx:269:1)
at ConnectFunction(./node_modules/react-redux/es/components/connectAdvanced.js:220:22)
at Redacted(./src/ui/components/Redacted.tsx:5:83)
at SecondaryToolbox(./src/ui/components/SecondaryToolbox/index.tsx:119:25)
at useGetShowVideo(./src/devtools/client/shared/components/splitter/SplitBox.tsx:25:37)
```
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24441
|
https://github.com/facebook/react/pull/24501
|
024a7274fb07f154676ec6443b83a4e31f259c22
|
d4acbe85d55b6048d65b6ff258b7996516d4aa58
| 2022-04-26T14:07:21Z |
javascript
| 2022-05-05T15:46:57Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,428 |
["packages/react-devtools-shared/src/backend/renderer.js"]
|
[DevTools Bug]: forwardRef components not marked as "rendered" if context changed
|
### Website or app
https://codesandbox.io/s/forwardref-context-change-did-not-render-lpdk4t?file=/src/index.js
### Repro steps
1. Goto https://lpdk4t.csb.app/
1. Start profiling
3. Enter "a" into the input
4. Stop profiling
### How often does this bug happen?
Every time
### DevTools package (automated)
_No response_
### DevTools version (automated)
4.24.3-46a98cff2
### Error message (automated)
_No response_
### Error call stack (automated)
_No response_
### Error component stack (automated)
_No response_
### GitHub query string (automated)
_No response_
|
https://github.com/facebook/react/issues/24428
|
https://github.com/facebook/react/pull/24494
|
c7e494b55320768863b821be96896b28f0a280ef
|
3dc9a8af05f98d185ca55d56f163dbb46e7ad3f4
| 2022-04-23T16:38:15Z |
javascript
| 2022-05-04T20:25:27Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,384 |
["packages/react-dom/src/__tests__/ReactDOMFizzServer-test.js", "packages/react-dom/src/__tests__/ReactDOMServerPartialHydration-test.internal.js", "packages/react-reconciler/src/ReactFiberHydrationContext.new.js", "packages/react-reconciler/src/ReactFiberHydrationContext.old.js", "packages/react-reconciler/src/ReactFiberThrow.new.js", "packages/react-reconciler/src/ReactFiberThrow.old.js"]
|
Bug: Incorrect Hydration Mismatch Detection during Suspense - "Hydration failed because the initial UI does not match what was rendered on the server."
|
React version: 18.0.0
## Steps To Reproduce
1. Add a Suspense Boundary
2. Add a **component that will suspend** to load some data (faked).
3. Render at least one **sibling component** _after_ the suspending component.
3. Render server-side using renderToPipeableStream()
4. Render client-side using hydrateRoot()
__Reproductions in CodeSandbox:__
- [Reproduction 1](https://yt3148.sse.codesandbox.io) with Next.js [Edit](https://codesandbox.io/s/github/xiel/SuspenseHydrationErrorNext)
- [Reproduction 2](https://codesandbox.io/s/brave-euclid-lx3et7?file=/server/render.js) using renderToPipeableStream (based on [example demo](https://codesandbox.io/s/kind-sammet-j56ro?file=/server/render.js:1054-1614))
````jsx
<>
<h4>This headline hydrates fine. </h4>
<SomethingA />{/* Will suspend on client and server */}
<h3>💥 This element after the suspending Component triggers an error (only in development).</h3>
</>
````
## The current behavior
- The sibling component following the suspending component is incorrectly seen as a **hydration mismatch**.
- Console will show errors (and Next.js will show big error overlay):
````
Warning: Expected server HTML to contain a matching <h3> in <div>.
at h3
at IndexPage
at Suspense
at App (webpack-internal:///./pages/_app.js:42:27)
at ErrorBoundary (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:20638)
at ReactDevOverlay (webpack-internal:///./node_modules/next/dist/compiled/@next/react-dev-overlay/client.js:8:23179)
at Container (webpack-internal:///./node_modules/next/dist/client/index.js:323:9)
at AppContainer (webpack-internal:///./node_modules/next/dist/client/index.js:825:26)
at Root (webpack-internal:///./node_modules/next/dist/client/index.js:949:27)
````
````
Uncaught Error: Hydration failed because the initial UI does not match what was rendered on the server.
at throwOnHydrationMismatch (react-dom.development.js?ac89:14344:1)
at tryToClaimNextHydratableInstance (react-dom.development.js?ac89:14372:1)
at updateHostComponent$1 (react-dom.development.js?ac89:20636:1)
at beginWork (react-dom.development.js?ac89:22373:1)
at HTMLUnknownElement.callCallback (react-dom.development.js?ac89:4157:1)
at Object.invokeGuardedCallbackDev (react-dom.development.js?ac89:4206:1)
at invokeGuardedCallback (react-dom.development.js?ac89:4270:1)
````
- Depending on the location of the suspending component and their siblings, there are errors or no errors at all. When the suspending component is the last component, there are no errors logged.
- Error can be suppressed by wrapping the suspending component in a Suspense boundary directly
## The expected behavior
- I expect to be able to use the same fetching mechanism using suspense on server and client in [React v18](https://reactjs.org/blog/2022/03/29/react-v18.html#suspense-in-data-frameworks).
_OR_
- If this is unsupported usage, the errors should be more clear and consistent.
|
https://github.com/facebook/react/issues/24384
|
https://github.com/facebook/react/pull/24404
|
0dc4e6663dc875e0f734b1a96b26ebc33902323a
|
9ae80d6a2bf8f48f20e3d62b9672f21c1ff77bd8
| 2022-04-15T16:28:29Z |
javascript
| 2022-04-20T21:52:54Z |
closed
|
facebook/react
|
https://github.com/facebook/react
| 24,302 |
["packages/react-devtools-shared/src/__tests__/console-test.js", "packages/react-devtools-shared/src/__tests__/utils-test.js", "packages/react-devtools-shared/src/backend/console.js", "packages/react-devtools-shared/src/backend/utils.js", "packages/react-devtools-shared/src/hook.js"]
|
Console dimming on second StrictMode render forces string cast
|
<!--
Please provide a clear and concise description of what the bug is. Include
screenshots if needed. Please test using the latest version of the relevant
React packages to make sure your issue has not already been fixed.
-->
React version: 18.0.0 (congrats on the release ☺️)
## Steps To Reproduce
1. During rendering of a component, log something that doesn't naturally cast to a string (e.g., `console.log(new Set())`).
2. Wrap the tree in `StrictMode`.
3. Observe the console.
Link to code example: https://codesandbox.io/s/magical-roman-wyeud7?file=/src/App.js
Note that the console dimming isn't applied to the inline CodeSandbox dev tools, so to see the issue, you need to visit the "fullscreen view" here: https://wyeud7.csb.app
## The current behavior
In Chrome:
<img width="479" alt="Screen Shot 2022-04-07 at 4 19 09 PM" src="https://user-images.githubusercontent.com/1158733/162289676-bb6ba95f-4f85-4ce3-a179-10dfed3d5ad1.png">
As expected, there are two console logs, one dimmed. Unfortunately, the way that the dimming works forces the second log to be serialized to a string. This has two issues:
1. It can result in two of the "same" logs looking very "different" from each other, which is confusing to developers. For example, in the screenshot above, it's pretty surprising that those two console lines occur from the same `console.log` call.
2. It prevents browser dev tools introspection. This can make it inconvenient or impossible to compare the two values if the string cast doesn't include the value, as in the screenshot above. This is problematic because a key use case of printing both values is to check whether they're the same.
You can kind of work around the second issue by writing your own string cast at the log callsite, but you lose the DX of introspection, which is pretty unfortunate especially in the case of large/deeply-nested objects, etc. Easier to compare two native console values than two `JSON.stringify` dumps.
## The expected behavior
While there is a new (appreciated!) dev tools option to suppress logging for the second render entirely, there is no way to disable the dimming feature.
Any of the following options would solve the issue:
1. Provide a dev tools option to disable dimming.
2. Remove the dimming feature entirely. (So that both logs are always printed the same way.)
3. Update the dimming implementation so that it doesn't force a string cast. (Guessing this isn't possible.)
4. Improve serialization of complex values. (IMO this isn't a great option because it doesn't solve the issue of consistency/confusion, but it would be better than the current behavior if all other options are ruled out.)
Thanks for considering.
|
https://github.com/facebook/react/issues/24302
|
https://github.com/facebook/react/pull/24373
|
ddb1ab1e97588136a3db736696bbc3c8cf9f0210
|
d63cd972454125d4572bb8ffbfeccbdf0c5eb27b
| 2022-04-07T20:49:39Z |
javascript
| 2022-04-14T16:30:04Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.