282739 - Printing city search page w/media causes crash [@ nsViewManager::RenderViews]

Status: RESOLVED DUPLICATE of bug 292055

(Core :: Web Painting, defect)

Description

[Hoss]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

while printing a page from citysearch.com, mozilla keeps crashing.  this happens
regardless of printer (or print to file) and can be reproduced using a static
version of the page on the local disk that was made using "Save Page As"

if the "*_files" directory created by "Save Page As" is moved away from the
.html page (ie: so there are no images, javascript, or css files) then the page
will rpint

Reproducible: Always

Steps to Reproduce:
1. visit this URL, or the file in the soon coming attachment...

http://sanfrancisco.citysearch.com/yellowpages/results/San_Francisco_CA/restaurant/page1.html?context=restaurants&force_where=Point%20Reyes%20Station%20CA&internal_redirect=1&market_id=&query=restaurant&radius_forced=10&sorted=&start=1&store_where_for_comparison=Point%20Reyes%20Station,%20CA&map=1&radius_forced=10&ulink=default__paginationtop_510___yellowpages__1

2. Print

Actual Results:  
crash

Expected Results:  
printed the page

* no special cookies needed (i tried it with a completley empty cookie manager)
* no special theme needed (i've tried with several)
* this page include iframes, a search of other printing causes crash bugs turned
up bug#254590 in which people seem to be speculating that large iframes cause
crashes in printing.  this may be a dup of that bug, or it may be a related but
not identicle issue.

Comment 1

[Hoss]

sorry, i think i missunderstood what this product/component was for, moving to
Core/Printing based on the location of other printing related bugs i've seen.

Comment 2

[Hoss]

Attachment: tgz of "Save Page As" html/media for the page that causes crash

Comment 3

[Frank Wein [:mcsmurf]]

wfm win2k current trunk build, HP Deskjet printer.
Can you post a talkback-id? Can you maybe try reproducing this bug with a recent
build (like Mozilla 1.8a6)?

Comment 4

[Hoss]

could *not* reproduce in M1.4 on winNT

could *not* reproduce in FF1.0 on winNT

I'm not really in a possition to install any other builds at the moment, i will
try to get to that a little later.

I didn't know how to find the talkback ID before, but i found it...

http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=3782545#id

Comment 5

[timeless]

   Incident ID: 3782545

      Stack Signature    nsViewManager::RenderViews() ac26ddcb
        Product ID       Mozilla17
         Build ID        2004061606
       Trigger Time      2005-02-18 10:35:28.0
         Platform        LinuxIntel
     Operating System    Linux 2.6.6.hoss1
          Module         libgklayout.so + (003c461c)
        URL visited
       User Comments     printing this page...
     Since Last Crash    0 sec
       Total Uptime      911 sec
      Trigger Reason     SIGSEGV: Segmentation Fault: (signal 11)
   Source File, Line No.
/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/view/src/nsViewManager.cpp,
line 704
        Stack Trace

   nsViewManager::RenderViews() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/view/src/nsViewManager.cpp,
line 704]
   nsViewManager::Display() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/view/src/nsViewManager.cpp,
line 86]
   nsSimplePageSequenceFrame::PrintNextPage() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/layout/html/base/src/nsSimplePageSequence.cpp,
line 901]
   nsPrintEngine::PrintPage() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/content/base/src/nsPrintEngine.cpp,
line 3578]
   nsPagePrintTimer::Notify() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/content/base/src/nsPagePrintTimer.cpp,
line 92]
   nsTimerImpl::Fire() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 386]
   handleTimerEvent() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 447]
   PL_HandleEvent() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpcom/threads/plevent.c,
line 673]
   PL_ProcessPendingEvents() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpcom/threads/plevent.c,
line 608]
   nsEventQueueImpl::ProcessPendingEvents() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpcom/threads/nsEventQueue.cpp,
line 395]
   event_processor_callback() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 188]
   our_gdk_io_invoke() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 75]
   libglib-1.2.so.0 + 0xea56 (0x40288a56)
   libglib-1.2.so.0 + 0x1003d (0x4028a03d)
   libglib-1.2.so.0 + 0x104f4 (0x4028a4f4)
   libglib-1.2.so.0 + 0x10724 (0x4028a724)
   libgtk-1.2.so.0 + 0xa025f (0x4019625f)
   nsAppShell::Run() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 319]
   nsAppShellService::Run() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 524]
   main1() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 710]
   main() 
[/builds/tinderbox/Mozilla1.7/Linux_2.4.18-3_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1783]
   libc.so.6 + 0x15904 (0x403b0904)

Comment 6

[Andrew Schultz]

worksforme with linux trunk 2005021805.  please try a trunk build

Comment 7

[timeless]

*** Bug 283167 has been marked as a duplicate of this bug. ***

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/