I've built an Electron app using the Squirrel packager/update manager.
I've had no issues in building the bundle, targeting Windows 64bits only.
I installed it on my Macbook pro (on a windows 7 x64 dual boot) without trouble. I tested it also on a 64 bit Surface pro 3 (Win 10), and another Win 7 PC. Everything works fine.
I published the app and got a few hundred downloads :half the people that downloaded it has it working, and for the other half it just won't start. The process spawns, then dies a second after. I tried starting it in admin, the admin dialog box won't even show. I tried running it from command line
myapp.exe > out.txt
But out is empty. How can I debug this ?
I was having trouble getting the logs for a production build as well.
My solution was to use electron-log to let the production app write logs to disk while debugging the problem.
You can then access the logs on windows at:
%USERPROFILE%\AppData\Roaming\<app name>\log.log.
Add some logs in your app that will give you insights in where the app crashes.
Don't forget to remove electron-log when you're done debugging and don't need to write any logs to disk any more.
I solved it for many users by building directly on a windows 10 fresh install.
The builds I used before were built on a windows 7. Not sure if it was that, I also have been cleaning the node modules a little bit, so maybe one of the modules I removed was the issue. Anyways, I still do not know of to debug the built exe in this kind of situation. There must be a way to get a log or something when the process kills itself
Related
I have written a JavaFX app running on Windows 10 machine in the office which has problems showing (painting/rendering) certain embedded controls such as a Pane with PdfBox when I connect to it with Remote Desktop for Mac. It shows only a black screen in the app instead of the pdf document.
When I connect using RDP from my Windows 10 machine at home to my Windows 10 machine at work, the app works just fine (the pdf is shown in the app).
I have the same problems using AnyDesk and Teamviewer.
The app only shows PDFs properly using a connection from Windows 10 to Windows 10 with Microsoft RDP.
It might be a JavaFX issue. Similar issues are described here (although not 100% identical):
https://bugs.openjdk.java.net/browse/JDK-8239589
https://bugs.openjdk.java.net/browse/JDK-8229394
However, since I guess Microsoft Remote Desktop for Mac is using the same technology as the Windows Desktop client, I would have expected it to work fine.
I have a Mac Mini M1 running the latest OS (Monterey) at the time of writing this post. I am also using the latest Remote Desktop client for Mac.
This problem is not new and was also present in older releases.
I have tried to play around with screen resolutions, both on Host and Client but nothing good came out of those tests.
Disabled also hardware acceleration in Remote Desktop for Mac preferences but it didn't change anything.
The machine at the office has the following specs (which I cannot change nor update)
Edizione Windows 10 Pro
Versione 20H2
Data installazione: 10/09/2021
Build sistema operativo 19042.1415
Esperienza Windows Feature Experience Pack 120.2212.3920.0
Anyone else who has seen this problem and perhaps resolved it?
Could it be a bug in either PdfBox or Remote Desktop for Mac?
Except for the above issue, the Remote Desktop Client for Mac is working great (not lagging as TeamViewer or AnyDesk) and the user experience is phenomenal.
PS: While this might be considered a programming question (since I wrote the app with JavaFX) but it might be better to post on another forum? If yes, which one? On the other hand, many similar posts (look at the suggested thread on the right) have been upvoted despite not dealing with programming issues.
Thanks.
How do you use PDFBox? I ask because this is not a JavaFX component. If you use a SwingNode for that it might be interesting to try one of my two PDFViewer demos here and see whether the problem persists.
https://github.com/mipastgt/JFXToolsAndDemos#awtimage
The difference is in how I do the rendering and maybe that makes a difference for your use-case too. But of course this is just a wild guess and I can't promise anything.
I have a number of SD-cards, with Windows IoT Core installed, which has been running in Raspberry Pi 3b for a time, sometimes weeks and sometimes months. They all have some kind of boot issue. Some wont boot at all, I can't even reach the Windows Debug Portal, so I assume that the installation of Windows IoT Core are totally broken. Some boot fine most of the time and sometimes fails with an error which reboots after a couple of seconds and often times manage to boot properly.
I have tried to follow this guide: https://learn.microsoft.com/en-us/windows/iot-core/manage-your-device/windowsdebugger#raspberry-pi-2-or-3-rpi2-or-rpi3 but when I try to run:
bcdedit /store c:\EFIESP\EFI\Microsoft\Boot\BCD -debug on
I get: An error occurred while attempting to access the specified entry. The system cannot find the file specified..
Blue Screens are also pretty common, when they happen the system does not reboot as far as I have seen.
I know that the devices are fine and working, and the SD-cards also seems to be fine, no broken partitions or similar.
How do I find out what went wrong?
When using my virtual machine, I'm trying to gain access to the Internet, but unable to get IE to start, when clicking the icon it doesn't react. I've done some research and a couple of hours troubleshooting, but no luck. It does appear to be a problem for some, but they don't have the exact same problem I do.
Here's what I've come across while troubleshooting:
1) OS is windows 8.1 32-bit, but my host machine is 64-bit, because of this there might be compatibility issues. Not much more on this though, no explanation on whether that is the problem at all.
2) My network settings could be wrong, but I'm attached to a bridged adapter, my IP's match for both VM and Host, and I can access the web when I use a web browser app (but the app that can't download anything, so I can't download google chrome or the necessary files I need to study).
3) Others say that the problem is Windows 8.1 itself. That VMs just don't work as they should like Windows 7.
I clicked to uninstall Windows explorer, but it seems it doesn't exist, and it doesn't have an icon on the home screen.
Could it be that the .iso I downloaded did not have IE included?
The original need for the VM was to test Docker containerisation for a report. Should I scrap the whole idea and try for Windows 7 64-bit instead? That's all I can do if I can't find a solution.
Any help would be appreciated. Thanks.
I have been using Windows 7 applications within Mac iOS software for a few months (using Parallels), but recently it has stopped working. Every time I try to open a windows 7 application the application shows a broken, corrupted page that looks like static.
I have tried uninstalling and reinstalling Parallels but this has been unsuccessful.
Thank you in advance.
Also, just before this happened my computer prompted that I was running out of memory.
Restart your computer and reset PRAM by holding down
'cmd+option+p+r'
After that try opening up the application again. If the issue persists, close the windows session and allow it to use some more memory and try again.
I have had basic tests for meteor on a Windows7 PC.
But there the application crashed too often.
Before this, I tested meteor on PC running Windows8. There, crashes happened much less often and generally they were recovered when I shutdown and rebooted the meteor.
Is Meteor unstable on windows7?
Or is there any way to avoid this?
The version packaged to the MSI installer that can be found on win.meteor.com is not official. If you want a more stable, try the virtualized option I've described on the site. I've been using that for a month without issues.
Please could you be specific about what problems you are seeing, for example, what do you mean by 'crash'.
You can certainly raise issues on SO, but if they appear to be specific to the windows port, please raise a ticket at: https://github.com/sdarnell/meteor
The only difference between Win7 and Win8 meteor, is that the installer sets the Win7 compatibility mode for the node.exe executable on Windows 8.
There are also relatively few differences between the windows port of meteor and the official linux/mac release. So there is a possibility that the issue is either environmental (e.g. you have different things installed on the two machines), or it may even be a core issue that just happens to appear more often Win7 due to timing issues (there was a case of this in 0.6.3).