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 732475 - ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
Status: RESOLVED FIXED
Product: frogr
Classification: Other
Component: general
master
Other Linux
: Normal critical
: ---
Assigned To: frogr maintainers
frogr maintainers
: 734200 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-06-30 12:51 UTC by Serrano Pereira
Modified: 2014-11-08 01:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Serrano Pereira 2014-06-30 12:51:28 UTC
I got the latest Frogr from the Git repository. When I run Frogr, it crashes immediately with the following error:

frogr: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
Aborted (core dumped)

If I clean up the application data (`rm -rf .config/frogr/') it will actually start without crashing, and it says in the status bar that it is connected to Flickr with account so and so.

The next time I try to run Frogr, it will crash with the same assertion error.

Sometimes I get the following error:

(process:25610): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Comment 1 Mario Sánchez Prada 2014-07-19 10:38:51 UTC
Thanks for the report, and sorry for the late reply. I have tried myself reproducing this locally, from the master branch, and I was unable to do it.

Anyway, that crash is happening in libgcrypt, so it's not entirely clear to me whether this is a bug in frogr or somewhere else, but it's difficult to say without more information.

Perhaps you could paste a backtrace or attach a coredump?
Comment 2 Serrano Pereira 2014-07-21 08:49:17 UTC
Thanks for the reply Mario. Find the core dump here: http://we.tl/ySmgA2OlX4

I'm a little confused though, as the behavior has changed. It used to crash all the time (unless I removed the data folder as explained), but as I was just trying to reproduce it for the core dump, nothing happened. In fact, I had to close and run Frogr like 5 times before it crashed again. I've executed Frogr more than 5 times after the last crash, and it's not crashing anymore.
Comment 3 Mario Sánchez Prada 2014-09-06 08:55:21 UTC
*** Bug 734200 has been marked as a duplicate of this bug. ***
Comment 4 Mario Sánchez Prada 2014-09-13 23:32:10 UTC
I'm not 100% sure but I could reproduce this crash the last two times I've tried to upload a big batch of pictures and, after landing the commit in [1], I didn't reproduce it again, so I guess that actually did the trick and fix it.

Resolving now then, but please reopen if you still experience this issue in newer versions of frogr. Thanks!

[1] https://git.gnome.org/browse/frogr/commit/?id=d7f4e944aa691244e57a8fcc8f4f0e5f91da8686