Bug 361744 - Internal Error (ASSERT line 327) upon switching between multiple views of same file
Summary: Internal Error (ASSERT line 327) upon switching between multiple views of sam...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 3.0 Alpha
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-14 01:44 UTC by Sam Keeper
Modified: 2016-04-16 13:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Image of the error message (462.82 KB, image/png)
2016-04-14 01:45 UTC, Sam Keeper 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Keeper 2016-04-14 01:44:34 UTC 
When switching between multiple views of the same file, I received an error message reading:

Krita has encountered an internal error:

Assert (krita):"dummy" in file C:\kritadev\ ... \timeline_frames_model.cpp, line 327

Please report a bug to developers!

Press ignore to continue &c.


The message appeared several times as I switched from the second view to the first (it ALWAYS appeared moving from second to first) and after the fourth or fifth time Krita crashed.

I could not recreate the bug unfortunately. It occurred several hours into working, and after reloading the program I was unable to prompt the error message again.

See attached image file

Reproducible: Couldn't Reproduce
Comment 1 Sam Keeper 2016-04-14 01:45:45 UTC 
Created attachment 98388 [details]
Image of the error message
Comment 2 Halla Rempt 2016-04-14 18:44:34 UTC 
Hi Sam,

Thanks for the report. I've asked Dmitry to take a look, he's the one who made the scary assert message box :-) Just the fact that it can happen makes it a confirmed bug!
Comment 3 Halla Rempt 2016-04-16 13:31:29 UTC 
Fixed in  


commit cb342ec320ad79c07c9d8963895ff963f841eb3f
Author: Dmitry Kazakov <dimula73@gmail.com>
Date:   Fri Apr 15 19:03:54 2016 +0300

    Fix all invalid accesses in stl-like iterators
    
    We must not keep 'end' iterator throughout the loop if the object
    is changed in the meantime. According to Qt's docs all the iterators
    become 'undefined' after every non-const function call over the
    iterated object.
    
    CC:kimageshop@kde.org