[A complimentary Cc of this posting was sent to
Felix Miata 
<[EMAIL PROTECTED]>], who wrote in article <[EMAIL PROTECTED]>:
> 1-Crash was immediately precipitated by attempting to open
> http://mrmazda.no-ip.com/SS/desktop-a-865-1792x1344x144.png in a new
> tab.
> 2-RAM freed as result of crash: 285M
> 3-Uptime at crash: 45.5 hours
> 4-Heavy usage while up, including mail, news, 14 CZ tabs, and lots of
> browser tabs, both regular and https
> 5-Bad image painting behavior noted shortly before crash:
> http://sperling.com/dave2.png had been loaded and properly some time
> before, but when I returned to it, the viewport was entirely blank, and
> reload didn't help. What worked was as described in my first post in
> this thread, sufficiently reducing the viewport size.

This behaviour looks very similar to the testcase I provided about a
month ago to Peter (can't provide the link publicly).  He claims that
the reason for my testcase crash is fixed in his latest release of FF
for OS/2 (all except "blank painting when remaining memory is low").

Can it be fixed *now*?

Thanks,
Ilya            [Fup to mozilla.dev.ports.os2]
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

Reply via email to