Need help with testing asynchronous saving branch! :)

[Wolthera]

Haven't found the cause of the previous, but I did find that if you take an
autosave, and then work on it, it is possible to have an autosave of an
autosave. I understand why this happens, but it is pretty... surreal
nonetheless.

On Thu, Jul 13, 2017 at 9:09 PM, Wolthera <griffinvalley at gmail.com> wrote:

> Yeah, I guess, but after poking a bit at it, the progress bar just seems
> confused, as autosave and friends always tell me what they're doing, but in
> this case the progress bar just.. sits there...
>
> I had another crash with a 4096x4096 file at 16bit int(I thought I'd try
> make a heightmap... Crash happened as I tried generating noise with the
> noise filter), couldn't get a backtrace, but I did get this...
>
> > Qt Concurrent has caught an exception thrown from a worker thread.
> > This is not supported, exceptions thrown in worker threads must be
> > caught before control returns to Qt Concurrent.
> > Qt Concurrent has caught an exception thrown from a worker thread.
> > This is not supported, exceptions thrown in worker threads must be
> > caught before control returns to Qt Concurrent.
> > Qt Concurrent has caught an exception thrown from a worker thread.
> > This is not supported, exceptions thrown in worker threads must be
> > caught before control returns to Qt Concurrent.
> > Qt Concurrent has caught an exception thrown from a worker thread.
> > This is not supported, exceptions thrown in worker threads must be
> > caught before control returns to Qt Concurrent.
> > terminate called recursively
> > terminate called recursively
> > terminate called after throwing an instance of 'terminate called
> recursively
> > std::bad_alloc'
> >   what():  std::bad_alloc
>
>
> On Thu, Jul 13, 2017 at 8:12 PM, Boudewijn Rempt <boud at valdyas.org> wrote:
>
>> I guess that's autosave not reporting 100% done?
>>
>> On Thu, 13 Jul 2017, Wolthera wrote:
>>
>> > Another bug:
>> > Sometimes, when the image is left alone for a while(in my case a single
>> > vector object was there), it's showing a progressbar stuck on 50%
>> > permanently. I do not know why. Of course the progressbar shouldn't do
>> such
>> > things, but I would also like a Tooltip to tell me what Krita is
>> thinking
>> > it's processing at that moment so I can give better feedback.
>> >
>> > On Tue, Jul 11, 2017 at 10:50 AM, Boudewijn Rempt <boud at valdyas.org>
>> wrote:
>> >
>> > > I just merged master into the async branch and applied the pdf
>> > > filter patch. In a short test, everything seems to work... But
>> > > the progress bar never gets to 100% when I save to .kra.
>> > > --
>> > > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>> > >
>> >
>> >
>> >
>> >
>>
>> --
>> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>>
>
>
>
> --
> Wolthera
>



-- 
Wolthera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20170713/77bb5393/attachment-0001.html>