Walmart.com crash

For support with specific websites

Moderator: trava90

Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
User avatar
krkkrk
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2022-07-05, 19:50

Walmart.com crash

Post by krkkrk » 2025-07-09, 14:33

PM 33.8.0 crashes on www.walmart.com.
Tried with empty profile.
Dump uploaded to ftp: walmart-pm-crash.7z

Regards

User avatar
therube
Board Warrior
Board Warrior
Posts: 1755
Joined: 2018-06-08, 17:02

Re: Walmart.com crash

Post by therube » 2025-07-09, 15:19

33.7.0, Win7

No crash, but walmart isn't loading, instead getting:

Sorry...
We’re having technical issues, but
we’ll be back in a flash.
Return to home

At the same time, ah, it works* in SeaMonkey & in FF 115.

That was with scripts blocked.
Enabling scripts in SeaMonkey & I'm in the same boat, the "Sorry..." message.

(So on my end, walmart is only "working" in FF.)


If I spoof the UA (in PM [to FF 115]), I get a "click & hold" prompt, which does, work, & says it was successful, but then it rolls back over to that "Sorry..." message.

User avatar
Moonchild
Project founder
Project founder
Posts: 38813
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Walmart.com crash

Post by Moonchild » 2025-07-09, 15:27

Thanks for the crash dump. It crashes somewhere pretty deep in the javascript engine
Unhandled exception thrown: read access violation.
wrapped->group_.value->**clasp_** was nullptr.

> [Inline Frame] mozjs.dll!js::Class::isProxy() Line 978 C++
[Inline Frame] mozjs.dll!js::IsProxy(const JSObject *) Line 357 C++
[Inline Frame] mozjs.dll!js::IsWrapper(JSObject *) Line 336 C++
[Inline Frame] mozjs.dll!JSObject::is() Line 34 C++
mozjs.dll!js::UncheckedUnwrap(JSObject * wrapped, bool stopAtWindowProxy, unsigned int * flagsp) Line 342 C++
mozjs.dll!JSCompartment::getNonWrapperObjectForCurrentCompartment(JSContext * cx, JS::MutableHandle<JSObject *> obj) Line 384 C++
mozjs.dll!JSCompartment::wrap(JSContext * cx, JS::MutableHandle<JSObject *> obj) Line 476 C++
mozjs.dll!JSCompartment::wrap(JSContext * cx, JS::MutableHandle<JS::Value> vp) Line 126 C++
xul.dll!mozilla::dom::PerformanceMeasureBinding::get_detail(JSContext * cx, JS::Handle<JSObject *> obj, mozilla::dom::PerformanceMeasure * self, JSJitGetterCallArgs args) Line 33 C++
xul.dll!mozilla::dom::GenericBindingGetter(JSContext * cx, unsigned int argc, JS::Value * vp) Line 2857 C++
[Inline Frame] mozjs.dll!js::CallJSNative(JSContext *) Line 238 C++
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 490 C++
mozjs.dll!js::Call(JSContext * cx, JS::Handle<JS::Value> fval, JS::Handle<JS::Value> thisv, const js::AnyInvokeArgs & args, JS::MutableHandle<JS::Value> rval) Line 554 C++
mozjs.dll!js::CallGetter(JSContext * cx, JS::Handle<JS::Value> thisv, JS::Handle<JS::Value> getter, JS::MutableHandle<JS::Value> rval) Line 673 C++
mozjs.dll!CallGetter(JSContext * cx, JS::Handle<JSObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<js::Shape *> shape, JS::MutableHandle<JS::Value> vp) Line 1843 C++
[Inline Frame] mozjs.dll!GetExistingProperty(JSContext *) Line 1891 C++
[Inline Frame] mozjs.dll!NativeGetPropertyInline(JSContext *) Line 2119 C++
mozjs.dll!js::NativeGetProperty(JSContext * cx, JS::Handle<js::NativeObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<jsid> id, JS::MutableHandle<JS::Value> vp) Line 2153 C++
[Inline Frame] mozjs.dll!js::GetProperty(JSContext *) Line 1539 C++
mozjs.dll!js::GetProperty(JSContext * cx, JS::Handle<JSObject *> obj, JS::Handle<JS::Value> receiver, js::PropertyName * name, JS::MutableHandle<JS::Value> vp) Line 837 C++
mozjs.dll!js::GetProperty(JSContext * cx, JS::Handle<JS::Value> v, JS::Handle<js::PropertyName *> name, JS::MutableHandle<JS::Value> vp) Line 4352 C++
mozjs.dll!GetPropertyOperation(JSContext * cx, js::InterpreterFrame * fp, JS::Handle<JSScript *> script, unsigned char * pc, JS::MutableHandle<JS::Value> lval, JS::MutableHandle<JS::Value> vp) Line 195 C++
mozjs.dll!Interpret(JSContext * cx, js::RunState & state) Line 2629 C++
mozjs.dll!js::RunScript(JSContext * cx, js::RunState & state) Line 422 C++
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 511 C++
mozjs.dll!Interpret(JSContext * cx, js::RunState & state) Line 2917 C++
mozjs.dll!js::RunScript(JSContext * cx, js::RunState & state) Line 422 C++
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 511 C++
mozjs.dll!Interpret(JSContext * cx, js::RunState & state) Line 2917 C++
mozjs.dll!js::RunScript(JSContext * cx, js::RunState & state) Line 422 C++
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 511 C++
mozjs.dll!js::Call(JSContext * cx, JS::Handle<JS::Value> fval, JS::Handle<JS::Value> thisv, const js::AnyInvokeArgs & args, JS::MutableHandle<JS::Value> rval) Line 554 C++
mozjs.dll!js::fun_apply(JSContext * cx, unsigned int argc, JS::Value * vp) Line 1248 C++
[Inline Frame] mozjs.dll!js::CallJSNative(JSContext *) Line 238 C++
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 490 C++
mozjs.dll!js::jit::DoCallFallback(JSContext * cx, js::jit::BaselineFrame * frame, js::jit::ICCall_Fallback * stub_, unsigned int argc, JS::Value * vp, JS::MutableHandle<JS::Value> res) Line 5952 C++
[External Code]
Unfortunately I can't glean much from the stack other than it seems to be related to the DOM performance API somewhere.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Moonchild
Project founder
Project founder
Posts: 38813
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Walmart.com crash

