Fennec Windows Mobile – Update

I previously reported that we found a memory-related problem in the Fennec Windows Mobile pre-alpha release. Bug 477956 was the primary place to track our efforts to fix the problem. However, it became clear that porting jemalloc to WinCE was the best way to handle the situation, so bug 478044 became the bug to watch. As you can see, we are in the process of getting the fix reviewed and landed.

Using our own memory allocator gives us much more flexibility and control. We can workaround the memory management limitations found in WinCE. The next version of WinCE makes some nice changes to memory management.

A few internal test builds have been made, and with a high level of confidence, we can say that the memory problems have been solved. Once we get the fix landed, you can expect new Fennec builds for Windows Mobile.

6 Comments

  1. Nino D'Aversa said,

    March 16, 2009 @ 11:02 am

    Excellent work by Brad to get jemalloc working. I know it allows me to run Fennec (without checkerboard issues) on my HTC Diamond.

  2. Kam-Yung Soh said,

    March 16, 2009 @ 8:26 pm

    Mark,

    Are there any plans for an Fennec update for the Maemo (Nokia N810/N800) platform also?

  3. Mark Finkle said,

    March 18, 2009 @ 1:39 am

    Kam-Yung Soh – Yes. See http://starkravingfinkle.org/blog/2009/03/fennec-10-beta-1-new-and-notable/

  4. root-dir said,

    March 23, 2009 @ 5:49 am

    “Once we get the fix landed, you can expect new Fennec builds for Windows Mobile.”

    YAHOOOO!! seriously looking foward to this

  5. Memory Dragon Slane at Brad’s Blog said,

    March 23, 2009 @ 10:52 pm

    [...] known as the “checkerboard” issue. Mark Finkle blogged about the problem and the solution before. Tonight I pushed the fix to mozilla-central, here are some [...]

  6. Coffee|Code : Dan Scott said,

    April 13, 2009 @ 12:29 am

    Evergreen iPhone application? Unnecessary!…

    This Easter weekend I had the opportunity to play with someone’s iPod Touch. Of course, the only thing I tried was the Evergreen 1.4 catalogue interface. Lo and behold, it came up just fine on Safari in all of its heavily dynamic JavaScript and less-t…

RSS feed for comments on this post