Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B Bolts-ObjC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BoltsFramework
  • Bolts-ObjC
  • Issues
  • #252
Closed
Open
Issue created May 20, 2016 by Nikita Lutsenko@nlutsenko

Removal of automatic exception catching.

This is an issue to track removal of automatic exception catching. Currently BFTask continue* methods automatically catch exceptions, unless you disable them via BFTaskSetCatchesExceptions().

This functionality leads to inconsistent behavior and big memory leaks, because ARC by default is not going to cleanup the memory that was not released at the time the exception was thrown. As an improvement to the API and consistency with Bolts-Swift - we are removing automatic exception catching from Bolts-ObjC.

Currently planned version that this will be removed in is 1.9.0.

Assignee
Assign to
Time tracking