I am getting crash like this in fabric crashlytics:
WebCore
bmalloc::IsoAllocator >::allocateSlow(bool)
Any clue to resolve this issue?
i'm getting same crash.
in my case, when large html load on webview and inline css in the html was reason.
check your html content.
this is knowledge in my case. not a question.
more detail is
i'm using UIWebView.
my same crash was to occur when client updated on ios 11.3
i checked all webview.
when call loadrequest on uiwebview function.
crash occured when large html load. the html content size was
char length 80000 ~ 200000. it's breaking on css in html content.
this is my case. I hope it helps.
In my case it helped to set the webView.delegate to nil after I used the webView.
Related
There are many crashes reported for WebKitLegacy on Crashlytics and I have been using webview in my application. There is no way to figure out why these crashes occur. I have set the delegate and webview to nil in viewwilldisappear method. But still it is crashing. Can please someone help me in this?
[
This error might be misleading. Are you using NSAttributedString to load HTML or to display "web link" like button? If so you might be calling the HTML importer from a background thread. See details here:
Unable to reproduce WebKitLegacy -[_WebSafeForwarder forwardInvocation:] crash
I have a project with iOS8.0+ support. I am using a WKWebView to load payment page; the page is working fine on iOS 11.0+ but it is showing bad Syntax for iOS 9 and 10. The info inside the loaded request are fetched from the server so there is no possibility that the error is in the request information.
Can anyone help me with issues known about WKWebView or any other similar issue?
There is a bug in WKWebView before iOS 11 that requires programmatic creation of the WKWebView instance (so you cannot do it from Storyboard).
A discussion & resolution of this issue can be found here:
Xcode 9 GM - WKWebView NSCoding support was broken in previous versions
Unfortunately I auto-updated Xcode to Version 5.1.1 (5B1008), and now one of my apps crashes in a very strange way.
The app is a PhoneGap 3.4 (+ jQuery Mobile 1.3.1) hybrid app, the crash happens when I try to open a JQM page that contains ~20 JQM checkbox.
The crash happens in CoreGraphics CGPathAddLineToPoint called by WebCore WebCore::RenderThemeIOS::paintCheckboxDecorations in the WebThread, I guess when WebCore attempts to render the checkboxes on then JQM page.
The console reads:
Assertion failed: (CGFloatIsValid(x) && CGFloatIsValid(y)), function void CGPathAddLineToPoint(CGMutablePathRef, const CGAffineTransform *, CGFloat, CGFloat), file Paths/CGPath.cc, line 224.
(lldb)
Any other JQM page NOT containing checkboxes is displayed properly, and it does not crash the app.
EDIT: interestingly, the crash is triggered by this line of Javascript:
$('#my_checkbox').prop("checked", my_boolean_value).checkboxradio("refresh");
If I disable it, the JQM page shows up. But then, even if the above line is disabled, if I click on any checkbox, it crashes again, with the same above Assertion failed message. (I guess because JQM toggles the check/unchecked class.)
I already performed all the tricks I could think of (clean, disable debugger, reboot, reinstalled Xcode), with no luck.
Any ideas on how to solve this issue?
I discovered the following very irritating fact: the crash is triggered by a
opacity:.01
directive, attached to the JQM .ui-checkbox class in my CSS.
Changing it to:
opacity:0
prevents the crash (which I still do not know if it is due to an Xcode bug or an iOS bug).
Interestingly, setting any value greater than 0 triggers the crash.
I had a similar issue,but it was caused by an attributed text link. I ended up having to change "Continue..." to "Continue"
I have being seeing crashes in my iOS app, when opening LA Times (www.latimes.com). The crash happens in WebCore somewhere and I have no clue where. Profiling with both "Zombie" or "leaks" do not return anything for this "EXE_BAD_ADDRESS" error.
I also checked with a small, bare UIWebView app and I could reproduce the effects.
Right now, I see this happening only with LA times, but I am not sure if there are other sites as well.
Can someone check on and guide me in what could be the possible error/source for this crash?
EDIT: I have added a small UIWebView project demonstrating this bug at
github
EDIT 2: The app (include the demo at github) works perfectly fine on iOS 7.0, but crashes in iOS 7.1 ... seems a recent bug with iOS 7.1. I have issued a bug report to Apple and will keep updated.
Thanks in advance,
Nikhil
I happened to bump into that same issue with one of my apps in iOS>7.0 only.
It seems to be a sync issue which can be fixed by creating the webview from the main thread only.
As a fix I just wrapped my UIWebView creation in a dispatch_sync(dispatch_get_main_queue(), ^{ ... });
And it solved the problem.
Of course if your code is running on the main thread you shouldn't wrap it this way ;)
I have an app with multiple webViews, on iOS6 it loads perfectly (sometimes I have to manually refresh the webviews content, and it works fine), but on iOS7 (the same code, the same sdk-ios7sdk) the webViews loads the first time, then if i hit refresh i get -999 error code, if i navigate to a page, then refresh the webviews data, then go back to view the webview, it works...
Here's the error message:
Error Domain=NSURLErrorDomain Code=-999 "The operation couldn’t be completed.
(NSURLErrorDomain error -999.)" UserInfo=0x9ba3220
{NSErrorFailingURLKey=file:///Users/jakaba/Library/Application%20Support/
iPhone%20Simulator/7.0/Applications/.../myapp.app/page.html,
NSErrorFailingURLStringKey=file:///Users/jakaba/Library/Application%20Support/
iPhone%20Simulator/7.0/Applications/.../myapp.app/page.html}
Any idea?
Thank you in advance!
I would look at this question:
How do I fix NSURLErrorDomain error -999 in iPhone 3.0 OS
The error code you're seeing is caused by two simultaneous requests on the UIWebView. This can be caused by a couple of things. Is your HTML doing any redirects? How are you loading the content into the UIWebView?
Anyway, take a look at the question I've linked to and see if it helps you. As to why you're seeing this on iOS 7 and not 6 - WebKit is improved in 7, and you may be encountering a race condition you didn't before due to speed.