search

peerigon / phridge

A bridge between node and PhantomJS
The Unlicense
519 stars 50 forks source link

[CRITICAL] QNetworkReplyImpl: backend error: caching was enabled after some bytes had been written #23

Closed suroorwijdan closed 9 years ago

suroorwijdan commented 9 years ago

I am trying to spawn multiple child phantom processes using phridge which perform certain tasks like submitting form.

Everything works fine when the number of processes is less then 8 but as soon as i try to spawn 8 or more then 8 phridge process i get the below error. 

2014-11-26T14:41:31 [CRITICAL] QNetworkReplyImpl: backend error: caching was enabled after some bytes had been written
2014-11-26T14:41:31 [CRITICAL] QNetworkReplyImpl: backend error: caching was enabled after some bytes had been written

Is it something related to PhantomJS itself, i am using the latest build of PhantomJS 2. ?

jhnns commented 9 years ago

Mhmm strange... I haven't tried phridge with PhantomJS 2 yet, but I don't have any idea how this message could been triggered by phridge. Phridge does no network communication...

suroorwijdan commented 9 years ago

I tested my code with PhantomJS v1.9.8 and this error disappears. I investigated a bit and this indeed looks like an error being thrown by PhantomJS 2, will post an issue on their tracker.

Closing this for now. Btw nice work with phridge. :thumbsup:

jhnns commented 9 years ago

Is PhantomJS 2 considered to be stable?

suroorwijdan commented 9 years ago

I did find the PhantomJS 2 build to be quite stable for most of the tasks. Just the above error is driving me nuts. Need to use PhantomJS 2 as the previous version (tried 1.9.8) don't support socket.io and fails silently.

pilavdzic commented 9 years ago

This is definitely a phantomjs 2 bug nothing to do with phridge, as I am getting this error while using casperjs on windows with no nodejs.

Having same problem though, can you post link to the phantomjs 2 bug so I can comment there... Having trouble finding it.