ICEmobile
  1. ICEmobile
  2. MOBI-172

Crashes in Simulator environment

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0 Beta
    • Fix Version/s: 1.1 Final
    • Component/s: None
    • Labels:
      None
    • Environment:
      ICEmobileContainer running in simulator environment

      Description

      The Blackberry simulator has been problematic over the course of development. It has very different error handling than the devices, operates at a far lower speed, and involves the developer more closely in the details of the network transport configuration.

      This Jira is to keep track of changes made to help the container run better in the simulator.

        Activity

        Hide
        Greg Dick added a comment -

        There was a problem in the simulator in ajax navigation between pages of the mobileshowcase application that would cause a complete crash of the container. I tracked it down to somewhere in the handleResponse method in the blackberry-interface.js file where we try to apply the updates to the existing DOM.

        I added some logging to the method. This method uses the container logging facility through one of our extensions to javascript and I expect it's rather expensive and slow, and lo! the crashing stopped. Currently I've added code to execute this logging only in the simulator. I tried to add an onload callback but in a short time before release couldn't get it to work. I'd like to get that to work and see if it offers any useful information, but this approach will work for now.

        Show
        Greg Dick added a comment - There was a problem in the simulator in ajax navigation between pages of the mobileshowcase application that would cause a complete crash of the container. I tracked it down to somewhere in the handleResponse method in the blackberry-interface.js file where we try to apply the updates to the existing DOM. I added some logging to the method. This method uses the container logging facility through one of our extensions to javascript and I expect it's rather expensive and slow, and lo! the crashing stopped. Currently I've added code to execute this logging only in the simulator. I tried to add an onload callback but in a short time before release couldn't get it to work. I'd like to get that to work and see if it offers any useful information, but this approach will work for now.
        Hide
        Greg Dick added a comment -

        Simulator seems to be running fine at this point.

        Show
        Greg Dick added a comment - Simulator seems to be running fine at this point.

          People

          • Assignee:
            Greg Dick
            Reporter:
            Greg Dick
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: