Skip to content

Commit 219aed3

Browse files
authored
Remove section on debugging Backburner
This has been incorrect for quite awhile per emberjs/ember.js#20001
1 parent 4161001 commit 219aed3

1 file changed

Lines changed: 0 additions & 19 deletions

File tree

guides/release/configuring-ember/debugging.md

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -80,22 +80,3 @@ window.addEventListener('error', function(error) {
8080
});
8181
});
8282
```
83-
84-
### Errors within `run` Backburner
85-
86-
[Backburner.js](https://github.com/ebryn/backburner.js) has support for stitching the stacktraces together so that you can
87-
track down where an error thrown by `run` is being initiated from. Unfortunately,
88-
this is quite slow and is not appropriate for production or even normal development.
89-
90-
To enable full stacktrace mode in Backburner, and thus determine the stack of the task
91-
when it was scheduled onto the run loop, you can set:
92-
93-
```javascript {data-filename=app/app.js}
94-
import { run } from '@ember/runloop';
95-
96-
run.backburner.DEBUG = true;
97-
```
98-
99-
Once the `DEBUG` value is set to `true`, when you are at a breakpoint you can navigate
100-
back up the stack to the `flush` method in and check the `errorRecordedForStack.stack`
101-
value, which will be the captured stack when this job was scheduled.

0 commit comments

Comments
 (0)