Closed
Bug 1575205
Opened 5 years ago
Closed 4 years ago
Crash in [@ raise | _IO_vasprintf]
Categories
(Core :: Graphics: CanvasWebGL, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox68 | --- | wontfix |
firefox69 | --- | wontfix |
firefox70 | --- | fix-optional |
People
(Reporter: mberlinger, Unassigned)
Details
(Keywords: crash, regression, regressionwindow-wanted)
Crash Data
Attachments
(1 file)
20.59 KB,
text/plain
|
Details |
This bug is for crash report bp-3ca9472b-a01d-416b-993b-426700190820.
Top 10 frames of crashing thread:
0 libc-2.27.so raise /build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51
1 libc-2.27.so _IO_vasprintf /build/glibc-OTsEL5/glibc-2.27/libio/vasprintf.c:81
2 libc-2.27.so abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:79
3 firefox-bin arena_t::DallocSmall memory/build/mozjemalloc.cpp:3242
4 firefox-bin free memory/build/malloc_decls.h:41
5 libc-2.27.so __assert_fail_base /build/glibc-OTsEL5/glibc-2.27/assert/assert.c:92
6 nouveau_dri.so _fini
7 nouveau_dri.so _fini
8 nouveau_dri.so _fini
9 nouveau_dri.so nouveau_drm_screen_create
Affected versions
- 68.0.2
- 69.0b15
- 70.0a1 (2019-08-20)
Affected platforms
- Ubuntu 18.04x64
Steps to reproduce
- Launch Firefox
- Access http://toji.github.io/webgl2-particles-2/
Expected result
- Page is properly loaded
Actual result
- Tabcrash when loading page
Regression range
- This is not a recent regression since I was able to reproduce it on Firefox 67.0b17. I'll provide a regression range asap, in case there is an old one.
Additional notes
- I’ve tried to reproduce this issue on a different machine with the same Graphics NVIDIA GeForce 210 and Intel Core i5-3470 (3.2 GHz) Processor but without success.
- My machine has AMD FX(tm)-8320 Eight-Core Processor × 8
(3.50GHz) and NVIDIA GeForce 210 Graphics - see the attached txt with about:support data from my computer
- windows and mac platforms are not affected
Comment 1•5 years ago
•
|
||
I tried the STR in comment 0 on Ubuntu 18.04x64 with the following. But I could not reproduce the problem. And from the crash place, it seems related to driver/gpu specific problem.
- 68.0.2
- 69.0b15
- 70.0a1 (2019-08-20)
Comment 2•5 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Keywords: regression
Updated•5 years ago
|
Priority: -- → P3
Updated•5 years ago
|
Has Regression Range: --- → no
Updated•5 years ago
|
Comment 4•4 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Flags: needinfo?(jgilbert)
You need to log in
before you can comment on or make changes to this bug.
Description
•