After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 718986 - [norepro] Crash with the error message "ERROR:arraylist.c:623:gee_array_list_real_insert: assertion failed: (_tmp1_ <= _tmp2_)".
[norepro] Crash with the error message "ERROR:arraylist.c:623:gee_array_list_...
Status: RESOLVED DUPLICATE of bug 764265
Product: shotwell
Classification: Other
Component: import
unspecified
Other All
: High normal
: ---
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-13 01:01 UTC by clinton
Modified: 2016-04-23 10:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-25 21:58:59 UTC


---- Reported by clinton@yorba.org 2013-03-12 18:01:00 -0700 ----

Original Redmine bug id: 6528
Original URL: http://redmine.yorba.org/issues/6528
Searchable id: yorba-bug-6528
Original author: Clinton Rogers
Original description:

While waiting for a long import to finish, I observed Shotwell crashing with
this:

    
    ERROR:arraylist.c:623:gee_array_list_real_insert: assertion failed: (_tmp1_ <= _tmp2_)

  
This was during a large drag-and-drop import of ~7000 images, all JPEG and
PNG, no RAW. The app was on the import queue page at the time.

This has only been seen once; unfortunately, there isn't a clear repro path
yet.



---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:44:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 8 months ago

  * **Category** set to _import_

####

#2

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.15.0_ to _0.16.0_

####

#3

Updated by Jim Nelson 6 months ago

  * **Target version** deleted (<strike>_0.16.0_</strike>)



--- Bug imported by chaz@yorba.org 2013-11-25 21:59 UTC  ---

This bug was previously known as _bug_ 6528 at http://redmine.yorba.org/show_bug.cgi?id=6528

Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Dustin 2014-01-03 05:14:18 UTC
I'm seeing this, too.  It happens while a large number of photos and/or videos are being updated.

I had added about two hundred photos, and it was on the Updating Library phase, when it just crashed with the above error message.  I can reproduce it twice until it won't do it anymore.  It's weird.  Everything works fine once it's restarted enough times.

My settings are to not import to my local folder, but rather to leave them on my Windows drive (Pictures folder) that this computer shares.

Would it help to delete my existing settings and re-try the import and provide the output?

I'm running Debian 7.0 on a Dell Inspiron 64-bit laptop with kernel 3.12-1.

Thanks,
Dustin
Comment 2 Dustin 2014-01-03 05:14:54 UTC
Oh, and this is with version 0.15.0.

Dustin
Comment 3 Jim Nelson 2014-01-03 22:07:08 UTC
If you can reproduce this while following these instructions, that would give us a stack trace, which is super useful:

https://wiki.gnome.org/Apps/Shotwell/ReportingABug
Comment 4 Dustin 2014-01-05 17:00:44 UTC
Thanks, Jim.

I cleared out my ~/.local/share/shotwell, which forced a big update, but I can't reproduce it.  I'll put my old ~/.local/share/shotwell back in and try to force a big update.  Could it be old data?

Thanks,
Dustin
Comment 5 Jim Nelson 2014-01-06 20:49:39 UTC
It could be.  Anything that gives us a stack trace would be immensely helpful in pinpointing the problem.
Comment 6 Jens Georg 2016-04-23 10:51:14 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 764265 ***