MobileSheets Forums

Full Version: Companion Crashes
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Every time I go to the "edit song" screen The Companion crashes with this info;

Problem signature:
Problem Event Name: APPCRASH
Application Name: MobileSheetsCompanion.exe
Application Version: 1.0.0.7
Application Timestamp: 4f868c25
Fault Module Name: mb_renderer.dll
Fault Module Version: 2.0.0.0
Fault Module Timestamp: 4f7c63df
Exception Code: c0000005
Exception Offset: 0003566a
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I have tried all the usual. Any thoughts?

My tablet is a Kindle Fire.

PC is Win 7 Ultimate 64 bit

I don't have this problem when I use my Transformer Prime with the Companion.

Regards,

Ken
Based on the info you provided, it seems like the PDF renderer is at fault. Does the same file work fine with your transformer prime? I'm wondering if that particular PDF is an issue for some reason. You can always disable image previewing in the menu of the Companion App, and you won't experience any crashes until I figure out the fix. If that file is a problem for both tablets, let me know. If so, I'll need a copy of the PDF so I can replicate the problem.

Mike
No, one of the first things I did was open the same file in both. The prime was OK. Every file crashed with the Kindle.

I jut realized you mark the older ver. of the companion for "Amazon users". At the time I installed the companion, I accepted the update to the latest ver. Could this be my problem and if so, will I be able to run both vers?

Ken
Unfortunately, you cannot run the new Companion App with version 1.9 of MobileSheets (the current Amazon version). 2.4 is being approved and will hopefully be available soon. I don't have a good workaround for having two tablets with different versions at the moment... This problem only occurs if I change the database schema, so hopefully it shouldn't happen very often.