Crash, beta 8: Failed to create BitmapFrame

I received this crash when starting Logos:

Time: 2011-12-11 07:46:11 +00:00 (2011-12-11T07:46:11Z)
Failed to create BitmapFrame.
System.IO.IOException: Cannot locate resource 'images/commandicon.png'.
   at MS.Internal.AppModel.ResourcePart.GetStreamCore(FileMode mode, FileAccess access)
   at System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)
   at System.IO.Packaging.PackWebResponse.CachedResponse.GetResponseStream()
   at System.IO.Packaging.PackWebResponse.GetResponseStream()
   at System.IO.Packaging.PackWebResponse.get_ContentType()
   at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
   at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
   at System.Windows.Media.Imaging.BitmapFrame.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy)
   at System.Windows.Media.Imaging.BitmapFrame.Create(Uri bitmapUri, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy)
   at System.Windows.Media.Imaging.BitmapFrame.Create(Uri bitmapUri, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption)
   at Libronix.Utility.Windows.BitmapSourceUtility.<>c__DisplayClassc.<CreateThreadAffinedFromLocalUri>b__b()
   at Libronix.Utility.Windows.BitmapSourceUtility.NullIfFailedCreation[T](Func`1 fn)

Looking at the logs, it started happening on 15 November, but I haven't noticed a crash before. Error log attached.

1122.Logos4Error.log

Nothing unusual shows up in the normal Logos/indexer logs. The crash didn't appear to have any adverse effect (Logos just carried on loading).

Find more posts tagged with

Comments

Dave Hooton

Looking at the logs, it started happening on 15 November, but I haven't noticed a crash before.

The error happens enough times to be a concern but none of them caused a crash (the only crash recorded was on 3 December ==> *** Application Crash ***). "Failed to create BitmapFrame" should be in logos4.log though.

Mark Barnes

https://community.logos.com/discussion/comment/312790#Comment_312790

none of them caused a crash

Even though no crash is listed in the log, it did crash. Here's the text from the Windows Event Viewer that has the same timestamp as the error above:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Logos4Indexer.exe
P2: 4.50.0.1543
P3: 4ed6b01a
P4: KERNELBASE.dll
P5: 6.1.7601.17651
P6: 4e211319
P7: e0434f4d
P8: 0000B9BC
P9:
P10:

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 1e23240b-23cc-11e1-b52a-001966fdaee8
Report Status: 0

Here's the Windows Error Report from that crash

0363.Report.wer.txt

Mark Barnes

https://community.logos.com/discussion/comment/312798#Comment_312798

Upon further investigation I find I have had several crashes like the one above. They do not necessarily correspond with the errors in the Logos error log.

TCBlack

https://community.logos.com/discussion/comment/312799#Comment_312799

I also have found this error recently. hmm.

Dave Hooton

https://community.logos.com/discussion/comment/312799#Comment_312799

They do not necessarily correspond with the errors in the Logos error log.

Very interesting! I seem to have a greater correlation.

TCBlack

https://community.logos.com/discussion/comment/312897#Comment_312897

This one keeps cropping up, all I was doing this time was clicking on the layouts menu to open my last layout.

http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/27516.Logos-Log-Files.zip

Dave Hooton

https://community.logos.com/discussion/comment/313298#Comment_313298

This one keeps cropping up, all I was doing this time was clicking on the layouts menu to open my last layout.

We learn a little more. It appears in logos4.log as:-

Error BitmapSourceUtility Cannot locate resource 'images/commandicon.png'.

But there is no application crash.

Otherwise BitmapSourceUtility appears when closing Logos 4:-

Info BitmapSourceUtility CreateApplicationScreenshot called for size (300,225)

i.e. when creating a snapshot

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/313363#Comment_313363

This issue has been reported to our Development Department for investigation.

Kevin Byford (Faithlife)

Mark,

Can you send us all of your log files zipped up together?

Mark Barnes

https://community.logos.com/discussion/comment/314234#Comment_314234

(

Can you send us all of your log files zipped up together?

I don't get a crash log, and you already have the error log. I'm able to send you old copies of Logos4.log if they'll be useful, but I don't want to create work for myself (it takes a few minutes to extract each one from my backup), or swamp you unnecessarily. Here are three Logos4.log files that cover the beginning of the period where there are bitmap errors. You can cross check them with the error log in the first post if that's helpful. If you want more of these log files, just ask.

7838.Logos4.log (2011-11-15 02:50:00.8359)
4572.Logos4.log (2011-11-16 17:49:23.9609)
4544.Logos4.log (2011-11-17 21:42:31.3828)

Also attached is a zip file of all my surviving Windows Error Report dumps: 8156.New WinZip File.zip

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/314262#Comment_314262

An error message referencing "images/commandicon.png" is a spurious error that can be safely ignored. (We should probably suppress the error logging for this specific message to avoid confusion, or figure out if we can prevent the error in the first place.)

If you remember back to the early days of Logos 4 (maybe even the private beta?), there was a generic spanner icon that was used for various commands and shortcut icons that didn't have their own custom icons yet. That icon ceased to exist once the final art was in place, but some systems still remember the existence of this icon (I'm not sure exactly how) and try to load it. This fails, so the app falls back to whatever its current default behaviour is (I don't have the source code available right now to check). However, it still logs an error because it's going through a standard code path that logs bitmap load failures because that can indicate issues with WPF or WIC image codecs that would be useful to know about when diagnosing other problems.

It's extremely unlikely that the presence of this error in a log file would be related to a crash.

NetworkGeek

https://community.logos.com/discussion/comment/314674#Comment_314674

If you remember back to the early days of Logos 4 (maybe even the private beta?),

To help diagnosis Bradley, I was not on the original private beta, and I see this error routinely; so it probably isn't something left over from that time.

TCBlack

https://community.logos.com/discussion/comment/314674#Comment_314674

I've also had a clean OS install twice since leaving private beta, and I'm almost certain after Logos 4.2 came out as well.