Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Electron not responding #73

Closed
ligi opened this issue Jul 29, 2018 · 10 comments
Closed

Electron not responding #73

ligi opened this issue Jul 29, 2018 · 10 comments

Comments

@ligi
Copy link
Contributor

ligi commented Jul 29, 2018

I just wanted to try the latest version of frame - but got this error:

electron_103

⋊> ~/g/3/frame on master ◦ npm run alpha                                                     14:32:03

> Frame@0.0.5-alpha.3 alpha /home/ligi/git/3rd/frame
> npm run bundle && npm run launch


> Frame@0.0.5-alpha.3 bundle /home/ligi/git/3rd/frame
> parcel build app/tray.html --public-url '.' --out-dir bundle --target electron

✨  Built in 427ms.

bundle/OpenSans-Bold.b990888e.ttf        219.19 KB     73ms
bundle/OpenSans-Light.2578cc0b.ttf       217.03 KB     73ms
bundle/FiraCode-Retina.a435fe44.ttf         216 KB     72ms
bundle/OpenSans-SemiBold.3b08feff.ttf    215.98 KB     73ms
bundle/OpenSans-Regular.d6b7c5f4.ttf     212.18 KB     73ms
bundle/app.9b5fc577.map                  134.54 KB     72ms
bundle/app.9b5fc577.js                    71.07 KB    125ms
bundle/app.f184f43e.css                   45.64 KB     47ms
bundle/app.f184f43e.js                      1.5 KB     50ms
bundle/tray.html                             255 B     38ms
bundle/app.f184f43e.map                      106 B      6ms

> Frame@0.0.5-alpha.3 launch /home/ligi/git/3rd/frame
> cross-env NODE_ENV=production electron ./main

Chrome: v61.0.3163.100
Electron: v2.0.5
Node: v8.9.3
Trezor Error: { FetchError: request to https://localback.net:21324 failed, reason: connect ECONNREFUSED 127.0.0.1:21324
    at ClientRequest.<anonymous> (/home/ligi/git/3rd/frame/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://localback.net:21324 failed, reason: connect ECONNREFUSED 127.0.0.1:21324',
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED' }
@floating
Copy link
Owner

Hey Ligi!

I just tried to reproduce on Ubuntu 16.04 and 18.04 and was unable to hit the same issue. Can you try to reproduce using npm run alpha again and if you're still hitting this issue try running with npm run dev which will open dev tools for the renderer process and could give us some more info.

Thanks for taking the time to try Frame.

Jordan

@ligi
Copy link
Contributor Author

ligi commented Jul 29, 2018

I am getting the same output with npm run dev

(⋊> ~/g/3/frame on master ◦ npm run dev                                  17:06:42

> Frame@0.0.5-alpha.3 dev /home/ligi/git/3rd/frame
> npm run bundle && cross-env NODE_ENV=development electron ./main


> Frame@0.0.5-alpha.3 bundle /home/ligi/git/3rd/frame
> parcel build app/tray.html --public-url '.' --out-dir bundle --target electron

✨  Built in 615ms.

bundle/OpenSans-Bold.b990888e.ttf        219.19 KB     56ms
bundle/OpenSans-Light.2578cc0b.ttf       217.03 KB     55ms
bundle/FiraCode-Retina.a435fe44.ttf         216 KB     57ms
bundle/OpenSans-SemiBold.3b08feff.ttf    215.98 KB     56ms
bundle/OpenSans-Regular.d6b7c5f4.ttf     212.18 KB     56ms
bundle/app.9b5fc577.map                  134.54 KB    105ms
bundle/app.9b5fc577.js                    71.07 KB    129ms
bundle/app.f184f43e.css                   45.64 KB     30ms
bundle/app.f184f43e.js                      1.5 KB     32ms
bundle/tray.html                             255 B     26ms
bundle/app.f184f43e.map                      106 B      6ms
Chrome: v61.0.3163.100
Electron: v2.0.5
Node: v8.9.3
Trezor Error: { FetchError: request to https://localback.net:21324 failed, reason: connect ECONNREFUSED 127.0.0.1:21324
    at ClientRequest.<anonymous> (/home/ligi/git/3rd/frame/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://localback.net:21324 failed, reason: connect ECONNREFUSED 127.0.0.1:21324',
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED' }
)

@floating
Copy link
Owner

That output looks ok, the Trezor errors occurs when Trezor bridge isn't installed but shouldn't cause an issue. When running npm run dev an instance of Chrome dev tools should open for the renderer process.

@ligi
Copy link
Contributor Author

ligi commented Jul 29, 2018

there are no dev tools opening for me - I made a video: https://www.youtube.com/watch?v=B3VFSMgeDUY

@floating
Copy link
Owner

Interesting, thanks for the video. It may be relate to this issue electron/electron#12850. I will keep looking into it but still cannot reproduce on my end. That issue mentions that built versions still worked so I built an AppImage version of master https://frame.nyc3.digitaloceanspaces.com/Frame-0.0.5-alpha.3-x86_64.AppImage for you to try that might help narrow things down.

You can also (as mentioned in that issue) try adding --disable-gpu to the launch script in the package.json ("launch": "cross-env NODE_ENV=production electron ./main --disable-gpu") and try running npm run alpha again, though I'm not sure what effect that will have on performance.

Thanks,
Jordan

@ligi
Copy link
Contributor Author

ligi commented Jul 29, 2018

thanks - the appimage worked - the --disable-gpu did not

@ligi
Copy link
Contributor Author

ligi commented Jul 29, 2018 •
edited
Loading

where does the hot.json needs to be in case of using the AppImage? And let me know how I can help to investigate the freeze problem any further.

@floating
Copy link
Owner

Hey ligi!

Glad you got it working. The hot.json would need to be in the root directory at build time. You can either do this yourself and build your own apps from source with npm run build or for testing purposes I've built another AppImage of master with some default test accounts already included. https://frame.nyc3.digitaloceanspaces.com/Frame-0.0.5-alpha.3-x86_64-with-test-accts.AppImage

Let me know if you have any issues or feedback, thanks again!

Jordan

@ligi
Copy link
Contributor Author

ligi commented Jul 30, 2018

I might have a data-point on this that could help getting closer to the root of the problem. When executing the appimage and frame is directly executed afterwards -> I get the same freeze. But when opening via the launcher -> it works.
Video here: https://youtu.be/WUzJfXuR8x0

@floating
Copy link
Owner

I believe this is no longer an issue. If I'm incorrect please let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ligi @floating