I'm working a chrome extension development. I stored some data on Chrome using chrome.storage. Sometimes, my mac uses too much memory and I will just force to close all the apps and restart macOS to free the memory. It took a long time for my mac to restart. So I press the power button to reboot my mac. Later I successfully login to my system. It turned out that my data store in chrome via chrome.storage is lost.
Do you know what happened? How do I avoid this kind of issue?
Related
Lately I've been using screen utility a lot on my Windows 10 PC via Cygwin. I usually open 5-6 screen sessions and do my work. Every time I reboot my system and start screen, it says my old screen sessions are dead and need to be wiped out before starting a new one. I'm wondering, is there a way we can make the sessions persist after reboot and I can do something like 'screen -x' and taken back to my old set of screen sessions. Thanks.
Long story short, windows 10 is utterly broken on my laptop after it automatically installed some updates. It's now stuck in a loop which always ends up saying "Undoing changes made to your computer"
I can't get into the BIOS.
I can't get into the Windows Recovery Environment.
Been talking to MS support for far too long so far, so I'm wondering if it's possible to add it as a secondary disk drive to another machine that does work, and manually remove any updates that were installed directly through the filesystem?
The only solution MS were willing to offer was to format the whole drive and re-install windows.
When I moved the HDD into a working windows 7 machine it actually prompted a chkdsk to run over the disk.
It found a whole load of orphaned files, not sure if that was really the cause, but after backing up as many files as I had access to, I put the drive back into the other machine and now it boots.
tl;dr, chkdsk fixed it.
I was stuck in this loop last night
machine configuration : Dell Inspiron
windows 10 (original)
What the one thing you can do is to use an application name Dell usb recovery tool. You will have to format you whole computer be it c:// or any other. You will need an extra hard drive to make a backup.
the process goes like this.
You will have to install the above application on other computer and open it and fill your service tag and make that pen drive bootable with that application.
Now plug in that pen drive to the laptop.
Go for troubleshoot.
Repair.
Install new original os.
It will ask for backup make a backup to other HDD.
Install and recover your backup.
We've created a Windows 10 application that runs on tablets in Windows 10 kiosk mode. It works just fine, however, the wifi connection gets lost sometimes since the locations are very remote. We tried fixing the issue from the networking side, but when the devices lose and regain internet access the application will still hang as if it doesn't have internet access displaying a blank page. Where these devices are used, they are bolted into the wall to prevent theft. Which means if we want to reboot its very time consuming as we have to unscrew the cases off the wall and then open the cases to gain access to the power button, and the only way to get the application to run successfully again is to do a reboot on the device.
It was suggested that we have a way to perform a reboot from the application, however, every code example I've tried doesn't work in Windows 10 UWP. Here is the most common one I've found:
System.Diagnostics.Process.Start("restart", "/r");
I have access to the namespace
System.Diagnostics
but the Process class does not exist. Anyone have suggestions on rebooting via code on Win 10 UWP? Or a better solution to our issue? Thanks in advance.
It's also worth mentioning I tried execute a Powershell command too and the dll I need to reference for the Powershell class is not compatible with UWP.
What you require is not possible with the APIs available to UWP apps. This was a security decision. An app distributed through the store shouldn't be able to do things like restart machines.
Based on your scenario though you shouldn't need to go through the store. This means that you could PInvoke native code to do whatever you want. This would still need to be initiated on the actual device.
Yes you can do that!
You should add IoT System Administration in App capability declarations:
<Capabilities><iot:Capability Name="systemManagement"/></Capabilities>
and also You need to have "Windows IoT Extension for UWP" added to your project
using this for Shutdown
Windows.System.ShutdownManager.BeginShutdown(Windows.System.ShutdownKind.Shutdown, TimeSpan.FromSeconds(1)); //Delay is not relevant to shutdown
or for Restart
Windows.System.ShutdownManager.BeginShutdown(Windows.System.ShutdownKind.Restart, TimeSpan.FromSeconds(1)); //Delay before restart after shutdown
You can get more information in this Link
Okay, I'm trying to implement fast switching on my app, and if I don't have to execute any background code / save any user data, do I really even need to do anything ? Or do I just upgd to iPhone SDK 4.0, click compile, and deploy?
Is there any way to simulate an out of memory exception, make the OS purge the application to test how it's being relaunched?
Thanks,
Teja.
If all you want is fast-user switching, I found that recompiling with the iOS4 SDK is sufficient in order to make your app 'fast-switch ready.' You just need to make sure your app can deal with memory warnings and being able to restore any data you had to release as a result of a memory warning.
The easiest way to simulate a memory warning is through the iPhone simulator, under Hardware -> Simulate Memory Warning. Personally, I used the Mac OSX Keyboard preferences to set a hot-key for that menu item so I can quickly simulate memory warnings on my app.
I have a Windows application that exports to Excel using the Excel Object Module (programming module). It has worked fine on all Winodws versions except Windows Server 2008. It takes about 2 seconds to do anything in Excel, making the process take minutes or even hours to complete what normally takes a few seconds.
This happens when using Terminal Services or RemoteApp. I discovered that it only happens when you check the Printers checkbox under Local Resources when connecting via Remote Desktop. If you uncheck it the speed is normal.
However, I need my printers, so I can't just uncheck it.
Any ideas what is causing the slow down?
The MS Office apps do a lot of calculation in the background based on the default printer. When you connect from a remote Terminal Services session and import the Printers from your Local Resources, the Terminal Server really needs to have an appropriate driver for each printer you're connecting.
Thus, one solution to the speed issue would be to ensure that the server has the right drivers (and that they work as expected).