Post by Moonchild » 2025-07-09, 15:28

I also can't reproduce the crash myself; but that's primarily because Walmart's website is reporting problems with the site.
You do not have the required permissions to view the files attached to this post.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
krkkrk
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2022-07-05, 19:50

Re: Walmart.com crash

Post by krkkrk » 2025-07-09, 16:08

Hi @Moonchild,

It requires performance observers to be enabled, otherwise it just shows this screen.

Regards

User avatar
mmouse
Moon lover
Moon lover
Posts: 85
Joined: 2019-02-13, 06:47

Re: Walmart.com crash

Post by mmouse » 2025-07-09, 16:29

@krkkrk

Here with Palemoon 33.8.0 Linux Gtk 3 no Avx and dom.enable_performance_observer=true I don't see a clear difference with Firefox (I just tried to click 3 items to be candid - but no crash)

User avatar
krkkrk
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2022-07-05, 19:50

Re: Walmart.com crash

Post by krkkrk » 2025-07-09, 16:53

I am on Win11 x64.
Crashes every time on clean profile after about 10 seconds on the site.

Regards

Goodydino
Keeps coming back
Keeps coming back
Posts: 940
Joined: 2017-10-10, 21:20

Re: Walmart.com crash

Post by Goodydino » 2025-07-09, 19:36

It did not crash for me. I have dom.enable.performance as false.

User avatar
mmouse
Moon lover
Moon lover
Posts: 85
Joined: 2019-02-13, 06:47

Re: Walmart.com crash

Post by mmouse » 2025-07-09, 19:59

@krkkrk

trying a bit more, after 1 or 2 minutes of trying to move between options I get a 'Sorry Technical Issues...' but I can reload the site. Some buttons seem to not work.
But no crash. It could be operating system specific. Maybe other people will report.

User avatar
Moonchild
Project founder
Project founder
Posts: 38813
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Walmart.com crash

Post by Moonchild » 2025-07-09, 21:39

I'm having the same issue with performance observer enabled. I did coerce it into a crash-to-desktop after a lot of trying, but not before I had the site itself choke on its own scripting with the error page shown a lot of times before; I'm guessing it relies really heavily on performance observers for basic site functionality (because walmart wants to track your every move on their website, I think, because management reports or something) and there are serious issues with Pale Moon's timing for scripts being very much different than Blink/Gecko... -- Sites should not rely on this primarily webmaster debugging API for basic functionality, and should operate without it, but eh, what do I know. :roll:

I caught the crash in a debugger but it doesn't really point me to what is going on other than somewhere losing its way between multiple recursive scripting calls, and will likely need at the very least a debug build to get more details about the problem. Even then, analyzing it will be difficult because this part of the code is very complex and uses a lot of pointer juggling and tricks and is not at all easy to understand.

There's no workaround in the interim, I'm afraid. Use a different browser for Walmart.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
CHris Hitarori
Hobby Astronomer
Hobby Astronomer
Posts: 28
Joined: 2024-01-31, 14:02

Re: Walmart.com crash

Post by CHris Hitarori » 2025-07-09, 22:39

mmouse wrote:
2025-07-09, 19:59
It could be operating system specific. Maybe other people will report.
I can reproduce the crash on Mac OS X 10.11 (El Capitan) with 33.8.0, but not with 33.6.1.

van p
Astronaut
Astronaut
Posts: 684
Joined: 2015-11-19, 07:15
Location: Cincinnati, OH, U.S.A.

Re: Walmart.com crash

Post by van p » 2025-07-10, 04:16

I gave up quite some time ago trying to use Pale Moon on Walmart's site because pictures of the products didn't display. Now, I'm getting the 'technical issues' screen after a couple seconds. I now use a Chromium browser on that site and everything works.
Windows 10 Pro x64 v22H2 8GB i5-4570|Pale Moon v34.0.1 x64

User avatar
krkkrk
Hobby Astronomer
Hobby Astronomer
Posts: 18
Joined: 2022-07-05, 19:50

Re: Walmart.com crash

Post by krkkrk » 2025-07-11, 14:45

van p wrote:
2025-07-10, 04:16
I gave up quite some time ago trying to use Pale Moon on Walmart's site because pictures of the products didn't display. Now, I'm getting the 'technical issues' screen after a couple seconds. I now use a Chromium browser on that site and everything works.
If I remember correctly there was a fix on this forum for images not showing on Walmart.
I also use Chrome clone for all sites that do not work in PM.
Just trying to make PM the best browser.

Thanks all for all hard work.

dbsoft
Project Contributor
Project Contributor
Posts: 515
Joined: 2020-02-21, 17:35

Re: Walmart.com crash

Post by dbsoft » 2025-07-16, 05:21

This is the same performance observers crash that I investigated years ago and was never able to figure out. Just debugged it myself and got a similar call stack to what Moonchild quoted.

Code: Select all

clang_rt.asan_dynamic-x86_64.dll!ShadowExceptionHandler()
ntdll.dll!RtlpCallVectoredHandlers()
ntdll.dll!RtlDispatchException()
ntdll.dll!KiUserExceptionDispatch()
mozjs.dll!JSCompartment::unsafeUnbarrieredMaybeGlobal() Line 33
	at c:\Work\PaleMoon\White-Star\platform\js\src\jscompartmentinlines.h(33)
mozjs.dll!JSObject::global() Line 444
	at c:\Work\PaleMoon\White-Star\platform\js\src\jsobjinlines.h(444)
