GNOME Bugzilla – Bug 157388
ERROR_SHARING_VIOLATION crash, likely Beagle related
Last modified: 2004-12-22 21:47:04 UTC
Yeah I know Beagle isn't your baby here, but while I'm running beagled I have noticed my Blam window kept mysteriously disappearing while I wasn't looking. I ran it in a term and found a clue: ========================================================= Unhandled Exception: System.IO.IOException: Win32 IO returned ERROR_SHARING_VIOLATION. Path: /home/tvon/.gnome2/blam/collection.xml in [0x001ea] (at /build/buildd/mcs-1.0.2/class/corlib/System.IO/FileStream.cs:180) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,bool) in [0x00018] (at /build/buildd/mcs-1.0.2/class/corlib/System.IO/FileStream.cs:103) System.IO.FileStream:.ctor (string,System.IO.FileMode) in <0x00065> (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode) in [0x0001f] (at /home/tvon/cvs/gnome2/blam/src/ChannelCollection.cs:111) Imendio.Blam.ChannelCollection:SaveToFile () in [0x00001] (at /home/tvon/cvs/gnome2/blam/src/ChannelCollection.cs:227) Imendio.Blam.ChannelCollection:WriteTimeoutHandler () in <0x0005d> (wrapper delegate-invoke) System.MulticastDelegate:invoke_bool () in <0x0003c> TimeoutProxy:Handler () in <0x00040> (wrapper native-to-managed) TimeoutProxy:Handler () in (unmanaged) (wrapper managed-to-native) Gtk.Application:gtk_main () in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main () in <0x00007> Gtk.Application:Run () in <0x00007> Gnome.Program:Run () in [0x00016] (at /home/tvon/cvs/gnome2/blam/src/Application.cs:673) Imendio.Blam.Application:Main (string[]) ========================================================= This seems to happen when beagled hits collection.xml If it means anything, beagled kicks this exception at the same time: ========================================================= INFO: Could not open Blam! channel list: System.Xml.XmlException: Document element did not appear. in [0x00114] (at /build/buildd/mcs-1.0.2/class/System.XML/System.Xml/XmlTextReader.cs:503) System.Xml.XmlTextReader:Read () in [0x0002c] (at /build/buildd/mcs-1.0.2/class/System.XML/System.Xml/XmlReader.cs:216) System.Xml.XmlReader:MoveToContent () in [0x00006] (at /build/buildd/mcs-1.0.2/class/System.XML/System.Xml.Serialization/XmlSerializationReaderInterpreter.cs:83) System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadRoot () in [0x00022] (at /build/buildd/mcs-1.0.2/class/System.XML/System.Xml.Serialization/XmlSerializer.cs:286) System.Xml.Serialization.XmlSerializer:Deserialize (System.Xml.Serialization.XmlSerializationReader) in [0x0002e] (at /build/buildd/mcs-1.0.2/class/System.XML/System.Xml.Serialization/XmlSerializer.cs:275) System.Xml.Serialization.XmlSerializer:Deserialize (System.Xml.XmlReader) in [0x00023] (at /home/tvon/cvs/gnome2/beagle/beagled/BlamQueryable/BlamQueryable.cs:189) Beagle.Daemon.BlamQueryable.ChannelCollection:LoadFromFile (string) in [0x0001e] (at /home/tvon/cvs/gnome2/beagle/beagled/BlamQueryable/BlamQueryable.cs:106) Beagle.Daemon.BlamQueryable.BlamQueryable:Index () ========================================================= Probably the indexer doing something it shouldn't, but I thought I'd file it anyways. Oh, and after this crash, all my feeds have 0/0 entries. They get repopulated when I run blam again of course, but all entries are then marked as unread.
Yes, Beagle is a bad citizen and Blam counts on such to not exist ;) *** This bug has been marked as a duplicate of 157149 ***
Could you expound some on Beagle is a bad citizen? I'd like to make sure this gets fixed correctly. All Beagle is doing is trying to read collection.xml, don't understand how that makes it a bad citizen.
Beagle shouldn't open the file in exclusive mode (which is does from what I was told). What can be done from Blam to solve this is to first write to a temporary file and then copy it over the old one.