Jump to content

My Browser Builds (Part 1)


Recommended Posts

14 hours ago, roytam1 said:

I can only provide PDB files of latest build, please let me know which archive you use (new builds are uploaded to server now, you may try that first)

Debug symbols for this build, crashes when close the browser (not always but often).

palemoon-27.9.6.win32-git-20190831-18efcca64-xpmod-sse.7z

Link to comment
Share on other sites


Dr.Mingw debug report hope this helps find the issue.

 

[First Debug Window]

plugin-container.exe caused a Breakpoint at location 100010bc in module mozalloc.dll.

Registers:
eax=00000000 ebx=00000001 ecx=002a0ed3 edx=00360ea8 esi=00000000 edi=00292425
eip=100010bc esp=0451f9b8 ebp=01a6bb4c iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000206

Call stack:
100010BC  mozalloc.dll:100010BC  mozalloc_abort  mozalloc_abort.cpp:37
006C06AA  xul.dll:006C06AA  NS_DebugBreak  nsdebugimpl.cpp:398
0087A63E  xul.dll:0087A63E  mozilla::ipc::MessageChannel::OnChannelErrorFromLink  messagechannel.cpp:1589
0087A5D8  xul.dll:0087A5D8  mozilla::ipc::ProcessLink::OnChannelError  messagelink.cpp:406
00863C6D  xul.dll:00863C6D  IPC::Channel::ChannelImpl::OnIOCompleted  ipc_channel_win.cc:488
00860895  xul.dll:00860895  base::MessagePumpForIO::DoRunLoop  message_pump_win.cc:463
00860E41  xul.dll:00860E41  base::MessagePumpWin::Run  message_pump_win.h:78
0086B035  xul.dll:0086B035  MessageLoop::RunHandler  message_loop.cc:227
0086ADFF  xul.dll:0086ADFF  MessageLoop::Run  message_loop.cc:201
0086F213  xul.dll:0086F213  base::Thread::ThreadMain  thread.cc:173
00861549  xul.dll:00861549  `anonymous namespace'::ThreadFunc  platform_thread_win.cc:27
7C80B713  kernel32.dll:7C80B713  GetModuleFileNameA

 

 

[Second Debug Window]

palemoon.exe caused an Access Violation at location 019276a9 in module xul.dll Reading from location 00000000.

Registers:
eax=0012fb00 ebx=0679d801 ecx=00000001 edx=034f23fc esi=06c3b420 edi=00000000
eip=019276a9 esp=0012fad0 ebp=034be830 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202

Call stack:
019276A9  xul.dll:019276A9  mozilla::ipc::MessageChannel::Call  messagechannel.cpp:848
0199EE96  xul.dll:0199EE96  mozilla::plugins::PPluginModuleParent::CallNP_Shutdown  ppluginmoduleparent.cpp:385
0251A782  xul.dll:0251A782  mozilla::plugins::PluginModuleParent::NP_Shutdown  pluginmoduleparent.cpp:1905
024EBB71  xul.dll:024EBB71  nsNPAPIPlugin::Shutdown  nsnpapiplugin.cpp:507
0250501C  xul.dll:0250501C  nsPluginTag::TryUnloadPlugin  nsplugintags.cpp:607
024F3CE9  xul.dll:024F3CE9  nsPluginHost::UnloadPlugins  nspluginhost.cpp:679
024F0DDB  xul.dll:024F0DDB  nsPluginHost::Observe  nspluginhost.cpp:3367
017811FF  xul.dll:017811FF  nsObserverList::NotifyObservers  nsobserverlist.cpp:100
017812BA  xul.dll:017812BA  nsObserverService::NotifyObservers  nsobserverservice.cpp:338
017B9EA4  xul.dll:017B9EA4  mozilla::ShutdownXPCOM  xpcominit.cpp:801
02AF0003  xul.dll:02AF0003  ScopedXPCOMStartup::~ScopedXPCOMStartup  nsapprunner.cpp:1105
02AF0137  xul.dll:02AF0137  mozilla::UniquePtr<ScopedXPCOMStartup,mozilla::DefaultDelete<ScopedXPCOMStartup> >::operator=  uniqueptr.h:278
02AF407F  xul.dll:02AF407F  XREMain::XRE_main  nsapprunner.cpp:3875
02AF553D  xul.dll:02AF553D  XRE_main  nsapprunner.cpp:3922
01785874  xul.dll:01785874  nsLocalFile::Append  nslocalfilewin.cpp:1410
0178142D  xul.dll:0178142D  mozilla::TimeStamp::ProcessCreation  timestamp.cpp:68
02AD8DE7  xul.dll:02AD8DE7  mozilla::StartupTimelineRecordExternal  startuptimeline.cpp:37
02AD93D1  xul.dll:02AD93D1  XRE_StartupTimelineRecord  startuptimeline.cpp:66
0040196C  palemoon.exe:0040196C  NS_internal_main  nsbrowserapp.cpp:481
00402236  palemoon.exe:00402236  wmain  nswindowswmain.cpp:124
00402CF9  palemoon.exe:00402CF9  __tmainCRTStartup  crt0.c:255
7C817067  kernel32.dll:7C817067  RegisterWaitForInputIdle

 

Edited by exogenesis
Link to comment
Share on other sites

23 minutes ago, exogenesis said:

Dr.Mingw debug report hope this helps find the issue.

 

[First Debug Window]

plugin-container.exe caused a Breakpoint at location 100010bc in module mozalloc.dll.

Registers:
eax=00000000 ebx=00000001 ecx=002a0ed3 edx=00360ea8 esi=00000000 edi=00292425
eip=100010bc esp=0451f9b8 ebp=01a6bb4c iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000206

Call stack:
100010BC  mozalloc.dll:100010BC  mozalloc_abort  mozalloc_abort.cpp:37
006C06AA  xul.dll:006C06AA  NS_DebugBreak  nsdebugimpl.cpp:398
0087A63E  xul.dll:0087A63E  mozilla::ipc::MessageChannel::OnChannelErrorFromLink  messagechannel.cpp:1589
0087A5D8  xul.dll:0087A5D8  mozilla::ipc::ProcessLink::OnChannelError  messagelink.cpp:406
00863C6D  xul.dll:00863C6D  IPC::Channel::ChannelImpl::OnIOCompleted  ipc_channel_win.cc:488
00860895  xul.dll:00860895  base::MessagePumpForIO::DoRunLoop  message_pump_win.cc:463
00860E41  xul.dll:00860E41  base::MessagePumpWin::Run  message_pump_win.h:78
0086B035  xul.dll:0086B035  MessageLoop::RunHandler  message_loop.cc:227
0086ADFF  xul.dll:0086ADFF  MessageLoop::Run  message_loop.cc:201
0086F213  xul.dll:0086F213  base::Thread::ThreadMain  thread.cc:173
00861549  xul.dll:00861549  `anonymous namespace'::ThreadFunc  platform_thread_win.cc:27
7C80B713  kernel32.dll:7C80B713  GetModuleFileNameA

 

 

[Second Debug Window]

palemoon.exe caused an Access Violation at location 019276a9 in module xul.dll Reading from location 00000000.

Registers:
eax=0012fb00 ebx=0679d801 ecx=00000001 edx=034f23fc esi=06c3b420 edi=00000000
eip=019276a9 esp=0012fad0 ebp=034be830 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202

Call stack:
019276A9  xul.dll:019276A9  mozilla::ipc::MessageChannel::Call  messagechannel.cpp:848
0199EE96  xul.dll:0199EE96  mozilla::plugins::PPluginModuleParent::CallNP_Shutdown  ppluginmoduleparent.cpp:385
0251A782  xul.dll:0251A782  mozilla::plugins::PluginModuleParent::NP_Shutdown  pluginmoduleparent.cpp:1905
024EBB71  xul.dll:024EBB71  nsNPAPIPlugin::Shutdown  nsnpapiplugin.cpp:507
0250501C  xul.dll:0250501C  nsPluginTag::TryUnloadPlugin  nsplugintags.cpp:607
024F3CE9  xul.dll:024F3CE9  nsPluginHost::UnloadPlugins  nspluginhost.cpp:679
024F0DDB  xul.dll:024F0DDB  nsPluginHost::Observe  nspluginhost.cpp:3367
017811FF  xul.dll:017811FF  nsObserverList::NotifyObservers  nsobserverlist.cpp:100
017812BA  xul.dll:017812BA  nsObserverService::NotifyObservers  nsobserverservice.cpp:338
017B9EA4  xul.dll:017B9EA4  mozilla::ShutdownXPCOM  xpcominit.cpp:801
02AF0003  xul.dll:02AF0003  ScopedXPCOMStartup::~ScopedXPCOMStartup  nsapprunner.cpp:1105
02AF0137  xul.dll:02AF0137  mozilla::UniquePtr<ScopedXPCOMStartup,mozilla::DefaultDelete<ScopedXPCOMStartup> >::operator=  uniqueptr.h:278
02AF407F  xul.dll:02AF407F  XREMain::XRE_main  nsapprunner.cpp:3875
02AF553D  xul.dll:02AF553D  XRE_main  nsapprunner.cpp:3922
01785874  xul.dll:01785874  nsLocalFile::Append  nslocalfilewin.cpp:1410
0178142D  xul.dll:0178142D  mozilla::TimeStamp::ProcessCreation  timestamp.cpp:68
02AD8DE7  xul.dll:02AD8DE7  mozilla::StartupTimelineRecordExternal  startuptimeline.cpp:37
02AD93D1  xul.dll:02AD93D1  XRE_StartupTimelineRecord  startuptimeline.cpp:66
0040196C  palemoon.exe:0040196C  NS_internal_main  nsbrowserapp.cpp:481
00402236  palemoon.exe:00402236  wmain  nswindowswmain.cpp:124
00402CF9  palemoon.exe:00402CF9  __tmainCRTStartup  crt0.c:255
7C817067  kernel32.dll:7C817067  RegisterWaitForInputIdle

 

the first one is intended to "break": https://github.com/roytam1/palemoon27/blob/master/ipc/glue/MessageChannel.cpp#L1589

the second one may be able to get rid: https://github.com/roytam1/palemoon27/blob/master/ipc/glue/MessageChannel.cpp#L848

both of them refers to same problem: plugin terminates too early that browser can't catch.

Link to comment
Share on other sites

hey guys-

Sorry once again, I was away for the week. but summer is over, which means vacations are too for me. The server file is updated so the installer will download the latest builds, and the promised new installer version that doesnt need it is coming soon-- I have much more time on my hands now.

:)

Link to comment
Share on other sites

On 8/31/2019 at 1:00 PM, roytam1 said:

New build of Firefox 45ESR SSE:

Changes since my last build:

- import changes from tenfourfox:
 - #521: baseline parser support for async/await, with toggle, without bytecode (passes tests) (0e5746aaf)
 - #521: fix yield handling (includes M1305566 pts 4-7) (2d25f717b)
 - #521: make async functions throw for compatibility when enabled (46b01b5d4)

it is worth mentioning that my fx45esr will now throw runtime error instead of syntax error when hitting async/await, thanks tenfourfox for implementing this!

Link to comment
Share on other sites

15 hours ago, roytam1 said:

the first one is intended to "break": https://github.com/roytam1/palemoon27/blob/master/ipc/glue/MessageChannel.cpp#L1589

the second one may be able to get rid: https://github.com/roytam1/palemoon27/blob/master/ipc/glue/MessageChannel.cpp#L848

both of them refers to same problem: plugin terminates too early that browser can't catch.

Just noticed if makes a difference the report windows are the wrong way round, swap them for which window appears first.

[First Debug Window] = [Second Debug Window]

[Second Debug Window] = [First Debug Window]

Not that it this info is needed maybe! Posted just in case it does.

Link to comment
Share on other sites

A couple of days ago I've noticed, that on you tube the button that said show more n the recommended for you has gone with the wind. Please see image attached. I can assure you it was there at least 10 days ago. Same applies to opera,google chrome , mypal and basilisk. However when I change Basilisk's user agent to win 7 I do get the boring infinite scrolling. At first I thought it was xp related. Then I tried good old firefox esr and to my surprise I do get the infinite scrolling which by the way it is such an anathema. As far as comments are concerned you still get the show more comments button .  Any ideas on that ?

Cheers

imagem.JPG

Link to comment
Share on other sites

2 hours ago, 404notfound said:

Github's interface is broken in v52-based Serpent.

Thankfully, I'm not seeing this here, not yet anyway - however, things do look grim in the weeks to come:

1. Today is the release date of Firefox ESR v60.9.0, the last member of the 60esr branch:

https://www.mozilla.org/en-US/firefox/60.9.0/releasenotes/

