0.8.0.0 crashes Fatal IO error 11

[GoogleCodeExporter]

What steps will reproduce the problem?
 1. Open gmc and zoom in/out quickly using either the mouse or keyboard

What is the expected output? What do you see instead?

When running from a terminal gmc eventually crashes with the following error:

maps.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

and sometimes it freezes and crashes with this error message:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been 
called
[xcb] Aborting, sorry about that.
python: ../../src/xcb_io.c:273: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)
cjreeve@onyx:~$ tmp/GMapCatcher/maps.py 
maps.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

What version of the product are you using? On what operating system?

mapcatcher_0.8.0.0-1_all.deb and svn copy downloaded yesterday.

I am currently running xubuntu 12.04 with python 2.7.3 and python-gtk2 
(2.24.0-3)

Is it that I should be running python 2.6? My copy of gmc from a couple weeks 
back works fine with my setup. 

Please provide any additional information below.

The svn copy is even more unstable.

The .deb copy still reports "No Tracks Found!" when a gps track has been drawn. 
Have not checked the current repository copy.

Original issue reported on code.google.com by cjre...@gmail.com on 21 Oct 2012 at 3:15

[GoogleCodeExporter]

Not happening on windows...

Original comment by heldersepu on 22 Oct 2012 at 12:57

[GoogleCodeExporter]

I haven't seen this problem in a long, long time. The latest SVN-version can be 
unstable though. Do you have tracks loaded when opening gmapcatcher when the 
crash occurs?

The "No Tracks Found!" information is correct for the .deb version, as I 
implemented using GPS track as a normal track after it was released. You can't 
hide GPS-track if you have selected it in the options in 0.8.0.0 (or ...1). 
There's a button to export GPS track seperately in the track control window.

The current trunk-version however handles GPS "just as another track".

Original comment by kipenros...@gmail.com on 23 Oct 2012 at 6:13

[GoogleCodeExporter]

I'm looking forward to testing the GPS-track updates but gmapcatcher is 
currently too unstable for me.

I realised that my version I am running is older than I thought. By trial and 
error (using svn update -r #) I think I have narrowed it down to the change 
r1495.
http://code.google.com/p/gmapcatcher/source/detail?r=1495

I haven't had time to look into exactly what part of those changes makes the 
difference.

Original comment by cjre...@gmail.com on 23 Oct 2012 at 9:50

[GoogleCodeExporter]

I'm fairly sure that the markers aren't thread-safe. I'll look into it this 
weekend.

In the mean time it should work, if you don't use markers. At least has worked 
for me and I've driven about 800 km with GMapCatcher tracking GPS...

Original comment by kipenros...@gmail.com on 26 Oct 2012 at 10:10

[GoogleCodeExporter]

Yes, I can confirm GMapCatcher works fine for me without markers. I tested the 
updates you made to the GPS tracks and it worked well.

I also gathered it was something to do with threads, based on the solution to 
this post:
http://stackoverflow.com/questions/3212010/why-does-my-pygtk-application-crash-w
hen-copying-text-on-a-clipboard

I haven't had time to get my head around it. Never done any GUI programming 
before and more familiar with using threads to mend my clothing.

Original comment by cjre...@gmail.com on 26 Oct 2012 at 10:37

[GoogleCodeExporter]

No worries, it doesn't require big changes. I'll remake the whole marker-thread 
thingy this weekend, once I get the time and motivation.

Original comment by kipenros...@gmail.com on 26 Oct 2012 at 5:44

[GoogleCodeExporter]

previous to r1495 I was using threads only IF it had more than 1000 markers 
maybe we should bring that back or put it as an option in the config file.

Original comment by heldersepu on 26 Oct 2012 at 6:10

[GoogleCodeExporter]

Should be fixed in r1558

Original comment by kipenros...@gmail.com on 26 Oct 2012 at 6:23

[GoogleCodeExporter]

Thanks. No more crashes! 

Original comment by cjre...@gmail.com on 30 Oct 2012 at 8:47

[GoogleCodeExporter]

Original comment by heldersepu on 30 Oct 2012 at 8:48

• Changed state: Done