Closed
Bug 177960
Opened 23 years ago
Closed 22 years ago
[mach-o] crash when trying to print [nsBaseWidget::GetRenderingContext()]
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bugzilla, Assigned: ccarlen)
References
()
Details
(Keywords: crash)
Attachments
(1 file)
|
12.97 KB,
text/plain
|
Details |
found using 2002.11.01.07 mach-o build on 10.2.1.
1. go to
http://www.mozilla.org/quality/browser/front-end/testcases/printing/widgets.html
2. click on the print button in the navigation toolbar.
3. in resulting native print dlg, click Print button to print.
results: mach-o crashes.
will attach crash report soon, and will also check the mozilla cfm build for
comparison.
| Reporter | ||
Comment 1•23 years ago
|
||
| Reporter | ||
Comment 2•23 years ago
|
||
unable to repro crash using 2002.11.01.08-trunk CFM mozilla build on 10.2.1.
Summary: crash when trying to print [nsBaseWidget::GetRenderingContext()] → [mach-o] crash when trying to print [nsBaseWidget::GetRenderingContext()]
Comment 3•23 years ago
|
||
I printed that page succesfully with a local trunk build from last night.
Running 10.1.5.
| Assignee | ||
Comment 4•23 years ago
|
||
With today's nightly, I can repro this crash every time.
With a debug tree which I pulled and built today, I can't repro this.
So,
* What level of opt are our nightlies built with?
* With a tree with a certain opt level, can I turn down the opt on a per-module
basis. (What's the makefile trick to do so?)
Comment 5•23 years ago
|
||
I thought that our nightly builds used -O2.
You can specify certain modules to build with debug symbols at configure time by
using --enable-debugger-info-modules=gfx,widget (or just editing the
MOZ_DBGRINFO_MODULES variable in the generated autoconf.mk). Otherwise, you'd
have to use --enable-optimize w/o any additional args (eg. w/o =-O2) and add
|MODULE_OPTIMIZE_FLAGS=-O0 -g| to the local Makefile.
FWIW, the latest trunk nightly build (2002120408) still works fine on 10.1.5.
| Assignee | ||
Comment 6•23 years ago
|
||
I just got this to happen on a debug build. It happens because, when the listbox
control is drawn, it scrolls the selection into view. For some reason, on my
PowerBook, it always performs a scroll and thus crashes. On my G4, selecting
"anchovies" in the second list before printing will cause scrolling to happen
and crash. The G4 is a debug, non-opt build.
This printf below shows that mContext == null, so we crash.
nsIRenderingContext* nsBaseWidget::GetRenderingContext()
{
nsresult rv;
nsCOMPtr<nsIRenderingContext> renderingCtx;
printf("nsBaseWidget::GetRenderingContext: mContext = 0x%.8X\n", mContext);
Trying to find out how mContext could be null...
| Assignee | ||
Comment 7•23 years ago
|
||
CC'ing Don.
Seawood, can you try selecting anchovies (might take some other twiddling of the
listbox in your case) and see if you can get it to crash on 10.1?
Comment 8•23 years ago
|
||
Yep, selecting anchovy in the bottom listbox causes it to crash here too.
| Assignee | ||
Comment 9•23 years ago
|
||
And, with 2002120508 CFM build, selecting anchovy on CFM build also crashes with
same stack. Since not Mach-0 specific, removing blockage of bug 176301.
Gotta love anchovies.
No longer blocks: 176301
| Reporter | ||
Comment 10•22 years ago
|
||
well, this no longer seems to happen (tested with a mach-o trunk build from
y'day). marking w4m.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•