Actually it wasn't :)
Found out it was QTBUG in 5.6.2 https://bugreports.qt.io/browse/QTBUG-56616
On Wed, Sep 27, 2017 at 1:13 AM, Thiago Macieira
wrote:
> On terça-feira, 26 de setembro de 2017 13:12:43 PDT Jani Tykka wrote:
> > No special reason why I couldnt use
On terça-feira, 26 de setembro de 2017 13:12:43 PDT Jani Tykka wrote:
> No special reason why I couldnt use 1 nam instance, I will try and see if
> it makes any difference.
Unlikely. The problem is most likely in your own code.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
No special reason why I couldnt use 1 nam instance, I will try and see if
it makes any difference.
Thanks
ti 26.9.2017 klo 22.04 Thiago Macieira
kirjoitti:
> On terça-feira, 26 de setembro de 2017 11:55:35 PDT Jani Tykka wrote:
> > Hi,
> >
> > I'd ask if the
On terça-feira, 26 de setembro de 2017 11:55:35 PDT Jani Tykka wrote:
> Hi,
>
> I'd ask if the following issues would ring anyones bells, before I start
> doing more deeper investigation and create test application to reproduce
> the issue. Basically the issue in our application is reproduced
Why can't you use only one QNetworkAccessManager instance for your
application?
On Tue, Sep 26, 2017 at 1:55 PM, Jani Tykka wrote:
> Hi,
>
> I'd ask if the following issues would ring anyones bells, before I start
> doing more deeper investigation and create test
Hi,
I'd ask if the following issues would ring anyones bells, before I start
doing more deeper investigation and create test application to reproduce
the issue. Basically the issue in our application is reproduced following
way.
1. Have 1 big download (https) 100MB (It uses own QNam instance)
-