Core Data model attribute with type binary and "Allow External Storage" enabled cause crash in NSPersistentCloudKitContainer sync mechanism.
This happens only on receiving device, meaning upload to CloudKit is successful, but download from CloudKit causes crash when in NSManagedContext.
<NSSQLSaveChangesRequestContext: 0x281ec8420> , *** NSAllocateMemoryPages(28317598) failed with userInfo of (null)
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** NSAllocateMemoryPages(30318498) failed
This is obviously a memory crash, but I can't figure out how to workaround it, it seems to be an iOS bug.
You are not alone!
It's not something you are doing wrong, if you disable "Allow External Storage" option (and delete the app from your device to avoid migration crash) it will sync fine.
Obviously it's something wrong with "Allow External Storage" option, and files bigger than a few mb.
In my app I was syncing png images. Those who were bigger than ~28mb (if I can recall the size correctly), couldn't sync to a device and made it crash.
I submitted a bug report with Feedback Assistant, and for the first time Apple asked for more details. I send them a sample app.
Edit:
Good news folks!
Apple flagged my bug report with "Potential fix identified - For a future OS update".
I'll check Xcode 12 beta if its fixed and report back.
Edit 2: For iOS 14 and Xcode 12, the bug has been fixed! Yay! 🎉
Related
My Binary file cannot be registered on galaxy store. After i uploaded the apk i get this error(This binary cannot be registered. please try again later).
Apparently after several tries and error elimination in vain as there were not any technical errors concerning the app. The only error was a glitch in my connection. Trying a different connection solved the problem. The process is straight forward as described both on amazon and Samsung portal.
Errorcode is 05 Access Denied/48 Unable to Log Transaction, this has come from RTL, not a custom function message, and only happens sometime when tokens are being fetched from database.
Everytime I trigger this function I use to get different error, what might be the reason, I have attached the screenshot but I wanted to know the root cause, why these errors are different everytime, would these be a TPS database related error.
Application is developed in Clarion 6.0 and compiled i n 8.0 and these issues don’t come up regulary, this errors are intermittent and occur at any stage, if it works smooth it doesn’t cause any issues but once issue pops up it will keep coming, any idea on these, do you think these is the code issue or can be a clarion custom error?
Files are on network drive and db is topspeed.PFA
My app has been test running without crashes for some weeks now. However, in Logcat there are 3 persistent errors (lines marked with "E"). I do not know how to solve them, but they do not appear to harm the proper functioning of the app.
E/zygote64: Failed sending reply to debugger: Broken pipe
E/MemoryLeakMonitorManager: MemoryLeakMonitor.jar is not exist!
E/vndksupport: Could not load vendor/lib64/egl/libGLES_mali.so from sphal namespace: dlopen failed: library "vendor/lib64/egl/libGLES_mali.so" not found.
How usual is it for developers to publish apps (like on Google Play) that knowingly have errors in them that don't seem to be "mission critical"?
The google play console has a 'Bad beheivour treshold' of '1.09%'.
This is calculated by: 'Percentage of daily sessions during which your users experienced at least one crash. A daily session refers to a day during which your app was used.'
So you should aim to have a lower crash rate of 1.09%. There will always be bugs in your app that you haven't encountered yet in in your tests so an app will (almost) never be completely crash free. So a lot of developers publish their apps while there are still (mostly unknown) error's in them.
Sadly enough I can't help you with your exact errors but I hope I have helped you with the Google Play Console Guidelines.
After upgrading system to Windows 10 - os 1803 we are getting below issues while working with ClearCase 8.0.1.x/9.0.1.x
Unable to checkin/checkout.
Not able to create views.
Not able to add any file to source control.
The system hangs & crashes while performing any ClearCase operation.
There is no error message, but I have attached screenshot for reference.
Please let us know if there is any issue with the Windows 10 ver(1803), any security system enabled?
Or has ClearCase provided any fix?
We have tried 9.0.1.5 and issue still persists.
This is what we got from windows event log.
The computer has rebooted from a bugcheck.
The bugcheck was:
0x000000c2 (0x0000000000000004, 0x00000000535be990, 0x000000000004efd3, 0xfffff803e01848b1)
for most of them whoever has upgraded to windows 1803 ver :( for people who are still using ver1709 it is working perfectly fine
Then I would recommand contacting IBM support: only them can update their ClearCase 9/Windows 10 compatibility matrix and confirm if MVFS is supported on a more recent (1803) Windows 10 edition.
We also facing same problem and I have raised the case with IBM. Still not yet resolved. As IBM said there are some limitations to work ClearCase with windows 10 and windows 2016.
We tried all the options except Secure boot disable. If possible please do disable secure boot option in Windows 10 and try to checkin/checkout code from CleraCase
Note : It works for Snapshot views. That means the issue related to MVFS
I'm seconding #VonC's recommendation to open a ticket with IBM. When you do that, save a step and collect a clearbug2 and a kernel memory dump to send in as soon as the case is opened. It will save the turn-around time of us asking you for it. If the installed programs list doesn't list installed security software (DLP, Privilege management sw like Avecto, other endpoint security tools), please list those separately as well.
I would also love to know who # IBM told you there are "limitations" with Win10-1803.
There are a few issues with Windows 10 "version upgrades" breaking things, but they generally don't cause system crashes. Windows 10 upgrades are actually full OS installs that then (imperfectly) migrate application settings. Anything that uses custom network providers (ClearCase is one example) will find that the network providers will be broken or partially broken. Reinstalling is usually required. Again, that has not yet been reported as a cause of a BSOD.
If the upgrade/reinstall didn't fix view creation, please post a separate question on the view creation issue. There may be things we can do to the SMB 2 caches to allow view creation to work in cases where the view storage is not on the client host.
I noticed that the screen shot you posted is a Terminal Services disconnect screenshot. Does the issue only occur over a Terminal Services client connection or does it also happen on a local connection?
My Azure Functions were running fine and all of a sudden I am getting several "Assembly changes detected. Restarting host..." messages that is preventing my functions from completing.
I am not deploying new code so not sure what is triggering the Assembly Change event to fire. I was running on the latest version of the runtime and have since reverted to version 1.0.10947 thinking that maybe the underlying runtime was updated, but I'm still getting that line showing up in the logs.
Update
Now that #Alexey has helped me track down what is causing the Assembly changes to be detected. I would like to ask if anyone can tell me WHY an assembly change is being detected even-tough I have not changed/redeployed my application.
After looking in your logs we opened an issue https://github.com/Azure/azure-webjobs-sdk-script/issues/1533#issuecomment-303595960.
Your functions had multiple restores but now issue is gone. Restores could be initiated by changing project.json.
If you are stuck with the multiple
Assembly changes detected. Restarting host
I fixed my issue by deleted the log file in the Kudu services:
https://[FunctionAppName].scm.azurewebsites.net/
and follow on the top menu:
Debug Console >> powerShell
And the file log is :
LogFiles >> Application >> Functions >> function >> [Function name]
You can remove the log file.
my 2c.
I was struggling with this issue for ages and not sure what was causing it. I believe I may have the answer.
Our solution has been toying with consumption plans, but pulled back to full App Service Plans because the initiation times were too long for our rather unique usage patterns.
But 2 of the appsetting params were still in place: WEBSITE_CONTENTSHARE And WEBSITE_CONTENTAZUREFILECONNECTIONSTRING.
per:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#websitecontentazurefileconnectionstring
these are ONLY for consumption plans.
I removed them and... touch wood, the issue seems to be resolved.