mozjs.dll!JSCompartment::getNonWrapperObjectForCurrentCompartment(JSContext * cx, JS::MutableHandle<JSObject *> obj) Line 368
	at c:\Work\PaleMoon\White-Star\platform\js\src\jscompartment.cpp(368)
mozjs.dll!JSCompartment::wrap(JSContext * cx, JS::MutableHandle<JSObject *> obj) Line 476
	at c:\Work\PaleMoon\White-Star\platform\js\src\jscompartment.cpp(476)
mozjs.dll!JSCompartment::wrap(JSContext * cx, JS::MutableHandle<JS::Value> vp) Line 126
	at c:\Work\PaleMoon\White-Star\platform\js\src\jscompartmentinlines.h(126)
mozjs.dll!JS_WrapValue(JSContext * cx, JS::MutableHandle<JS::Value> vp) Line 799
	at c:\Work\PaleMoon\White-Star\platform\js\src\jsapi.cpp(799)
xul.dll!mozilla::dom::MaybeWrapObjectValue(JSContext * cx, JS::MutableHandle<JS::Value> rval) Line 974
	at c:\Work\PaleMoon\White-Star\obj-x86_64-pc-mingw32\dist\include\mozilla\dom\BindingUtils.h(974)
xul.dll!mozilla::dom::MaybeWrapValue(JSContext * cx, JS::MutableHandle<JS::Value> rval) Line 1040
	at c:\Work\PaleMoon\White-Star\obj-x86_64-pc-mingw32\dist\include\mozilla\dom\BindingUtils.h(1040)
xul.dll!mozilla::dom::PerformanceMeasureBinding::get_detail(JSContext * cx, JS::Handle<JSObject *> obj, mozilla::dom::PerformanceMeasure * self, JSJitGetterCallArgs args) Line 29
	at c:\Work\PaleMoon\White-Star\obj-x86_64-pc-mingw32\dom\bindings\PerformanceMeasureBinding.cpp(29)
xul.dll!mozilla::dom::GenericBindingGetter(JSContext * cx, unsigned int argc, JS::Value * vp) Line 2851
	at c:\Work\PaleMoon\White-Star\platform\dom\bindings\BindingUtils.cpp(2851)
mozjs.dll!js::CallJSNative(JSContext * cx, bool(*)(JSContext *, unsigned int, JS::Value *) native, const JS::CallArgs & args) Line 238
	at c:\Work\PaleMoon\White-Star\platform\js\src\jscntxtinlines.h(238)
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 490
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(490)
mozjs.dll!InternalCall(JSContext * cx, const js::AnyInvokeArgs & args) Line 535
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(535)
mozjs.dll!js::Call(JSContext * cx, JS::Handle<JS::Value> fval, JS::Handle<JS::Value> thisv, const js::AnyInvokeArgs & args, JS::MutableHandle<JS::Value> rval) Line 554
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(554)
mozjs.dll!js::CallGetter(JSContext * cx, JS::Handle<JS::Value> thisv, JS::Handle<JS::Value> getter, JS::MutableHandle<JS::Value> rval) Line 673
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(673)
mozjs.dll!CallGetter(JSContext * cx, JS::Handle<JSObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<js::Shape *> shape, JS::MutableHandle<JS::Value> vp) Line 1843
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\NativeObject.cpp(1843)
mozjs.dll!GetExistingProperty<1>(JSContext * cx, JS::Handle<JS::Value> receiver, JS::Handle<js::NativeObject *> obj, JS::Handle<js::Shape *> shape, JS::MutableHandle<JS::Value> vp) Line 1891
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\NativeObject.cpp(1891)
mozjs.dll!NativeGetPropertyInline<1>(JSContext * cx, JS::Handle<js::NativeObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<jsid> id, IsNameLookup nameLookup, JS::MutableHandle<JS::Value> vp) Line 2119
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\NativeObject.cpp(2119)
mozjs.dll!js::NativeGetProperty(JSContext * cx, JS::Handle<js::NativeObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<jsid> id, JS::MutableHandle<JS::Value> vp) Line 2154
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\NativeObject.cpp(2154)
mozjs.dll!js::GetProperty(JSContext * cx, JS::Handle<JSObject *> obj, JS::Handle<JS::Value> receiver, JS::Handle<jsid> id, JS::MutableHandle<JS::Value> vp) Line 1539
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\NativeObject.h(1539)
mozjs.dll!js::GetProperty(JSContext * cx, JS::Handle<JSObject *> obj, JS::Handle<JS::Value> receiver, js::PropertyName * name, JS::MutableHandle<JS::Value> vp) Line 836
	at c:\Work\PaleMoon\White-Star\platform\js\src\jsobj.h(836)
mozjs.dll!js::GetProperty(JSContext * cx, JS::Handle<JS::Value> v, JS::Handle<js::PropertyName *> name, JS::MutableHandle<JS::Value> vp) Line 4352
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(4352)
mozjs.dll!GetPropertyOperation(JSContext * cx, js::InterpreterFrame * fp, JS::Handle<JSScript *> script, unsigned char * pc, JS::MutableHandle<JS::Value> lval, JS::MutableHandle<JS::Value> vp) Line 195
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(195)
mozjs.dll!Interpret(JSContext * cx, js::RunState & state) Line 2629
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(2629)
mozjs.dll!js::RunScript(JSContext * cx, js::RunState & state) Line 422
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(422)
mozjs.dll!js::InternalCallOrConstruct(JSContext * cx, const JS::CallArgs & args, js::MaybeConstruct construct) Line 508
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(508)
mozjs.dll!InternalCall(JSContext * cx, const js::AnyInvokeArgs & args) Line 535
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(535)
mozjs.dll!js::CallFromStack(JSContext * cx, const JS::CallArgs & args) Line 542
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Interpreter.cpp(542)
mozjs.dll!js::jit::DoCallFallback(JSContext * cx, js::jit::BaselineFrame * frame, js::jit::ICCall_Fallback * stub_, unsigned int argc, JS::Value * vp, JS::MutableHandle<JS::Value> res) Line 5946
	at c:\Work\PaleMoon\White-Star\platform\js\src\jit\BaselineIC.cpp(5946)
[External Code]
mozjs.dll!js::Activation::registerProfiling() Line 1691
	at c:\Work\PaleMoon\White-Star\platform\js\src\vm\Stack.cpp(1691)
All of the crashes I observed involve this call:

Code: Select all

xul.dll!mozilla::dom::PerformanceMeasureBinding::get_detail(JSContext * cx, JS::Handle<JSObject *> obj, mozilla::dom::PerformanceMeasure * self, JSJitGetterCallArgs args) 

dbsoft
Project Contributor
Project Contributor
Posts: 515
Joined: 2020-02-21, 17:35

Re: Walmart.com crash

Post by dbsoft » 2025-07-16, 05:57

Interesting, I ran it again with the thought to look at some of the variables and such and I hit an ASSERT...

Code: Select all

mozjs.dll!js::gc::Arena::getAllocKind() Line 606
	at c:\Work\PaleMoon\White-Star\platform\js\src\gc\Heap.h(606)
mozjs.dll!js::gc::TenuredCell::getAllocKind() Line 1271
	at c:\Work\PaleMoon\White-Star\platform\js\src\gc\Heap.h(1271)
mozjs.dll!js::gc::AssertGCThingHasType(js::gc::Cell * cell, JS::TraceKind kind) Line 6422
	at c:\Work\PaleMoon\White-Star\platform\js\src\jsgc.cpp(6422)
mozjs.dll!JS::GCCellPtr::checkedCast(void * p, JS::TraceKind traceKind) Line 226
	at c:\Work\PaleMoon\White-Star\obj-x86_64-pc-mingw32\dist\include\js\HeapAPI.h(226)
mozjs.dll!JS::GCCellPtr::GCCellPtr(const JS::Value & v) Line 6561
	at c:\Work\PaleMoon\White-Star\platform\js\src\jsgc.cpp(6561)
xul.dll!TraceCallbackFunc::Trace(JS::Heap<JS::Value> * aPtr, const char * aName, void * aClosure) Line 40
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollectorTraceJSHelpers.cpp(40)
xul.dll!mozilla::dom::PerformanceMeasure::cycleCollection::Trace(void * p, const TraceCallbacks & aCallbacks, void * aClosure) Line 43
	at c:\Work\PaleMoon\White-Star\platform\dom\performance\PerformanceMeasure.cpp(43)
xul.dll!nsCycleCollectionParticipant::TraverseNativeAndJS(void * aPtr, nsCycleCollectionTraversalCallback & aCb) Line 143
	at c:\Work\PaleMoon\White-Star\obj-x86_64-pc-mingw32\dist\include\nsCycleCollectionParticipant.h(143)
xul.dll!MayHaveChild(void * aObj, nsCycleCollectionParticipant * aCp) Line 2534
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(2534)
xul.dll!RemoveSkippableVisitor::Visit(nsPurpleBuffer & aBuffer, nsPurpleBufferEntry * aEntry) Line 2770
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(2770)
xul.dll!nsPurpleBuffer::VisitEntries<RemoveSkippableVisitor>(RemoveSkippableVisitor & aVisitor) Line 1056
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(1056)
xul.dll!nsPurpleBuffer::RemoveSkippable(nsCycleCollector * aCollector, bool aRemoveChildlessNodes, bool aAsyncSnowWhiteFreeing, void(*)() aCb) Line 2793
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(2793)
xul.dll!nsCycleCollector::ForgetSkippable(bool aRemoveChildlessNodes, bool aAsyncSnowWhiteFreeing) Line 2847
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(2847)
xul.dll!nsCycleCollector_forgetSkippable(bool aRemoveChildlessNodes, bool aAsyncSnowWhiteFreeing) Line 4061
	at c:\Work\PaleMoon\White-Star\platform\xpcom\base\nsCycleCollector.cpp(4061)
xul.dll!FireForgetSkippable(unsigned int aSuspected, bool aRemoveChildless) Line 1144
	at c:\Work\PaleMoon\White-Star\platform\dom\base\nsJSEnvironment.cpp(1144)
xul.dll!CCTimerFired(nsITimer * aTimer, void * aClosure) Line 1697
	at c:\Work\PaleMoon\White-Star\platform\dom\base\nsJSEnvironment.cpp(1697)
xul.dll!nsTimerImpl::Fire(int aGeneration) Line 486
	at c:\Work\PaleMoon\White-Star\platform\xpcom\threads\nsTimerImpl.cpp(486)
xul.dll!nsTimerEvent::Run() Line 277
	at c:\Work\PaleMoon\White-Star\platform\xpcom\threads\TimerThread.cpp(277)
xul.dll!nsThread::ProcessNextEvent(bool aMayWait, bool * aResult) Line 1140
	at c:\Work\PaleMoon\White-Star\platform\xpcom\threads\nsThread.cpp(1140)
xul.dll!NS_ProcessNextEvent(nsIThread * aThread, bool aMayWait) Line 355
	at c:\Work\PaleMoon\White-Star\platform\xpcom\glue\nsThreadUtils.cpp(355)
xul.dll!mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate * aDelegate) Line 95
	at c:\Work\PaleMoon\White-Star\platform\ipc\glue\MessagePump.cpp(95)
xul.dll!MessageLoop::RunInternal() Line 228
	at c:\Work\PaleMoon\White-Star\platform\ipc\chromium\src\base\message_loop.cc(228)
xul.dll!MessageLoop::RunHandler() Line 221
	at c:\Work\PaleMoon\White-Star\platform\ipc\chromium\src\base\message_loop.cc(221)
xul.dll!MessageLoop::Run() Line 202
	at c:\Work\PaleMoon\White-Star\platform\ipc\chromium\src\base\message_loop.cc(202)