v60.9.0 will become EoS on Oct 22nd, when v68.2.0 will be released (there won't be a 60.10.0, of course) and existing 60.9.0esr users will be migrated to 68.2.0esr.

https://wiki.mozilla.org/Release_Management/Calendar

2. UXP's (platform) support for GitHub is based on the fact the javascript code they (GitHub) are serving to Firefox ESR 60.x.x (which they'll support until it reaches EoS) is still compatible with UXP (and hence with browsers like New Moon 28 and Serpent 52.9.0 built on top of it...).

3. Serpent 52.9.0 doesn't have a native SSUAO for GitHub, but if the following prefs are at these posted values:

general.useragent.compatMode.firefox;true (user set)
general.useragent.compatMode.version;60.9 (default)

I find that GitHub still works at the time of this writing:

GB0Fx4u.jpg

I also find that a SSUAO for GitHub of the following format:

general.useragent.override.github.com;Mozilla/5.0 (Windows NT 6.0; rv:52.0) Goanna/4.4 Basilisk/52.9.0

also does the job if I set the previous pref to a value of 52.9 (Serpent 52.9.0 is really NOT Firefox 60.9 - this value was a setting implemented by MCP to achieve better compatibility with recent sites (which tend to use UA sniffing rather than browser feature set detection); actually, I feel better having the browser advertise itself as Fx 52.9 and then create as needed SSUAOs for those sites that break with that setting...

When FxESR 68 becomes the only one available ESR branch, no doubt the sites implementing UA sniffing will raise the bar, so to speak, to demand Firefox 68.0 as a minimum Fx version; spoofing UXP browsers to Fx 68.9 in the state they are now may or may not work for those sites; if the sites update along the javascript+CSS code they serve to Fx 68.0, then that SSUAO hack won't work :( ; indeed, using a SSUAO for GitHub in Serpent 52.9.0 and making it pose as Firefox 68.0 (or 69.0) will give you grief, as GitHub will be broken :realmad: .

When we come to that point, we (using UXP browsers on XP/Vista) will be at the mercy of the Moonchild team; they'll have to successfully backport newer Javascript and CSS iterations to UXP (Pale Moon + Basilisk), so we can benefit, in turn, in the NM28 and St52 forks!

Edited by VistaLover
Link to comment
Share on other sites

3 hours ago, 404notfound said:

Github's interface is broken in v52-based Serpent.

I agree with @VistaLover; it seems to work OK for me. But I do use a user-agent override to

Mozilla/5.0 (Windows NT 6.1; rv:60.9) Gecko/20100101 Firefox/60.9

... which can be implemented either by a github.com-specific SSUAO, a general UAO, or by the compatibility prefs @VistaLover mentioned.

Without a UAO of some sort, Github.com hasn't worked with FF 52 or Serpent for quite some time.

(I agree that before long, we'll need to start spoofing FF 68 to have a chance, and even that may not work, depending on what new Javascript and/or CSS features Github decides to start using.)

Also, if you have enabled either dom.webcomponents.enabled or dom.webcomponents.customelements.enabled, you need to disable them for Github.com to work with Serpent. (I have no idea why.) Everything seems to work fine with these disabled, although disabling them costs you a few points on html5test.com....

Link to comment
Share on other sites

1 hour ago, VistaLover said:

I also find that a SSUAO for GitHub of the following format:


general.useragent.override.github.com;Mozilla/5.0 (Windows NT 6.0; rv:52.0) Goanna/4.4 Basilisk/52.9.0

also does the job....

Interesting that a "native" Basilisk user agent works, given that a "native" FF 52.9 UA does not! It implies that Github has chosen to support Basilisk (at least, the official version), which is hopeful for the future. Once Github stops supporting 60.9, it may be best to move to the above (via a SSUAO) vs. trying to spoof FF 68. Why lie if telling the truth works?

Link to comment
Share on other sites

I did notice one cosmetic change with the latest Serpent 52 version: When enabling and using the hidden "Developer Edition" theme, the "Classic Theme Restorer" add-on can no longer "square" the browser tabs! The Tab Appearance selection is greyed out, and there are new messages on the Classic Theme Restorer Tabs settings (Page 1) that say "Tab appearance is controlled by the current theme." and "Third party theme detected! Some options do not work with third party themes!" Apparently CTR now considers the Developer Edition theme a "third party" theme, but didn't in earlier Serpent 52 versions.

I don't know if that's a new bug or a fix for a bug (i.e., square tabs were never supposed to work with the Developer Edition theme, but did anyway until now).

That's pretty minor in the grand scheme of things, but I did happen to like the Developer Edition theme with squared tabs. I guess you can't have everything though.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...