Closed
Bug 191028
Opened 22 years ago
Closed 22 years ago
Printing crashed
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: palm, Unassigned)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
After opening/creating/editing a page in Composer and attempting to print the
memory and subsequently CPU utilisation the goes through the roof until the
notification agent kicks in and Mozilla bombs out.
Printing from within the browser and elsewhere works fine
Reproducible: Always
Steps to Reproduce:
1. Invoke window->composer
2. Make some changes
3. Select Print (File->Print) and confirm
Actual Results:
No print occured, I am checking to see if the progress bar appears.
Memory Utilisation went to 50% CPU topped out at 98% and Mozilla crashed with
the reporting agent presenting itself.
This has happened twice out of two attempts to print, I'm assuming it is
reproducible.
Expected Results:
It should have printed and not crashed
Prerequisites may be that I have also installed the calendar product which has a
known bug with printing (culminating in printing being disabled for calendar).
Using Modern Theme
Plugins:
nppdf.so
Shockwave Flash
Reporter | ||
Comment 1•22 years ago
|
||
Atempted again after submitting this bug and it worked.
Repeatability is not "every time".
Comment 2•22 years ago
|
||
-->Composer
reporter: can you reproduce on a more recent build (1.4beta or newer)?
Assignee: jfrancis → composer
Component: Editor: Core → Editor: Composer
QA Contact: sujay → petersen
Comment 3•22 years ago
|
||
resolving as worksforme since this hasn't been confirmed in a recent build
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•