-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Endless frame processing #11459
Comments
I believe I have found another occurrence of this problem in a certain application. I encountered this while working with CasperJS, but I believe it is PhantomJS related. When using SlimerJS for example it all goes well. My apologies for placing CasperJS logs and code here, but I am not experienced enough to whip up a PhantomJS only reproducable script. My PhantomJS version is 1.9.2, the precompiled win32 build straight from the website.
It just keeps at that, I can wait for hours but then I finally press ctrl-c. My sincere apologies for posting CasperJS code on the PhantomJS issue tracker, but only this way I can show you how to reproduce. var casper = require('casper').create({
verbose: true,
logLevel: "debug",
});
casper.start('http://natschool.rijnijssel.nl/', function() {
this.capture('screencap.png');
});
casper.run(); |
I have the save problem with you.Is this bug fixed ? |
I have a a very similar problem, using 1.9.0. Is there any update on this? |
yup same problem but a year later... must of been fixed |
Due to our very limited maintenance capacity, we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed (see #15395 for more details). In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution! |
Example command:
GDB:
GDB BackTrace:
This bug is 100% is not connected with InterruptJavaScript callback. I'll try to investigate further on my side
The text was updated successfully, but these errors were encountered: