Images on Backstageitem content crashes browser

4 posts, 0 answers
  1. Peter
    Peter avatar
    22 posts
    Member since:
    Nov 2007

    Posted 06 Mar 2012 Link to this post

    In my project, I allow the user to select a background that they want to use.  In Silverlight 4, I was using the RadRibbonBar with the image selection on the application menu.  I have since switched to Silverlight 5 and the RadRibbonView.  I'm trying to do the samething on the backstage item, but it causes the browser to crash most of the time.  Sometimes it works fine.
    Here is a snippet of my XAML  There are more than 2 items, but they are the same thing with a different image source:
    <telerik:RadRibbonBackstageItem Header="Background" Icon="Icons/atom16.png">                         
        <StackPanel HorizontalAlignment="Left">
            <telerik:RadRibbonButton Width="242" Height="64" Click="BackgroundChange_Click"  Size="Large" >
                    <Image Source="/Images/Background/crm_black.png" Stretch="Fill"  />                                                                     

    telerik:RadRibbonButton Width="242" Height="64" Click="BackgroundChange_Click"  Size="Large" >                                 
                    <Image Source="/Images/Background/crm_blue.png" Stretch="Fill" />                                 

    After I launch my project, I click on the BackStage button of the RibbonView, then click on the BackStageItem.  At that point, it works sometimes, but most of the time the browser crashes with the following in the Internet Explorer has Stopped Working window:

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: IEXPLORE.EXE

    Application Version: 9.0.8112.16421

    Application Timestamp: 4d76255d

    Fault Module Name: KERNELBASE.dll

    Fault Module Version: 6.1.7601.17651

    Fault Module Timestamp: 4e211319

    Exception Code: 80000003

    Exception Offset: 0000b9bc

    OS Version: 6.1.7601.

    Locale ID: 1033

    Additional Information 1: b3af

    Additional Information 2: b3af06887682a730693c32bbc1ab54eb

    Additional Information 3: fb66

    Additional Information 4: fb6647f0d7418c77f2fbeef6e2233d29

    Any ideas?


  2. Viktor Tsvetkov
    Viktor Tsvetkov avatar
    382 posts

    Posted 08 Mar 2012 Link to this post

    Hi Peter,

    Could you please send us a sample project that reproduces the problem, thus we will be able to assist you better?

    Viktor Tsvetkov
    the Telerik team
    Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>
  3. Peter
    Peter avatar
    22 posts
    Member since:
    Nov 2007

    Posted 23 Mar 2012 Link to this post

    I've created a sample project and it worked fine.  So, there must be something in my current project causing the issue.  Unfortunatly, company policy prohibits me from sending you that project.
  4. Tina Stancheva
    Tina Stancheva avatar
    3299 posts

    Posted 28 Mar 2012 Link to this post

    Hello Peter,

    Unfortunately unless we manage to reproduce the issue locally we can't further assist you in identifying the cause. However you can follow these simple steps to try and isolate the cause of the issue in your solution:

    1.   Selecting the right UserControl/Page/Window to work on: Isolate the Page/Window/UserControl where the control is and where the issue occurs. Any other code that is out of the scope of the issue should be removed.
    2.   Determine which is/are the controls that cause the problem: Often there are only 2 or 3 controls that are directly involved with a given problem. Determine which are the controls that are not related to it. We suggest you to use the "remove and try" approach when it is hard for you to determine what is causing the problem. This means that you should remove parts of the code and check if the issue reproduces without it. Keep doing this till you find the cause for the problem.
    3.   Isolating the reproduction steps: Try isolating the steps that allow you to reproduce the problem in a written list. Make sure that these steps reproduce the problem every time. There are cases where the problem appears from time to time only - in such cases, make sure that the steps that you have isolated will reproduce the problem if repeated number of times.

    I hope such an approach will help you find and fix the issue. Let us know if we can further assist you.

    Tina Stancheva
    the Telerik team
    Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>
Back to Top