Closed Bug 13731 Opened 26 years ago Closed 25 years ago

grey line

Categories

(Core :: Layout: Tables, defect, P2)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: rb, Assigned: karnaze)

References

()

Details

If you visit www.vol.at you can see a thin grey line from the left the to right in the middle of the page, sometimes a segfault occurs a few seconds later. debug output: FindShortcut: in='http://www.vol.at' out='null' Warning - table cell content max element height 2038 greater than desired height 346 Warning - table cell content max element height 2038 greater than desired height
Assignee: karnaze → ramiro
I was able to get the following stack on WinNT only once. I do not see the thin line. Ramiro, can you check this out on Linux. NTDLL! DbgBreakPoint@0 address 0x77f76148 nsWindow::StandardWindowCreate(nsIWidget * 0x00000000, const nsRect & {...}, nsEventStatus (nsGUIEvent *)* 0x01803b63 HandleEvent(nsGUIEvent *), nsIDeviceContext * 0x01c1c3d0, nsIAppShell * 0x00000000, nsIToolkit * 0x00000000, nsWidgetInitData * 0x00000000, void * 0x00000000) line 555 + 30 bytes nsWindow::Create(nsWindow * const 0x01ddf1f4, nsIWidget * 0x00000000, const nsRect & {...}, nsEventStatus (nsGUIEvent *)* 0x01803b63 HandleEvent(nsGUIEvent *), nsIDeviceContext * 0x01c1c3d0, nsIAppShell * 0x00000000, nsIToolkit * 0x00000000, nsWidgetInitData * 0x00000000) line 602 nsView::CreateWidget(nsView * const 0x01ddf330, const nsID & {...}, nsWidgetInitData * 0x00000000, void * 0x00000000, int 1) line 1234 DocumentViewerImpl::MakeWindow(void * 0x00000000, const nsRect & {...}, nsScrollPreference nsScrollPreference_kAuto) line 887 + 34 bytes DocumentViewerImpl::Init(DocumentViewerImpl * const 0x01c18690, void * 0x00000000, nsIDeviceContext * 0x01c1c3d0, nsIPref * 0x00b81d70, const nsRect & {...}, nsScrollPreference nsScrollPreference_kAuto) line 394 nsWebShell::Embed(nsWebShell * const 0x01c1c940, nsIContentViewer * 0x01c18690, const char * 0x01c1d1e0, nsISupports * 0x00000000) line 975 + 69 bytes nsDocumentBindInfo::OnStartRequest(nsDocumentBindInfo * const 0x01c1d220, nsIChannel * 0x01c1d090, nsISupports * 0x00000000) line 1896 + 36 bytes nsChannelListener::OnStartRequest(nsChannelListener * const 0x01c1d160, nsIChannel * 0x01c1d090, nsISupports * 0x00000000) line 2234 + 43 bytes nsHTTPResponseListener::FinishedResponseHeaders() line 680 + 37 bytes nsHTTPResponseListener::OnDataAvailable(nsHTTPResponseListener * const 0x01dbe660, nsIChannel * 0x01c1eb20, nsISupports * 0x01c1d090, nsIInputStream * 0x01dbe5e8, unsigned int 0, unsigned int 314) line 166 + 8 bytes nsOnDataAvailableEvent::HandleEvent(nsOnDataAvailableEvent * const 0x01c174e0) line 345 nsStreamListenerEvent::HandlePLEvent(PLEvent * 0x01c174e4) line 144 + 12 bytes PL_HandleEvent(PLEvent * 0x01c174e4) line 509 + 10 bytes PL_ProcessPendingEvents(PLEventQueue * 0x00b80520) line 470 + 9 bytes _md_EventReceiverProc(HWND__ * 0x00010576, unsigned int 49375, unsigned int 0, long 12059936) line 938 + 9 bytes USER32! DispatchMessageWorker@8 + 135 bytes USER32! DispatchMessageA@4 + 11 bytes nsNativeViewerApp::Run() line 56 main(int 1, char * * 0x00b115c0) line 117 + 11 bytes mainCRTStartup() line 338 + 17 bytes
Assignee: ramiro → karnaze
i can browse to this page fine. I dont get a core dump Back to karnaze, if you have a stack trace, then maybe its worth looking into. Or you can mark it worksforme.
Severity: normal → critical
Priority: P3 → P2
Apprunner 1999-10-09-09-M11 on Windows 98 SE - No crash but the main table is displayed twice.
Severity: critical → normal
Status: NEW → ASSIGNED
Summary: grey line + segfault → grey line
Lowering the severity and removing "+ segfault" from summary.
Is there anything still wrong with this page? I think the lines were a dup of bug 15942, and the table appearing twice might have been a content sink bug fixed by vidur's recent checkin?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Marking worksforme.
Status: RESOLVED → VERIFIED
Using 11/16 build on Linux, verifying WORKSFORME
You need to log in before you can comment on or make changes to this bug.