Question

我之前使用过的每一个BAD_ACCESS通常都是一个快速错字修复，但是这个非常混乱

此代码应该下载.ics google日历文件，然后将其传递给解析器函数，该函数将返回一个Event对象数组（此处未包含）

问题是，在物理iOS设备上测试时，每次第3次运行loadEventIntoCalendar（）时，调用此行时都会抛出EXC_BAD_ACCESS

tempHold = calendarString.substring(with: tempRange)

在event（）函数的while循环中。

我尝试用许多不同的技术解决这个问题。 Zombie对象直接向上不会在日志中打印任何内容。我尝试用 Instruments 分析运行但我没有找到任何有用的东西。我尝试在参数中传递的String文件的单独副本，但没有改变任何东西。

我很肯定这个问题与calendarString有关，或者至少与指向的值有关。我尝试通过Xcode分析内存块，但我找不到任何变量，这将指向导致错误的内存位置。

我非常确定RAM不会过载，因为整个应用程序最多只占用大约70兆字节（用 Instruments 检查）

events（）应该是一个单独的静态函数。

以下是两个功能

func loadEventsIntoCalendar() {
    // The link from which the calendar is downloaded
    let url = URL (string: "https://calendar.google.com/calendar/ical/wlmacci%40gmail.com/public/basic.ics")!


    // The process of downloading and parsing the calendar
    let task = URLSession.shared.dataTask(with: url, completionHandler: { (data, response, error) in
        // The following is simply a declaration and will not execute without the line 'task.resume()'
        if let URLContent = data {  // If Data has been loaded
            // If you got to this point then you've downloaded the calendar so...
            // Calendar File parsing starts here!!!
            // The string that holds the contents of the calendar's events
            var webContent:String = String(data: URLContent, encoding:String.Encoding.utf8)!
            self.events(forCalendarFile: &webContent, inCalendar: Calendar(identifier: Calendar.Identifier.gregorian))
        }
    })
    task.resume()
}

// Calendar Parser for this VC
func events(forCalendarFile webContent:inout String, inCalendar calendar:Calendar) {
    // The reason for this complication is, i thought copying the object might solve the issue, it did not :(
    let NSWebContent = NSString(string: webContent)
    let calendarString = NSWebContent.copy() as! NSString

    // An array of flags used for locating the event fields
    // [h][0] - The flag that marks the begining of a field, [h][1] - The flag that marks the end of a field
    let searchTitles:[[String]] = [["SUMMARY:", "TRANSP:"], ["DESCRIPTION:", "LAST-MODIFIED:"], ["DTSTART", "DTEND"], ["DTEND", "DTSTAMP"], ["LOCATION:", "SEQUENCE:"]]

    // The range of "webContent's" content that is to be scanned
    // Must be decreased after each event is scanned
    var range:NSRange = NSMakeRange(0, calendarString.length - 1)
    // Inside function that will be used to determine the 'difference' range between the begining and end flag ranges.
    let findDifference:(NSRange, NSRange) -> NSRange = {(first:NSRange, second:NSRange) -> NSRange in
        let location = first.location + first.length, length = second.location - location   // Determine the start position and length of our new range
        return NSMakeRange(location, length)                                                // Create and return the new range
    }
    // Inside function that will be used to move the searching range to the next event
    // Returns an NSNotFound range (NSNotFound, 0) if there are no more events
    let updateRange:(NSRange) -> NSRange = {(oldRange:NSRange) -> NSRange in
        let beginingDeclaration = calendarString.range(of: "BEGIN:VEVENT", options: NSString.CompareOptions.literal, range: oldRange)
        // If the "BEGIN:VEVENT" was not found in webContent (no more events)
        if NSEqualRanges(beginingDeclaration, NSMakeRange(NSNotFound, 0)) {
            return beginingDeclaration  // Return an 'NSNotFound' range (Named it myself;)
        }
        // Calculate the index of the last character of 'beginingDeclaration' flag
        let endOfBeginingDeclaration = beginingDeclaration.location + beginingDeclaration.length
        // Calculate the length of the new range
        let length = oldRange.length - endOfBeginingDeclaration + oldRange.location
        // Calculate the starting location of the new range
        let location = endOfBeginingDeclaration
        // Create and return the new range
        return NSMakeRange(location, length)
    }

    // A holder for the begining and end flags for each event field
    var fieldBoundaries:[NSRange]
    // The actual parsing of each event
    repeat {
        range = updateRange(range)  // Move our searching range to the next event
        if NSEqualRanges(range, NSMakeRange(NSNotFound, 0)) {   // If there are no more events in the searching range
            break;                                              // Then no more shall be added (break from the loop)
        }

        var tempHold:String!
        // Record each field into our event database
        for h in 0...searchTitles.count-1 {
            fieldBoundaries = [NSRange]()   // Clear the fieldBoundaries for the new search
            fieldBoundaries.append(calendarString.range(of: searchTitles[h][0], options: NSString.CompareOptions.literal, range: range))   // Find the begining flag
            fieldBoundaries.append(calendarString.range(of: searchTitles[h][1], options: NSString.CompareOptions.literal, range: range))   // Find the ending flag
            let tempRange = findDifference(fieldBoundaries[0], fieldBoundaries[1])
            print ("Isolating event content")
            tempHold = calendarString.substring(with: tempRange)                         // Create a new string from whatever is in between the two flags. This will be the current field of the event
            print ("Event content isolated")
            tempHold = tempHold.trimmingCharacters(in: CharacterSet.newlines)                                           // Remove all /r /n and other 'new line' characters from the event field
            tempHold = tempHold.replacingOccurrences(of: "\u{005C}", with: "", options: .literal, range: nil)           // Replace all backslashes from the event field
        }
    } while (true)
}

这必须很快完成，因此将非常感谢快速回复。

提前致谢！

Answer 1

据我所知，字符串搜索方法并不能保证结果范围的长度为0。如果更换两个范围检查会发生什么？

if range.location == NSNotFound { ... }

而不是

if NSEqualRanges(range, NSMakeRange(NSNotFound, 0)) { ... }

Answer 2

实际上，我最终做的是完全重写算法。它的工作方式有点不同，现在实际上要短20行，速度要快得多。

感谢您的关注！感谢帮助：）

幻影EXC_BAD_ACCESS

2 个答案: