Page 1 of 1

PM Crash when loading specific reddit page

Posted: 2023-02-05, 17:59
by stux2000
Hi everyone,

I unfortunately am creating this thread to report a browser crash (which I was able to replicate).

The steps are fairly simple:
  • wait for the page to finish loading
  • Expected Result: the page loads normally without issue
  • Actual Result: The browser crashes
Testing information:
  • I tested this on 3 different profiles, one of which has no add-ons. The crash was also confirmed independently by L29Ah.
  • My OS is Windows 7 x64
  • All 3 Profiles are running Pale Moon Portable-64 version 32.0.0
  • Not sure if relevant: CPU = Intel Core i7-4720HQ RAM=16GB
  • I was able to load the page without issue on Firefox EST 102.6.0. I did not try to find it on bugzilla
Here is the gdb trace reported by L29Ah on their system:

Code: Select all

(gdb) bt
#0  js::CreateRegExpMatchResult(JSContext*, js::RegExpShared&, JS::Handle<JSString*>, js::MatchPairs const&, JS::MutableHandle<JS::Value>) (cx=<optimized out>, re=<optimized out>, input=..., matches=..., rval=...)
   at /var/tmp/portage/www-client/palemoon-32.0.0/work/palemoon-32.0.0/platform/js/src/builtin/RegExp.cpp:115
#1  0x00007f5950ef8e3d in js::RegExpMatcherRaw(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSString*>, int, js::MatchPairs*, JS::MutableHandle<JS::Value>)
    (cx=0x7f594872b000, regexp=..., input=..., lastIndex=<optimized out>, maybeMatches=0x7fff7a7cc258, output=...)
    at /var/tmp/portage/www-client/palemoon-32.0.0/work/palemoon-32.0.0/platform/js/src/vm/RegExpObject.h:303
Hope this helps track down the cause of the issue.

-stux

Re: PM Crash when loading specific reddit page

Posted: 2023-02-05, 20:20
by Moonchild
This would be Issue #2093 (UXP) which will be addressed in the next point release.

Re: PM Crash when loading specific reddit page

Posted: 2023-02-25, 21:14
by stux2000
I know it's a bit late but I wanted to thank you Moonchild for the update letting me know of the issue number and upcoming fix. I was able to confirm on my end that the issue was still present on that page on the old 32.0.0 version and it was fixed in the new 32.0.1 version!

Once again, many thanks to everyone involved in fixing this issue!