xul.dll!nsBaseAppShell::Run() Line 155
	at c:\Work\PaleMoon\White-Star\platform\widget\nsBaseAppShell.cpp(155)
xul.dll!nsAppShell::Run() Line 204
	at c:\Work\PaleMoon\White-Star\platform\widget\windows\nsAppShell.cpp(204)
xul.dll!nsAppStartup::Run() Line 282
	at c:\Work\PaleMoon\White-Star\platform\toolkit\components\startup\nsAppStartup.cpp(282)
xul.dll!XREMain::XRE_mainRun() Line 3789
	at c:\Work\PaleMoon\White-Star\platform\toolkit\xre\nsAppRunner.cpp(3789)
xul.dll!XREMain::XRE_main(int argc, char * * argv, const nsXREAppData * aAppData) Line 3893
	at c:\Work\PaleMoon\White-Star\platform\toolkit\xre\nsAppRunner.cpp(3893)
xul.dll!XRE_main(int argc, char * * argv, const nsXREAppData * aAppData, unsigned int aFlags) Line 3975
	at c:\Work\PaleMoon\White-Star\platform\toolkit\xre\nsAppRunner.cpp(3975)
whitestar.exe!do_main(int argc, char * * argv, char * * envp, nsIFile * xreDirectory) Line 253
	at c:\Work\PaleMoon\White-Star\whitestar\app\nsBrowserApp.cpp(253)
whitestar.exe!NS_internal_main(int argc, char * * argv, char * * envp) Line 377
	at c:\Work\PaleMoon\White-Star\whitestar\app\nsBrowserApp.cpp(377)
whitestar.exe!wmain(int argc, wchar_t * * argv) Line 111
	at c:\Work\PaleMoon\White-Star\platform\toolkit\xre\nsWindowsWMain.cpp(111)
Assert is here:

Code: Select all

    AllocKind getAllocKind() const {
        MOZ_ASSERT(allocated());  <-----
        return AllocKind(allocKind);
    }
allocKind is 30... which it looks like is probably REGEXP_SHARED if it isn't uninitialized. Sorry, 29 is REGEXP_SHARED, 30 is outside the valid range which is why it is failing that ASSERT.

dbsoft
Project Contributor
Project Contributor
Posts: 515
Joined: 2020-02-21, 17:35

Re: Walmart.com crash

Post by dbsoft » 2025-07-19, 18:12

Just going to link the issue I investigated in the past that might be the same problem resurfacing:

https://repo.palemoon.org/MoonchildProd ... ssues/2255

User avatar
Stargate38
Moon lover
Moon lover
Posts: 95
Joined: 2018-05-27, 22:55
Location: Earth

Re: Walmart.com crash

Post by Stargate38 » 2025-10-24, 21:58

Just happened to me. Hoping this gets fixed soon, as I want to be able to shop their store using PM again.

Link where it happened: https://www.walmart.com/ip/WW-HVY-WT-HO ... 5459567819

It takes several seconds for the crash to happen, and seems to be after the page is almost fully loaded.

User avatar
Night Wing
Knows the dark side
Knows the dark side
Posts: 5734
Joined: 2011-10-03, 10:19
Location: Piney Woods of Southeast Texas, USA

Re: Walmart.com crash

Post by Night Wing » 2025-10-25, 01:57

Stargate38 wrote:
2025-10-24, 21:58
Just happened to me. Hoping this gets fixed soon, as I want to be able to shop their store using PM again.

Link where it happened: https://www.walmart.com/ip/WW-HVY-WT-HO ... 5459567819
When I clicked on your link, the page which showed up said, "Sorry. We are having technical issues".

At the time of this posting I am using 64 bit linux Pale Moon (GTK2) 33.9.1 running in 64 bit MX Linux 23.6 (Libretto) Xfce.
MX Linux 25.1 (Infinity) Xfce w/Pale Moon, Waterfox, Firefox
Linux Debian 13.3 (Trixie) Xfce w/Pale Moon, Waterfox, Firefox