>07.08.2019, 02:21, "Sérgio Martins via Development"
>:
>> I looked at it again and the test-case was flawed, it was using unneeded
>> QStrings and QString::toUtf8().
>>
>> By reading directly from the file heaptrack now reports only 300 MB
>> peak.
I think I would have noticed anything more sub
07.08.2019, 02:21, "Sérgio Martins via Development"
:
> On 2019-08-06 22:49, Sérgio Martins via Development wrote:
>> On 2019-08-06 13:48, René J. V. Bertin wrote:
>>> Joerg Bornemann wrote:
>>>
Unfortunately, this isn't possible at the moment.
This issue is tracked in QTBUG-47629.
On 2019-08-06 22:49, Sérgio Martins via Development wrote:
On 2019-08-06 13:48, René J. V. Bertin wrote:
Joerg Bornemann wrote:
Unfortunately, this isn't possible at the moment.
This issue is tracked in QTBUG-47629.
Thanks, I'll try the patch!
Can you also check how much memory is occupie
On Tuesday, 6 August 2019 10:48:36 PDT André Pönitz wrote:
> For me, 'ACME' probably will always trigger 'ACME Corporation' as in
> https://en.wikipedia.org/wiki/Acme_Corporation, but ..
I think of my friend acme, maintainer of the Linux perf tool.
http://vger.kernel.org/~acme/perf/
https://git.k
On 2019-08-06 13:48, René J. V. Bertin wrote:
Joerg Bornemann wrote:
Unfortunately, this isn't possible at the moment.
This issue is tracked in QTBUG-47629.
Thanks, I'll try the patch!
Can you also check how much memory is occupied by reading that 100 MB
file ?
My memory is hazy but I th
On 8/6/19, 1:49 PM, "André Pönitz" wrote:
.. by now I think we can simply side step this issue of finding a name
for a branch, as I think we shouldn't have a branch to start with.
Fair enough, we will target master.
Regards,
Brett
___
Deve
On Mon, Aug 05, 2019 at 11:48:54PM +, Stottlemyer, Brett (B.S.)
wrote:
> Before I address André's specific questions, let me add a little more
> context.
>
> We have a few plugins for QtC that were developed with KDAB starting
> about 5 years ago with the development of Qt Remote Objects. We'
On Tuesday, 6 August 2019 04:47:01 PDT René J. V. Bertin wrote:
> Hello,
>
> I have a 114Mb big JSON file that I'd like to be able to parse but that is
> rejected because of its size.
>
> Is it possible to rebuild Qt with a larger maximum document size for the
> JSON parser? I found the Value::Ma
Joerg Bornemann wrote:
> Unfortunately, this isn't possible at the moment.
> This issue is tracked in QTBUG-47629.
Thanks, I'll try the patch!
R.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 8/6/19 1:47 PM, René J. V. Bertin wrote:
> I have a 114Mb big JSON file that I'd like to be able to parse but that is
> rejected because of its size.
>
> Is it possible to rebuild Qt with a larger maximum document size for the JSON
> parser?
Unfortunately, this isn't possible at the moment.
Hello,
I have a 114Mb big JSON file that I'd like to be able to parse but that is
rejected because of its size.
Is it possible to rebuild Qt with a larger maximum document size for the JSON
parser? I found the Value::MaxSize token which is somehow related to the too-
large error, understand you
Hi Qt Developers,
Coin production has been updated 1.1.1 -> 1.1.2
If you want to see the what has been changed in comparison to the
previous **baseline version, you can take a look at our newly
auto-generated change logs:
https://testresults.qt.io/coin/doc/changelog.html
** If you see lett
Hi,
Final downmerge from '5.13' -> '5.13.1' is now done. So all changes for Qt
5.13.1 release must be done in '5.13.1' and '5.13' is for Qt 5.13.2
br,
Jani
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/de
13 matches
Mail list logo
