Closed
Bug 166469
Opened 23 years ago
Closed 21 years ago
[BeOS] crash in libart
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: beos, Assigned: alex)
References
()
Details
(Keywords: crash)
Almost every SVG page I've visited, crashes in the same place: line 757 of
art_render.c in the libart_lgpl library under BeOS. The only SVG file that
hasn't crashed it is the tests/example.xml, which just gives javascript
permissions denied exceptions, and does not display any graphics.
Log for thread 2926 (mozilla-bin) of team 585 (mozilla-bin)
Reason why stopped: "Segment Violation"
Registers:
eax : 0x70450311
ebx : 0xecd06c10
ecx : 0x01000000
edx : 0x00000000
ebp : 0xfd000a10
edi : 0xeccf3a24
esi : 0xeccf0fd0
eip : 0xeccf121e
uesp : 0xfd0009a0
eflags : 0x00010246
error_code : 0x00000004
cs : 0x0000001b
ds : 0x00000023
es : 0x00000023
fs : 0x00005beb
gs : 0x00000000
ss : 0x00000023
esp_res : 0xfd005fd4
trap_no : 0x0000000e
Stack Crawl:
pc fp procedure
0xeccf121e 0xfd000a10 art_render_composite_rgb8
0xeccf18f0 0xfd000a3c art_render_invoke_callbacks
0xeccf318e 0xfd000a80 art_render_svp_callback
0xeccfaf41 0xfd000ab8 art_svp_render_aa
0xeccf3ad4 0xfd000ae8 art_render_svp_invoke_driver
0xeccf1c69 0xfd000b3c art_render_invoke
0xef2d5825 0xfd000b50 nsSVGRenderingContext::InvokeRender(_ArtRender *)
0xef2d51ca 0xfd000b84
nsSVGRenderingContext::PaintSVGRenderItem(nsSVGRenderItem *)
0xef2c8e97 0xfd000b9c nsSVGGraphic::Paint(nsSVGRenderingContext *)
0xef2c9db5 0xfd000bb4 nsSVGGraphicFrame::Paint(nsSVGRenderingContext *)
0xef2ce23a 0xfd000c28 nsSVGOuterSVGFrame::Paint(nsIPresContext *,
nsIRenderingContext &, nsRect const &, nsFramePaintLayer, unsigned int)
0xef0f4e98 0xfd000cc8 PresShell::Paint(nsIView *, nsIRenderingContext &,
nsRect const &)
0xef7599bb 0xfd000d08 nsView::Paint(nsIRenderingContext &, nsRect const &,
unsigned int, int &)
0xef765f95 0xfd000dcc
nsViewManager::RenderDisplayListElement(DisplayListElement2 *,
nsIRenderingContext &)
0xef765d49 0xfd000e94 nsViewManager::RenderViews(nsView *,
nsIRenderingContext &, nsRect const &, int &)
0xef764616 0xfd00106c nsViewManager::Refresh(nsView *, nsIRenderingContext
*, nsIRegion *, unsigned int)
0xef767cea 0xfd001188 nsViewManager::DispatchEvent(nsGUIEvent *,
nsEventStatus *)
0xef759145 0xfd0011b4 HandleEvent
0xee3dd367 0xfd0011d8 nsWindow::DispatchEvent(nsGUIEvent *, nsEventStatus &)
0xee3dd405 0xfd001200 nsWindow::DispatchWindowEvent(nsGUIEvent *)
0xee3e2174 0xfd0012ac nsWindow::OnPaint(nsRect &)
0xee3e131e 0xfd0013ec nsWindow::CallMethod(MethodInfo *)
0xee3f4251 0xfd00140c
0xee3d5aaf 0xfd001468 nsAppShell::Run(void)
0xee326ff3 0xfd00148c nsAppShellService::Run(void)
0x80021681 0xfd0015d0 main1
0x80021f5c 0xfd001614 main
0x8001bc85 0xfd001640 _start
Comment 1•23 years ago
|
||
I suspect problems rather in mozilla/layout/svg than in libart itself.
Comment 2•23 years ago
|
||
They said that libart required 16-bit color depth. BeZilla uses hardcoded 32
AFAIK. So will wait for patch in libart
Comment 3•22 years ago
|
||
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity. Only changing open bugs to
minimize unnecessary spam. Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
Comment 4•22 years ago
|
||
Probably libart build config misses some important for BeOS options.
Recently i discovered libart_lgpl.so.2.3.3 in my BeOS system, i tried to replace
mozilla's one with it (changing its name to ) - and yes, now BeZilla don't
crash. But shows nothing on SVG pages, and only message which i can see in debug
output is
art_render_new: n_chan = 722976, exceeds 16 max libmoz_art_lgpl.so
instead old crash message
art_render_composite_rgb8 : Segment violation.
Need help from some libart guru.
| Assignee | ||
Comment 5•21 years ago
|
||
This should be fixed by the SVG development branch landing, bug#182533. -> Closing.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•