GNOME Bugzilla – Bug 382691
Crash in IA__g_assert_warning, miUnionNonO at gdkregion-generic.c line 1086
Last modified: 2010-06-16 21:41:07 UTC
Version: 2.16.1 What were you doing when the application crashed? I was seeing some photograhs Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 105947136 vsize: 0 resident: 105947136 share: 0 rss: 42872832 rss_rlim: 0 CPU usage: start_time: 1165343602 rtime: 0 utime: 5403 stime: 0 cutime:4825 cstime: 0 timeout: 578 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225996096 (LWP 15123)] [New Thread -1292489824 (LWP 15131)] [New Thread -1228051552 (LWP 15127)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 91821
Thread 1 (Thread -1225996096 (LWP 15123))
We're hitting this all over the place in VMware Workstation 6. It definitely seems to be specific to GTK+ 2.10, and we've hit it with 2.10.3 and 2.10.6. I'm trying to figure out a test case for this, but it's proving difficult to figure out what exactly is causing this code path to be executed. Unfortunately, this is proving to be a showstopper for us :(
If you want to me to do anything, just drop a line.
We still don't know what's causing it. If it turns out to be an application bug that's triggering it, we'll certainly document the cause here so eog can address it.
(In reply to comment #1) > We're hitting this all over the place in VMware Workstation 6. It definitely > seems to be specific to GTK+ 2.10, and we've hit it with 2.10.3 and 2.10.6. I'm > trying to figure out a test case for this, but it's proving difficult to figure > out what exactly is causing this code path to be executed. Unfortunately, this > is proving to be a showstopper for us :( > Christian, What you are saying is that this bug is not EOG specific? if that's the case, could you please move it to the correct product? Thanks.
Any additional info on this bug?
It turned out to be some memory corruption (in particular, something was writing 4 bytes of 0 to a bad location) on our end. My guess is it's something similar here, since the code that the assert happens in is in a really common path.
*** Bug 367788 has been marked as a duplicate of this bug. ***
last duplicate was a collection of 20 duplicates, all crashes of eog 2.16 asserting with the same expression on the same line, but this trace is superior. smells like a bug triggered only by eog to me. Confirming this report.
Christian, The report you closed as duplicated of this one was assigned to GTK+. Os this then a bug in GTK+ or in EOG?
Claudio: It appears that this is not a bug in GTK+. We believed it to be at first due to seeing the same problem in an early beta of VMware Workstation 6, but we discovered it was memory corruption on our end. We have since ran into this at times when we've had memory corruption due to just simply accessing an invalid block of memory. It appears that this code path just happens to fail with this assert pretty often under such conditions, as the code path is very regularly executed. So, this appears to be memory corruption somewhere in EOG, but I don't know if it's been fixed since.
*** Bug 420701 has been marked as a duplicate of this bug. ***
*** Bug 423178 has been marked as a duplicate of this bug. ***
*** Bug 434179 has been marked as a duplicate of this bug. ***
*** Bug 435303 has been marked as a duplicate of this bug. ***
*** Bug 444916 has been marked as a duplicate of this bug. ***
*** Bug 447514 has been marked as a duplicate of this bug. ***
With the rewrite of the EOG core in the eog-ng branch, now trunk, this bug is no longer reproducible. Closing as FIXED. Please feel free to reopen if you can reproduce it with 2.19/2.20. This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
*** Bug 452903 has been marked as a duplicate of this bug. ***
*** Bug 461749 has been marked as a duplicate of this bug. ***
*** Bug 467148 has been marked as a duplicate of this bug. ***
I'm reopening this bug because a dupe was filed that was triggered by Epiphany, not EOG.
*** Bug 482443 has been marked as a duplicate of this bug. ***
Moving to gdk component. Can someone who's able to reproduce this paste the last couple of lines of the .xsession log?
(In reply to comment #23) > Moving to gdk component. > > Can someone who's able to reproduce this paste the last couple of lines of the > .xsession log? -> NEEDINFO
sorry, I can't reproduce the error anymore, I updated my system several times since then. sorry.
OK, seems that this bug is no longer reproducible. Closing as FIXED. Please feel free to reopen if you can reproduce it with a new GTK+ version.