Nitro Pro (64-bit) 歷史版本列表
更新時間：2020-01-29
更新細節：
更新時間：2020-01-17
更新細節：
更新時間：2020-01-16
更新細節：
What's new in this version:
Fixed:
- [Mono.Debugger.Soft] Connections are not properly closed
- New arm64_32 architecture (watchOS 5) [arm64_32] make “Debug Mode” work on Watch series 4 with –interpreter
- Task calls SynchronizationContext.Post on cancelling
- DataContractSerializer is not available
- [Blazor] IL Linker not working correctly with IQueryable extensions
- condition ‘ji’ not met, with ‘dynamic’ and multithreading
- mono 5.20 hangs when called from native thread
- Null Pointer Exception after debugger pauses and then continues
- [iOS][Tests] There are a number of System.Numeric tests that fail on iOS 32b devices
- [iOS][Tests] A number of linq tests fail on iOS 32b devices
- [iOS][Tests] A number of tests from Microsoft.CSharp fail on iOS 32b devices.
- [iOS][Tests] Several corelib tests crash on iOS32b devices.
- [netcore] Make OverlappedTests.PackNegTest Pass
- [netcore] Make OverlappedTests.UnPackTest Pass
- MERP indefinitely hangs on application quit
- [debugger] Update client thread frames after SetIP.
- Mono.Net.Security.MonoTlsStream: Crash when stream appears to have already been disposed
- 1024 hard limit of open file descriptors
- Mono crashes during precompiling dll in fullaot mode
- Coverity: derefenrecing null in profiler (CID: 1307043) Skip degenerate qsort: num < 2, size == 0, base == 0
- [mini] run regression tests with fullaot+llvm
- typeof(object).GetMember(“”) does not return an empty array
- Native crash in ves_icall_System_Net_Sockets_Socket_Connect_internal
- IOException: Sharing violation on path …
- [netcore] AOT with unresolved dependencies hits asserts
- VS 16.2.0 regression: CopyToAsync from DeflateStream to GzipStream throws NotImplementedException
- Interpreter stack size is too large
- Embedded Mono hangs when using native threads
- Change netcore package to be using release builds
- LLVM: ““.AsSpan()[0] doesn’t throw IndexOutOfRangeException
- [wasm] Timers do not fire when run inside WebWorkers.
- Relocations in .text on arm
- [netcore] Regession with AOTed System.Private.CoreLib
- [llvm] Assertion: should not be reached at mini-llvm.c:7104
- [Mobile] DateTime.Now returns incorrect local time for one hour after entering DST in 39 locales.
- JitTests.Float fails on iOS devices in release mode on 2019-08
- Timezone data not handled correctly on FreeBSD
- System.IO.Path.GetFullPath(“\.pipepipename”): different results on Mono and .NET
- FileSystemEventArgs.FullPath throws ArgumentNullException
- make distclean fails after build w/ embedded zlib
- [netcore] Vector.CopyTo w/ LLVM emits wrong exception
- [WinForms] ControlBox property didn`t hide Close button and icon
- [merp] missing data in crashing reporting json native frames
- C# REPL Unusable on Mono 6 / Ubuntu 19
- Disposing the FileSystemWatcher does not close associated file descriptors
- SIGSEGV in mono_class_setup_vtable_general
- Date.Time parse issue (year 1948) Avoid creating un-representable DateTime for transition point
- Stream.ReadAsync continues on different thread
- mono_gc_finalize_notify spinning after process exit
- LLVM failed for String.GetHashCode
- [coop][interp] mono_threads_enter_gc_safe_region Cannot transition thread 0x1952b000 from STATE_BLOCKING with DO_BLOCKING
- Crash when debugging iOS application that throws on DispatchQueue
- [arm64_32] fix remaining regression tests
- [Wasm] Switch to PNSE FileWatcher & Exclude Tests
- [Wasm] Determine if System.Net.Http.UnitTests Failures are Relevant
- XmlSerializer Deserializing Property with same name as its enum type no longer works
- LLVM: recursive calls have overhead in JIT mode
- Starting in Mono 6.0 (2019-02), NotImplementedException prevents using StreamWriter with GZipStream for encodings that use a preamble
- File.GetCreationTimeUtc() returns the time last modified, not time created
- [merp] crash reports have Darwin kernel version in OSVersion field
- Out of bounds unhandled exception
- [wasm][xunit tests] RemoteExecutorTests.RemoteInvokeWritesToFile fails
- [wasm][xunit tests] System.Net.Security.Tests.SslStreamAlpnTests - MissingMethodException: Default constructor not found
- Regression: when debugger encounters a not-unhandled exception, it stops and shows “Dns.cs file not found” (Dns being the BCL class used)
- Marshalling managed exception contains cut off stacktraces
- SystemNative_CopyFile() call to fchmod() introduced in Mono 6.0 is not compatible with the external storage location on some Android OS versions and devices
- mono_aot_register_module conflicting definitions
- DriveInfo return empty space for system volume on MacOS 10.15 Catalina
- [merp] mono_summarize_unmanaged_stack tries to take a lock while calling decode_exception_debug_info
- System.BadImageFormatException when reflecting on BCL shipped with Mono
- mono_magic_trampoline being called more than expected
- Investigate heavy stack from System_Threading_Interlocked_Exchange_T_REF_T_REF__T_REF
- [merp] generate a crash report if process is killed with SIGTERM
- Debugging ‘async Task Name()' method makes app crash
- Await within method with return type Task makes debugging fail
- AOT + System.Reflection.Emit + ConstructorInfo doesn’t work as expected
- [Regression] Profiler’s calls log SIGABRTs when using GDI+ loader
- Delegate does not invoke target virtually
- Q: is using loader lock for domain seq_points access correct? (mono runtime) [runtime] Fix locking in mono_get_seq_points ().
- [merp] SendMicrosoftTelemetry icall doesn’t do any MERP logging when inducing a Managed Crash
- threadpool hang due to unlimited hill climbing
- Deadlock in GC during bridge callback from native thread on Android
- Mtouch argument interpreter crashes EntityFrameworkCore 3.0 iOS app
- [Bug] Segmentation Fault receiving message on WatchOS with debugger attached
- Native linking fails for armv7s
- [embedding] Chaining Mach exceptions to Mono signals using utility threads
更新時間：2020-01-16
更新細節：
What's new in this version:
- chr - improved stability when changing ARP modes on e1000 type adapters
- console - prevent "flash" directory from being removed (introduced in v6.46)
- console - updated copyright notice
- crs305 - disable optical SFP/SFP+ module Tx power after disabling SFP+ interface
- defconf - fixed "caps-mode" not initialized properly after resetting
- defconf - fixed default configuration loading on RBwAPG-60adkit (introduced in v6.46)
- lora - fixed packet sending when using "antenna-gain" higher than 5dB
- lte - fixed "cell-monitor" on R11e-LTE in 3G mode
- lte - fixed "earfcn" reporting on R11e-LTE6 in UMTS and GSM modes
- lte - report only valid info parameters on R11e-LTE6
- ppp - fixed minor typo in "ppp-client" monitor
- qsfp - do not report bogus monitoring readouts on modules without DDMI support
- qsfp - improved module monitoring readouts for DAC and break-out cables
- routerboard - added "mode-button" support for RBcAP2nD
- security - fixed vulnerability for routers with default password (limited to Wireless Wire), admin could login on startup with empty password before default configuration script was fully loaded
- system - fixed "*.auto.rsc" file execution (introduced in v6.46)
- system - fixed "check-installation" on PowerPC devices (introduced in v6.46)
- traffic-generator - improved memory handling on CHR
- webfig - allow skin designing without "ftp" and "sensitive" policies
- webfig - fixed "skins" saving to "flash" directory if it exists (introduced in v6.46)
- winbox - automatically refresh "Packets" table when new packets are captured by "Tools/Packet Sniffer"
- winbox - fixed "Default Route Distance" default value when creating new LTE APN
- winbox - removed duplicate "join-eui" and "dev-eui" parameters under "Lora/Traffic"
更新時間：2020-01-16
更新細節：
What's new in this version:
Resolved potential security vulnerabilities:
Heap Corruption JPEG2000 ssizDepth:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to heap corruption and the application crashing out. Arbitrary remote code execution has not been proven but may be possible.
Heap Corruption JPEG2000 yTsiz:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to heap corruption and the application crashing out. Arbitrary remote code execution has not been proven but may be possible.
Use After Free CharProcs:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to use-after-free condition and the application crashing out
Heap Corruption ICCBased Color Space:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to heap corruption and the application crashing out. Arbitrary remote code execution has not been proven but may be possible.
Heap Corruption Page Kids:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to heap corruption and the application crashing out. Arbitrary remote code execution has not been proven but may be possible.
Use After Free Stream Length:
- A vulnerability exists when opening a specially crafted malicious PDF document which can lead to use-after-free condition and the application crashing out
更新時間：2020-01-16
更新細節：
What's new in this version:
Improvements for plugin authors:
- Finalize property value only when the value is queried
- In previous Gradle releases, certain Gradle types, such as Property or ConfigurableFileCollection, provided a finalizeValue() method that eagerly calculated the final value for a property and prevented further changes
- When a task starts running, Gradle automatically finalizes task properties of these types, so that the same value is seen by the task's actions and Gradle's build caching/up-to-date checks. This also avoids calculating the property value multiple times, which can sometimes be expensive. Plugins can also use finalizeValue() to finalize other properties, such as a property of a project extension, just prior to querying the value.
- In this release, these types gain a new finalizeValueOnRead() method. This method is similar to finalizeValue(), except that the final value is calculated when the value is queried rather than immediately. Plugins can use this method when a property value may be expensive to calculate or when the value may not have been configured to ensure that all consumers of the property see the same, final, value from that point onwards.
- Please see the user manual for more details
New managed property types:
- Gradle 5.5 introduced the concept of a managed property for tasks and other types, where Gradle provides an implementation of the getter and setter for an abstract property defined on a task, project extension, or other custom type. This simplifies plugin implementations by removing a bunch of boilerplate.
In this release, it is possible for a task or other custom type to have an abstract read-only property of type DomainObjectSet<T>.
- Please see the user manual for more details.
New factory methods:
The ObjectFactory type, which plugins and other custom types use to create instances of various useful types, has several new factory methods to create certain Gradle types that could only be created using internal APIs in previous releases:
- The polymorphicDomainObjectContainer() method to create ExtensiblePolymorphicDomainObjectContainer<T> instances
- The namedDomainObjectSet() method to create NamedDomainObjectSet<T> instances
- The namedDomainObjectList() method to create NamedDomainObjectList<T> instances
Improvements for Gradle tooling providers:
- Tooling API: TestLauncher can run specific Test task tests
- The TestLauncher interface in the Tooling API could already launch tests by specifying the name of the test classes or methods; however, if there are multiple Test tasks, then all Test tasks would be executed.
- For IDEs, developers usually want to execute only one task at a time. Gradle 6.1 introduces a new API to execute tests with specific Test task using the withTaskAndTestClasses() and withTaskAndTestMethods() methods.
更新時間：2020-01-16
更新細節：
更新時間：2020-01-15
更新細節：
更新時間：2020-01-03
更新細節：
更新時間：2019-12-30
更新細節：