search

sejerpz / vtg

Automatically exported from code.google.com/p/vtg
0 stars 0 forks source link

opening glib-2.0.vapi makes vtg very unstable #173

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 

I usually look into the vapi files while programming. There, you can sometimes 
see things otherwise not so easy to find.
Unfortunately, having glib-2.0.vapi open in a gedit vtg session will make gedit 
very instable and mostly crash after a short time.   

I guess vtg tries indexing this vapi alongside with the project and has 
difficulties with that.

Original issue reported on code.google.com by shuerhaaken on 2 Jun 2011 at 10:04

GoogleCodeExporter commented 9 years ago 
I can reproduce this bug following these steps:

1) open glib vapi
2) open another source file

if I invert steps 1 and 2 vtg works well. After some (big) changes in afrodite 
the bug seems fixed, but I'm not sure I fixed the root cause.

Can you test it with current master (commit 
3240effc308bc69d73768a7f1ca91090a30fbc5e) and eventually reopen this issue?

Original comment by seje...@gmail.com on 12 Jul 2011 at 9:36

GoogleCodeExporter commented 9 years ago

Original comment by seje...@gmail.com on 27 Jul 2011 at 11:34

GoogleCodeExporter commented 9 years ago

Original comment by seje...@gmail.com on 27 Jul 2011 at 11:36